Broadband Related > ISPs

odd apparent congestion on my tbb graph - sky ipv4

(1/4) > >>

Chrysalis:
Link to my graph here

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2c7929f86f40f9234633198ceb0a161e

Notice how the max latency increases during dusk hours (this has been daily for weeks now), of course that is not peak usage time of day, so it is odd, I have not done any speedtesting during that time.

My ipv6 graph does not show this issue.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/ec6acc210ba8cc3f2c08a166f017a582

burakkucat:
That is a puzzling observation, for which I cannot offer any possible explanation.

tommy45:
The peering routeing will probably be different maybe the issues lie on 3rd parties network(links) failing that if they use the same routes, then maybe they have one reversed? As the TBBQM etc will only show the route in one direction

Chrysalis:
well its not just tbb, here is a jittery set of pings, tbb speedtest is perfect tho so whatever it is doesnt seem to affect throughput.

C:\Windows\system32>ping -t bbc.co.uk

Pinging bbc.co.uk [212.58.244.22] with 32 bytes of data:
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=12ms TTL=56
Reply from 212.58.244.22: bytes=32 time=11ms TTL=56
Reply from 212.58.244.22: bytes=32 time=9ms TTL=56
Reply from 212.58.244.22: bytes=32 time=9ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=9ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=13ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56
Reply from 212.58.244.22: bytes=32 time=9ms TTL=56
Reply from 212.58.244.22: bytes=32 time=10ms TTL=56

Ping statistics for 212.58.244.22:
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 13ms, Average = 10ms

Chrysalis:
have tried to raise it via official tech support but hitting a brick wall, as I cannot put 100% into trying to say its something like congestion given the time of day so I am unsure myself, I am pretty sure its not my network tho.

So will have to report this via the backdoor directly to a senior network bod.

Navigation

[0] Message Index

[#] Next page