Re: Think Broadband Ping Monitor Results (POST YOURS)
 

After how long :erm:

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Manchester the same

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I can give you details of the peering route if you want :)

[root@london2 ~]# traceroute 82.9.223.211
traceroute to 82.9.223.211 (82.9.223.211), 30 hops max, 40 byte packets
1 95.154.245.130 (95.154.245.130) 0.031 ms 0.034 ms 0.014 ms
2 87.117.212.29 (87.117.212.29) 0.443 ms 0.448 ms 0.462 ms
3 610.core1.hex.as20860.net (62.233.127.181) 1.497 ms 1.483 ms 1.466 ms
4 202.core1.thn.as20860.net (62.233.127.11) 1.427 ms 1.413 ms 1.440 ms
5 195.66.224.23 (195.66.224.23) 1.447 ms 1.365 ms 1.413 ms
6 brhm-bb-1c-ae5-0.network.virginmedia.net (212.250.15.209) 12.153 ms 12.135 ms 12.153 ms
7 brhm-bb-2a-ae3-0.network.virginmedia.net (62.254.42.109) 6.031 ms 5.982 ms 28.850 ms
8 nrth-bb-2a-ae4-0.network.virginmedia.net (62.254.42.46) 6.600 ms 6.468 ms 6.646 ms
9 nott-core-2b-ae13-0.network.virginmedia.net (62.254.42.78) 6.835 ms 6.824 ms 6.811 ms

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

TBH, it only started at 1am this morning, them acknowledging it within a day is far better than the north-of-Manchester core congestion that went on for a month...

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Awesome cheers! Looks like it's peered at a different node in LINX than the one having issues?

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

very possible.
Its on a VPS in a IOMark data center.

It peers at Linx on 195.66.224.2

If you give me the IP at Linx that is the problem i'll add it to www.ukinternetreport.co.uk so it gets graphed

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

To be fair this may be correct but it's not necessarily that simple, often there are many logical links on the same 'node' for private peering vs. public peering, as well as multiple physical links serving each logical link via bonded channels. Last I knew VM used many 10Gbps links into LINX (vs. BT who used fewer ports but running at 100Gbps). ---------- Post added at 19:47 ---------- Previous post was at 19:41 ---------- It's not actually an IP at LINX that's the problem. The problem appears to lie solely on VM's core network, on some link between their LINX router and Northants. 62.253.174.17 is a good IP to ping if you want to monitor it, although that's only affected when entering via London far as I can tell, traffic from my location on BT to VM bounces via Manchester in one direction and isn't affected (thus, the congestion seems to be unidirectional)

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

pingbox1.thinkbroadband.com
nrth-bb-1b-ae7-0.network.virginmedia.net

Should start graphing soon

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

great apcybrax. I do want to see the graphing...
its been a bit of time since last graphing....

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Cool, thanks.

FWIW the culprit seems to be a link between Telehouse East and VM's Nrth datacentre wherever that is.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

gas..omg.stop following me

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

anyone able to advise what the potential problem is here?

I've restarted my SH to see if that resets my graph.

I'm in the FK1 area.

[img]Download Failed (1)[/img]

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Ekk Blairhoyle.

That not good.

Have you noticed any other problems? Its its only the TBB graph and your speed and connection is otherwise ok it might be related to the peering problem.

If you have other problems Post a new thread for help as this one will get full of unrelated stuff if you ahve a connection problem.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

thanks for the response mate

---------- Post added at 20:11 ---------- Previous post was at 20:10 ----------

I've got internet connection fine and down speeds seem poor

my TBB profile is lagging a bit though