cancel
Showing results for 
Search instead for 
Did you mean: 

Has something happened in London today? 11th march

Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Has something happened in London today? 11th march

Routing to US is all over the place, taking on average 7 hops just to pass through London alone and being routed to London then via NL to US

FTTP 500 regrade from Tues 28th November
8 REPLIES 8
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: Has something happened in London today? 11th march

So is it squeaky wheel time?  Has something happened to routing to US via London or not?  Or did you finally change from level3, but to a worse provider for traffic to US?
FTTP 500 regrade from Tues 28th November
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Has something happened in London today? 11th march

Hi Gus,
Do you know what kind of ping times you were seeing prior to this to the same site/server?
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: Has something happened in London today? 11th march

Historically with level3 they used to be around 130ms until mid winter then it increased too the 170-180.  Its been that way since the big winter storm hit the US.
But this new routing is worse, regularly seeing lost syncs with the games embedded irc chat.  level3 were bad but ntt.net are worse from my point of view.
edit: added a 5min trace, note this if off peek, yet I get 200ms its worse at peek times
FTTP 500 regrade from Tues 28th November
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: Has something happened in London today? 11th march

From here, 5 minutes ago if it's any help.
ping 192.184.14.42
Pinging 192.184.14.42 with 32 bytes of data:
Reply from 192.184.14.42: bytes=32 time=179ms TTL=51
Reply from 192.184.14.42: bytes=32 time=178ms TTL=51
Reply from 192.184.14.42: bytes=32 time=178ms TTL=51
Reply from 192.184.14.42: bytes=32 time=178ms TTL=51
Ping statistics for 192.184.14.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 178ms, Maximum = 179ms, Average = 178ms

tracert 192.168.14.42
Tracing route to 192.168.14.42 over a maximum of 30 hops
  1    1 ms    <1 ms    <1 ms  192.168.1.254
  2    34 ms    32 ms    33 ms  lo0-central10.ptn-ag04.plus.net [195.166.128.193]
  3    33 ms    32 ms    33 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.140]
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
Think you can probably guess the next 20!
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: Has something happened in London today? 11th march

Another trace at start of peek gaming time  Lips_are_sealed
FTTP 500 regrade from Tues 28th November
AndyH
Grafter
Posts: 6,824
Thanks: 1
Registered: ‎27-10-2012

Re: Has something happened in London today? 11th march

I think your traceroute is showing both directions of traffic - it looks like the return path is via Amsterdam.
ejs
Aspiring Hero
Posts: 5,442
Thanks: 631
Fixes: 25
Registered: ‎10-06-2010

Re: Has something happened in London today? 11th march

It looks like a standard outbound traceroute, mine is pretty similar:
[tt]traceroute to 192.184.14.42 (192.184.14.42), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  1.289 ms
2  lo0-central10.pcl-ag05.plus.net (195.166.128.186)  42.957 ms
3  link-b-central10.pcl-gw02.plus.net (212.159.2.178)  39.984 ms
4  xe-1-2-0.pcl-cr02.plus.net (212.159.0.210)  19.962 ms
5  195.99.126.98 (195.99.126.98)  21.272 ms
6  core4-te0-12-0-20.faraday.ukcore.bt.net (109.159.249.153)  21.436 ms
7  peer2-et-10-3-0.faraday.ukcore.bt.net (62.6.201.199)  34.822 ms
8  213.137.183.88 (213.137.183.88)  27.147 ms
9  82.112.115.185 (82.112.115.185)  23.300 ms
10  ae-1.r03.londen05.uk.bb.gin.ntt.net (129.250.6.230)  179.116 ms
11  ae-15.r03.amstnl02.nl.bb.gin.ntt.net (129.250.6.25)  178.398 ms
12  ae-4.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.146)  33.270 ms
13  ae-6.r23.asbnva02.us.bb.gin.ntt.net (129.250.6.176)  120.973 ms
14  ae-0.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.84)  131.760 ms
15  ae-2.r21.lsanca03.us.bb.gin.ntt.net (129.250.3.55)  188.018 ms
16  ae-2.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.70)  197.230 ms
17  ae-22-100.r04.lsanca03.us.ce.gin.ntt.net (129.250.200.138)  180.011 ms
18  192.184.12.9 (192.184.12.9)  178.963 ms
19  192.184.14.42 (192.184.14.42)  195.643 ms[/tt]
30FTTC06
Pro
Posts: 2,286
Thanks: 108
Fixes: 4
Registered: ‎18-02-2013

Re: Has something happened in London today? 11th march

Same here.
--- 192.184.14.42 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49069ms
rtt min/avg/max/mdev = 167.845/174.111/187.179/4.475 ms
[tt]traceroute to 192.184.14.42 (192.184.14.42), 30 hops max, 60 byte packets
1  192.168.0.254 (192.168.0.254)            0.890 ms  0.879 ms  0.886 ms
2  lo0-central10.pcl-ag01.plus.net (195.166.128.182)  9.913 ms  10.853 ms  10.786 ms
3  link-a-central10.pcl-gw01.plus.net (212.159.2.160)  9.176 ms  10.116 ms  10.055 ms
4  xe-10-0-0.pcl-cr01.plus.net (212.159.0.192)  10.640 ms  10.562 ms  10.335 ms
5  195.99.126.96 (195.99.126.96)  10.841 ms  10.377 ms  10.348 ms
6  core3-te0-2-0-19.faraday.ukcore.bt.net (109.159.249.5)  10.349 ms
  core4-te0-12-0-18.faraday.ukcore.bt.net (109.159.249.17)  11.804 ms
  core3-te0-0-0-26.faraday.ukcore.bt.net (109.159.249.49)  10.079 ms
7  peer2-et-8-3-0.faraday.ukcore.bt.net (62.6.201.197)  11.546 ms  10.227 ms  10.134 ms
8  213.137.183.70 (213.137.183.70)  9.698 ms 213.137.183.64 (213.137.183.64)  9.728 ms 213.137.183.66 (213.137.183.66)  9.139 ms
9  82.112.115.185 (82.112.115.185)  10.406 ms  10.326 ms  12.109 ms
10  ae-1.r03.londen05.uk.bb.gin.ntt.net (129.250.6.230)  168.963 ms  171.374 ms  170.429 ms
11  ae-15.r03.amstnl02.nl.bb.gin.ntt.net (129.250.6.25)  183.304 ms  186.740 ms  185.924 ms
12  ae-4.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.146)  17.677 ms  18.340 ms  26.053 ms
13  ae-6.r23.asbnva02.us.bb.gin.ntt.net (129.250.6.176)  108.078 ms  99.847 ms  102.809 ms
14  ae-0.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.84)  102.866 ms  102.624 ms  97.915 ms
15  ae-2.r21.lsanca03.us.bb.gin.ntt.net (129.250.3.55)  164.899 ms  167.384 ms  201.088 ms
16  ae-2.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.70)  166.620 ms  178.782 ms  163.310 ms
17  ae-23-100.r04.lsanca03.us.ce.gin.ntt.net (129.250.200.122)  170.287 ms  176.589 ms  164.853 ms
18  192.184.12.81 (192.184.12.81)  161.331 ms  166.177 ms 192.184.12.9 (192.184.12.9)  173.093 ms
19  192.184.14.42 (192.184.14.42)  156.795 ms  166.335 ms  180.038 ms[/tt]