In reply to a post by GonePostal:

"I have looked at the service for that period and can see the line was being heavily saturated which would cause the latency you experienced.
"This may be caused by you being connected to a gateway in Manchester. I would advise rebooting your router so you connect to a more local one."
Two short disconnects at about 02:00 and 04:30 this morning and the graph is looking a lot more sensible but I have no idea whether that was Zen or IDNet.
All in all, less than helpful with no indication the IDNet are willing to take ownership of the problem or review their backhaul agreement with Zen.

To be fair they gave a reasonable explanation above. I've struggled to get anything useful from network operators who we pay a lot more money to (not broadband). NTT in particular is being really painful with their inability to agree connectivity with other networks causing weird things like routing from one rack in same building going via another country (US being worst example) to another.

Can't comment on the specifics but we do hope to aggregate BQM data soon for more visibility

In reply to a post by seb:

. . . .To be fair they gave a reasonable explanation above. . . .

Maybe it's a reasonable explanation but it is neither taking ownership of the problem nor indicating that they are willing to chase up their supplier to try and resolve it. I have made the same comments to IDNet in response to their e-mail.

There have been a number of issues reported here and on other online outlets over the last few months which seem to point to the IDNet mindset as not being aligned with their domestic customers. I am only still with them because we are waiting for a viable fibre offering in our village. I would prefer a single pain barrier of going to VoIP and FTTP at the same time if possible rather than two separate disruptions.

Edited by GonePostal (Tue 11-Mar-25 14:54:42)