Post Your Fibre Think Broadband Ping Graphs (Not VirginMedia Cable)

[Qtx]

Originally Posted by driz

Any chance of a tracert to qw.foppa.dk?

Did a few tracerts and they all came back pretty much the same with a huge jump at 4.69.166.22 which is the second hop on the route owned by Level 3 (195.50.122.113 being theirs too and obviously where they peer with sky).

C:\>tracert qw.foppa.dk

Spoiler: 

Tracing route to qw.foppa.dk [89.104.194.146]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 9 ms 6 ms 7 ms ip-84-38-37-10.easynet.co.uk [84.38.37.10]
4 12 ms 7 ms 7 ms ip-84-38-37-106.easynet.co.uk [84.38.37.106]
5 5 ms 5 ms 5 ms 195.50.122.113
6 28 ms 28 ms 28 ms 4.69.166.22
7 28 ms 28 ms 27 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
8 28 ms 29 ms 28 ms ae-47-47.ebr2.Amsterdam1.Level3.net [4.69.143.77]
9 28 ms 29 ms 28 ms ae-24-24.ebr1.Amsterdam1.Level3.net [4.69.143.65]
10 38 ms 28 ms 28 ms ae-48-48.ebr2.Dusseldorf1.Level3.net [4.69.143.210]
11 28 ms 28 ms 28 ms ae-23-23.ebr1.Dusseldorf1.Level3.net [4.69.143.189]
12 28 ms 27 ms 28 ms ae-1-7.bar1.Copenhagen1.Level3.net [4.69.142.169]
13 28 ms 28 ms 27 ms ae-0-10.bar1.Copenhagen2.Level3.net [4.69.137.154]
14 29 ms 28 ms 28 ms 212.73.252.6
15 26 ms 26 ms 26 ms 93.176.94.135
16 25 ms 25 ms 26 ms 37.49.139.102
17 25 ms 25 ms 25 ms dist01b.ip.comendo.com [89.104.192.66]
18 26 ms 25 ms 25 ms klyden.foppa.dk [89.104.194.146]

Trace complete.

Also a simple ping:

Spoiler: 

C:\>ping -t qw.foppa.dk

Pinging qw.foppa.dk [89.104.194.146] with 32 bytes of data:
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=26ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=28ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56
Reply from 89.104.194.146: bytes=32 time=25ms TTL=56

Ping statistics for 89.104.194.146:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 28ms, Average = 25ms
Control-C
^C
C:\>

[driz]

That's brilliant, thanks. Jump is probably an artifact of MPLS since every hop is around 25-28ms afterwards.

[Qtx]

Yeah, always see that happen on transit routes out of the UK.

Nice pings for the gaming servers I use too

Spoiler: 

C:\>tracert 94.76.229.7

Tracing route to quakelive.london.i3d.net [94.76.229.7]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms ip-84-38-37-10.easynet.co.uk [84.38.37.10]
4 13 ms 7 ms 7 ms te0-0-0-5.er11.thlon.ov.easynet.net [89.200.135.135]
5 7 ms 7 ms 8 ms the-linx.as29550.net [195.66.224.223]
6 8 ms 8 ms 8 ms a.1.magic-the.as29550.net [217.112.81.90]
7 8 ms 8 ms 7 ms quakelive.london.i3d.net [94.76.229.7]

Trace complete.

Spoiler: 

C:\ping -t 94.76.229.7

Pinging 94.76.229.7 with 32 bytes of data:
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59
Reply from 94.76.229.7: bytes=32 time=8ms TTL=59
Reply from 94.76.229.7: bytes=32 time=7ms TTL=59

Ping statistics for 94.76.229.7:
Packets: Sent = 42, Received = 42, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
Control-C
^C

[driz]

Very nice - has convinced me to switch from BT. Sick of getting 20ms to London servers because of everything going to Sheffield and back (and I'm in London zone 3).

[Chrysalis]

yes I dont know why BT have such bizzare routing.

even much smaller isps like zen have PoPs in every major city. Yet BT seem limited to routing through a dozen or so PoPs around the country causing indirect routes, and even weirder can be if you somewhere like london you an still get routed via sheffield. This is a problem BT have had for decades. Its a good reason to sign up to a LLU provider who bypass BTs network.

here is mine to the 2 destinations QTX posted and I am on fast path. note the jump to ealing hop.

qw.foppa.dk

 1    <1 ms    <1 ms    <1 ms  home.gateway [192.168.1.253]
 2     6 ms     5 ms     5 ms  bt.gateway [217.32.144.166]
 3     6 ms     6 ms     6 ms  bt.internal [217.32.144.190]
 4     8 ms     7 ms     8 ms  213.120.181.246
 5     8 ms     7 ms     7 ms  217.41.169.213
 6     8 ms     7 ms     7 ms  bt.internal [217.41.169.109]
 7     7 ms     7 ms     7 ms  109.159.251.249
 8    18 ms    23 ms    23 ms  core2-te-0-13-0-10.ealing.ukcore.bt.net [109.159
251.179]
 9    17 ms    17 ms    18 ms  peer1-xe3-2-1.telehouse.ukcore.bt.net [109.159.2
4.209]
10    18 ms    17 ms    17 ms  xe-2-3-0-0.ldn1nqp1.uk.ip.tdc.net [195.66.236.64

11    30 ms    30 ms    78 ms  ae0-0.boanqp7.dk.ip.tdc.net [83.88.23.196]
12   198 ms   209 ms   207 ms  62.243.244.238
13    33 ms    33 ms    33 ms  klyden.foppa.dk [89.104.194.146]

  1    <1 ms    <1 ms    <1 ms  home.gateway [192.168.1.253]
  2     5 ms     5 ms     5 ms  bt.gateway [217.32.144.166]
  3     6 ms     6 ms     6 ms  bt.internal [217.32.144.206]
  4     8 ms     8 ms     8 ms  213.120.181.246
  5     8 ms     7 ms     7 ms  217.41.169.213
  6     8 ms     8 ms     7 ms  bt.internal [217.41.169.109]
  7     7 ms     7 ms     7 ms  acc2-10GigE-9-3-0.sf.21cn-ipp.bt.net [109.159.25
1.223]
  8    17 ms    16 ms    20 ms  core2-te0-5-0-7.ealing.ukcore.bt.net [109.159.25
1.151]
  9    23 ms    23 ms    23 ms  peer4-te0-5-0-5.telehouse.ukcore.bt.net [109.159
.254.169]
 10    18 ms    22 ms    17 ms  hex89-linx.as29550.net [195.66.236.223]
 11    16 ms    16 ms    16 ms  vl668.the-7600.as29550.net [92.48.95.14]
 12    32 ms    36 ms    48 ms  a.1.magic-the.as29550.net [217.112.81.90]
 13    18 ms    18 ms    18 ms  quakelive.london.i3d.net [94.76.229.7]

[pabscars]

Anybody else seeing this on their graph

[Qtx]

Lots of hops there Chrys! The routing truly does suck on BT.

Not on my graph here Pabscar. The timing of that hump makes me think Sky was possibly doing some work during the quiet hours that affected you.



My Synology NAS is up and running now, with a healthy download queue

[pabscars]

cheers Q, yes I thought as much, always worth checking though

[craigj2k12]

I had the same, no idea what it was but back to normal now

[Qtx]

Maybe a location or route you both have in common. Shout if you want to compare tracerts to TBB.

[pabscars]

Originally Posted by Qtx

Maybe a location or route you both have in common. Shout if you want to compare tracerts to TBB.

Cheers will do, all back to normal now

[Qtx]

Seeing a pattern with the peaks here, could it be DLM? Don't think the NAS is doing anything that would cause them and they were there before I started a big download queue in the early hours of the morning

[craigj2k12]

seems to be consistent with Sky graphs

[pabscars]

Agreed, mine has had spikes like that since day one

[Qtx]

Interesting! So no one knows what causes it?

Obviously there is no impact on our connections but I would still like to know if it is caused by x or y on Sky's network or if its something to do with the route to TBB for example.

A little puzzle for sure

Edit: Just a thought, could the sky tv box be causing it? I might unplug mine from the network to test it