To me that sounds like your router and the Coms DSLAM are less compatible than your pairing on ADSL24.

I thought the ISP had little to do with your actually sync speed, as its between your home router and the exchange so before it even hits the ISPs routers?

Certainly in coms/adsl24 case where they both use TTB

Your right as a general point, I agree. What I wouldn't be sure about is whether or not the same TT DSLAM or line card would be used.

I'm probably talking rubbish, but I wouldn't rule out the possibility, given that we aren't aware of any other reason for a difference.

Well, as guinea pig number three, I can confirm I have just migrated from Coms LLU to Xilo LLU virtually hitch free. Just had to manually reboot the router and add the new login details and away we went! For some reason I remained connected to Coms even though migration was done.

Initial results look very good with some of the best speeds I've ever had!
Long may it continue!

Woody

Yea not sure why you can still connect to both old and new ISP, but happened with ADSL24/Coms migration

It happens a lot on BT Wholesale-based ADSLx. It will be the same cause here.

On BT Wholesale your login details are fed to an authentication centre (I think that's what it is called) which routes them to the ISP indicated by them. The losing ISP will usually not delete your account until a bit after they receive the Openreach notification of a completed migration, but the gaining ISP will normally activate the new one before the expected migration.

On TTB, if as has been said there is no real change other than an internal accounting one, I expect the same applies. Don't forget that on these connections they probably aren't a resold TBB product, but hived off the TT network at some stage to the backhaul provider for the vISP, Coms or xilo/uno. So both logins could work for a while, and there is no physical disconnection to wake you up.

yea, that make sense bob (both,lol)

Despite having migrated on the 9th and having given notice in April, my Coms account today still showed the service marked "active". Left a ticket and received the reply:

"Thank you for bringing this to our attention, Please accept our apologies our system has been update to reflect your migration."

It's probably best to make sure Coms acknowledge the migration before and after it occurs.

1471 now fixed. Had to be actioned by a third party it seems.

Next up: Usage reporting errors. Looks like offpeak time is being metered.

Are you on a metered TTB package Woody? If so, are the usage stats accurate?