200M : Network Congestion

[Sephiroth]

Originally Posted by Skie

Well it's pinging whatever you have set to respond on the IP or Hostname you give it

But yes, is this actually affecting anyone's interweb browsing or vidya gaming? Someone would need to run Smokeping or something similar to get a long term view of latency to multiple sites.

Yeah - the router.

[General Maximus]

ya, very few peeps are going to have publicly routable ips on their home networks so you aren't going to get a pc or anything else responding to it.

[punkrock101]

Originally Posted by alanbjames

I honestly think since Virgin has made the 1Gig available in more and more areas they have not upgraded the capacity of their network enough to cope with demand.

That would be them alright... they used to wait until the capacity has been upgraded to support the higher tiers in the area I remember years ago being stuck on 50 Mb long after 100 Mb started as the local network wasn't ready. Not now they just sell Gigabit broadband in areas with already congested headends.

[SirThomas]

Definitely something amiss the last couple of weeks - It's not just something local to me. PO7 and myself (PO9) for reference.

I do notice that general browsing is a bit 'off' in peak times - So don't think it's a TBB problem. Throughputs aren't affected.

I've missed todays peak, I'll do a few traceroutes and checks tomorrow - be interesting to see what's going on.

Tom

[alanbjames]

This is my current graph and I've not done any downloading today at all.....

[General Maximus]

mine's the same:

[General Maximus]

I would love to know where the problem is and what is causing it because it is getting earlier and earlier. My graph is clear after 8:30.

[The Installer]

Pretty colours here too



Is it affecting connection performance, yes it is 100% Last night webpages were lagging and taking ages to load, and no there is no other stuff happening on my network. This is only a peak time thing.

BBC pings are great too, and show plenty of jitter going on.

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=19ms TTL=58
Reply from 151.101.0.81: bytes=32 time=37ms TTL=58
Reply from 151.101.0.81: bytes=32 time=33ms TTL=58
Reply from 151.101.0.81: bytes=32 time=14ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 37ms, Average = 25ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=40ms TTL=58
Reply from 151.101.0.81: bytes=32 time=27ms TTL=58
Reply from 151.101.0.81: bytes=32 time=22ms TTL=58
Reply from 151.101.0.81: bytes=32 time=75ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 75ms, Average = 41ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=119ms TTL=58
Reply from 151.101.0.81: bytes=32 time=56ms TTL=58
Reply from 151.101.0.81: bytes=32 time=22ms TTL=58
Reply from 151.101.0.81: bytes=32 time=28ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 119ms, Average = 56ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=22ms TTL=58
Reply from 151.101.0.81: bytes=32 time=18ms TTL=58
Reply from 151.101.0.81: bytes=32 time=27ms TTL=58
Reply from 151.101.0.81: bytes=32 time=45ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 45ms, Average = 28ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=101ms TTL=58
Reply from 151.101.0.81: bytes=32 time=18ms TTL=58
Reply from 151.101.0.81: bytes=32 time=66ms TTL=58
Reply from 151.101.0.81: bytes=32 time=196ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 196ms, Average = 95ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=30ms TTL=58
Reply from 151.101.0.81: bytes=32 time=238ms TTL=58
Reply from 151.101.0.81: bytes=32 time=17ms TTL=58
Reply from 151.101.0.81: bytes=32 time=23ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 238ms, Average = 77ms

C:\Users\User>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=47ms TTL=58
Reply from 151.101.0.81: bytes=32 time=12ms TTL=58
Reply from 151.101.0.81: bytes=32 time=76ms TTL=58
Reply from 151.101.0.81: bytes=32 time=68ms TTL=58

[General Maximus]

It looks like I have finally caught it mid-mountain and have been able to run a speed test







The speed test result isn't perfect but I am not worried at all. It kicked off at 600mb/sec and increased proportionally over time. If the test had continued to run another 3 seconds it would have reached my max of 940mbits. The only negative I would say about it is that my ping is higher than usual. They usually come back at 9-11ms so it is running at double atm. I made sure I didn't have anything else running on my network when I ran the test so as to not skew the result.

[Brunel]

https://www.thinkbroadband.com/broad...33e-25-04-2022

[Sephiroth]

[General Maximus]

the full picture from last night

[heero_yuy]

Mine is an almost exact duplicate.

[ianch99]

Seems to be happening every day now? Weird ..

Mon



Tue



Wed

[General Maximus]

Monday




Tuesday




Wednesday