Internet slowdowns in the evenings in Utrecht centraal

Hello dear Ziggo forum users!

Anyone else experiencing problems with Ziggo cable internet in the evenings/nights? During daytime it`s totally fine, and usually after 8, it starts to slow down to an unusable state. Very high ping with a very low data transfer. It`s absolutely worthless for me like that, since i usually start using internet at around 8 for gaming, and with a high ping it is impossible. I think it is a problem with the ISP, since it works fine during daytime. I guess in the evening they have a heavy increase on the network load and that could cause the problem.

Anyone else having similar issues? Any thoughts on how to resolve this?

Regards
Barni

Today it is terrible during the whole day. Here is a short log what I get when pinging google.nl


Pinging www.l.google.com [173.194.65.104] with 32 bytes of data:
Reply from 173.194.65.104: bytes=32 time=134ms TTL=51
Reply from 173.194.65.104: bytes=32 time=178ms TTL=51
Reply from 173.194.65.104: bytes=32 time=162ms TTL=51
Reply from 173.194.65.104: bytes=32 time=158ms TTL=51
Reply from 173.194.65.104: bytes=32 time=82ms TTL=51
Reply from 173.194.65.104: bytes=32 time=52ms TTL=51
Reply from 173.194.65.104: bytes=32 time=84ms TTL=51
Reply from 173.194.65.104: bytes=32 time=87ms TTL=51
Reply from 173.194.65.104: bytes=32 time=39ms TTL=51
Reply from 173.194.65.104: bytes=32 time=31ms TTL=51
Reply from 173.194.65.104: bytes=32 time=110ms TTL=51
Reply from 173.194.65.104: bytes=32 time=160ms TTL=51
Reply from 173.194.65.104: bytes=32 time=126ms TTL=51
Request timed out.
Reply from 173.194.65.104: bytes=32 time=100ms TTL=51
Reply from 173.194.65.104: bytes=32 time=111ms TTL=51
Reply from 173.194.65.104: bytes=32 time=163ms TTL=51
Request timed out.
Reply from 173.194.65.104: bytes=32 time=16ms TTL=51
Request timed out.
Request timed out.
Reply from 173.194.65.104: bytes=32 time=105ms TTL=51
Reply from 173.194.65.104: bytes=32 time=27ms TTL=51

Ping statistics for 173.194.65.104:
Packets: Sent = 23, Received = 19, Lost = 4 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 178ms, Average = 101ms

ping statistics for google.nl based on a bigger sample:

Ping statistics for 173.194.65.147:
Packets: Sent = 645, Received = 601, Lost = 44 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 514ms, Average = 68ms

doesn`t look good to me

others do not have such problems with ziggo cablenet?

No connection at all this morning.

Just from curiosity, I made a test from my workplace.

Pinging google.nl [173.194.65.103] with 32 bytes of data:
Reply from 173.194.65.103: bytes=32 time=9ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=72ms TTL=49
Reply from 173.194.65.103: bytes=32 time=10ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=11ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=9ms TTL=49
Reply from 173.194.65.103: bytes=32 time=14ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=12ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=10ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=9ms TTL=49
Reply from 173.194.65.103: bytes=32 time=12ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49
Reply from 173.194.65.103: bytes=32 time=12ms TTL=49
Reply from 173.194.65.103: bytes=32 time=8ms TTL=49

Ping statistics for 173.194.65.103:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 72ms, Average = 10ms

Now that is what I would like to see at home on my Ziggo net.

The only thing I can tell is that I experience no problems at all in Utrecht 3572. Have the full 120 megabit download speed 24/7. Do not know about pings, as latency for me is not really an issue as I do not play games where high latency is a problem. But full speed downloading works excellent.

I assume that you already did try a modem reset?

Thanks for the reply, it`s good to hear that, `cause it might show that the promblem is with my system.

I`m at Utrecht 3511. Yes I tried modem reset already. And the strange thing is, that sometimes after modem reset, it is perfect for a short time with very good ping and data transfer results. But only for a few minutes, than it goes wrong again.

What i tried so far is:

-modem reset
-turned off firewall in windows and in the router.
-turned off block anonymous requests in router
-tried with wifi connection
-tried with direct utp connection
-used googles free DNS server (8.8.8.8, 8.8.4.4)
-checked if there are any loose cables
-disconnected the TV from the signal splitter

The internet is shared with another guy, If I get home I will try pinging from his system.

barni zei:

The internet is shared with another guy, If I get home I will try pinging from his system.

Klik om te vergroten...

And that other guy is not by any chance in full download mode each evening starting at 8 ?

Maybe you should try your connection if you connect your PC/laptop directly at the modem without a router in between. Preferably directly at the place where the cable enters your house before any splitters.
And try in Windows Safe Mode to also eliminate the impact of the stuff running on your PC.

If you then still experience issues I would suggest calling the Ziggo helpdesk (which is a quite tiring experience, also hope they speak English) or, maybe better, contact a person from Ziggo webcare at this forum via Private Message.

nooo i checked his download habits already

allrighty, I will try then a few more stuff, and contact them if there is no result.

thanks for your help!

well.....

it seems it was the other guys utorrent what took all the upload bandwith even when not downloading....

sorry it is so lame...

but, thanks for the help! it is working perfectly now, stable connection, low ping!


cheers o/