Lag to newark

Definitely appears to be intermittent issues to newark…

64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=6 ttl=50 time=13.0 ms
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=7 ttl=50 time=15.0 ms
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=8 ttl=50 time=12.6 ms
From POS6-0.GW12.NYC4.ALTER.NET (152.63.22.77) icmp_seq=9 Time to live exceeded
From POS6-0.GW12.NYC4.ALTER.NET (152.63.22.77) icmp_seq=10 Time to live exceeded
From POS6-0.GW12.NYC4.ALTER.NET (152.63.22.77) icmp_seq=11 Time to live exceeded
From POS6-0.GW12.NYC4.ALTER.NET (152.63.22.77) icmp_seq=12 Time to live exceeded
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=13 ttl=50 time=12.9ms
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=14 ttl=50 time=11.4ms
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=15 ttl=50 time=15.6ms
64 bytes from newark23.linode.com (207.192.68.30): icmp_seq=16 ttl=50 time=13.0ms

The router that gave the TTL EXCEEDED error is only 8 hops from me. But I only saw it the once. Very intermittent routing issue?

Just one minute later:

--- newark23.linode.com ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19010ms
rtt min/avg/max/mdev = 11.553/14.486/18.711/1.868 ms

Did anybody look into this? i'm starting to get timeouts on my website now :(

Maybe I should open a ticket?

Am also in the UK and my Linode at Newark seems fine. Traceroutes to newark23 and newark37 (which I'm on) are fine.

Although I do run a site that switched over to a Linode yesterday. People have been complaining that they can only get on intermittently. I've seen none of it and was putting it down to the DNS changes, propagation, and all that jazz. Maybe there is a routing issue that's only manifesting itself on some UK ISPs?

@Adam_Leyshon:

Did anybody look into this? i'm starting to get timeouts on my website now

Did you post a traceroute or a MTR report showing where the problem is?

Yeah, I'm having issues as well. I'm in Massachusetts and I'm getting routed through london on the way to newark.

Traceroute:

$ traceroute tick.shadypixel.com
traceroute to tick.shadypixel.com (207.192.71.181), 30 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  7.524 ms  7.797 ms  8.100 ms
 2  10.85.0.1 (10.85.0.1)  18.497 ms  19.025 ms  19.266 ms
 3  172.20.15.49 (172.20.15.49)  22.577 ms  26.687 ms  33.031 ms
 4  172.20.15.122 (172.20.15.122)  38.309 ms  38.549 ms  38.769 ms
 5  so-7-1.car2.Boston1.Level3.net (4.79.0.89)  89.638 ms  90.021 ms  90.261 ms
 6  ae-2-5.bar2.Boston1.Level3.net (4.69.132.250)  39.770 ms  11.231 ms  57.551 ms
 7  ae-8-8.ebr1.NewYork1.Level3.net (4.69.140.98)  65.158 ms  65.784 ms  65.532 ms
 8  ae-44.ebr2.London1.Level3.net (4.69.137.77)  143.000 ms ae-42.ebr2.London1.Level3.net (4.69.137.69)  142.338 ms  142.737 ms
 9  ae-24-54.car3.London1.Level3.net (4.68.116.113)  133.206 ms  86.385 ms ae-24-56.car3.London1.Level3.net (4.68.116.177)  92.232 ms
10  195.50.112.250 (195.50.112.250)  94.435 ms  97.828 ms  101.651 ms
11  customer-side-netaccess-1-new3.new.seabone.net (195.22.216.214)  107.849 ms  119.660 ms  119.079 ms
12  0.e1-2.tbr1.mmu.nac.net (209.123.10.118)  135.944 ms  134.952 ms  135.517 ms
13  vlan803.esd2.mmu.nac.net (209.123.10.30)  136.616 ms  130.434 ms  119.702 ms
14  tick.shadypixel.com (207.192.71.181)  121.962 ms  88.866 ms  157.124 ms

Normally, my ping is under 20ms.

Edit: also, routing loops:

$ traceroute tick.shadypixel.com
traceroute to tick.shadypixel.com (207.192.71.181), 30 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  6.639 ms  6.936 ms  7.236 ms
 2  10.85.0.1 (10.85.0.1)  17.286 ms  17.692 ms  18.279 ms
 3  172.20.15.49 (172.20.15.49)  23.534 ms  27.665 ms  31.633 ms
 4  172.20.15.122 (172.20.15.122)  38.980 ms  39.220 ms  39.604 ms
 5  so-7-1.car2.Boston1.Level3.net (4.79.0.89)  41.299 ms  41.538 ms  41.923 ms
 6  ae-2-5.bar2.Boston1.Level3.net (4.69.132.250)  40.872 ms  10.864 ms  15.285 ms
 7  ae-8-8.ebr1.NewYork1.Level3.net (4.69.140.98)  33.662 ms  34.165 ms  34.526 ms
 8  ae-2.ebr1.Newark1.Level3.net (4.69.132.98)  50.493 ms  50.896 ms  51.130 ms
 9  ae-13-51.car3.Newark1.Level3.net (4.68.99.7)  45.982 ms ae-13-53.car3.Newark1.Level3.net (4.68.99.71)  85.016 ms  85.254 ms
10  TELECOM-ITA.car3.Newark1.Level3.net (4.71.148.10)  83.652 ms  84.056 ms *
11  new3-new50-racc1.new.seabone.net (195.22.216.237)  84.312 ms  84.737 ms *
12  157.130.67.177 (157.130.67.177)  18.405 ms  22.183 ms  25.944 ms
13  telecomeitalilia.alter.net (157.130.67.178)  32.920 ms  34.346 ms  39.494 ms
14  157.130.67.177 (157.130.67.177)  39.246 ms  38.828 ms  19.126 ms
15  telecomeitalilia.alter.net (157.130.67.178)  22.391 ms  26.315 ms  30.748 ms
16  157.130.67.177 (157.130.67.177)  33.938 ms  38.009 ms  45.359 ms
17  telecomeitalilia.alter.net (157.130.67.178)  43.101 ms  43.772 ms  43.522 ms
18  157.130.67.177 (157.130.67.177)  46.056 ms  45.826 ms  45.576 ms
19  telecomeitalilia.alter.net (157.130.67.178)  44.322 ms  37.373 ms  34.348 ms
20  157.130.67.177 (157.130.67.177)  29.430 ms  25.234 ms  23.023 ms
21  telecomeitalilia.alter.net (157.130.67.178)  21.712 ms  75.982 ms  75.800 ms
22  157.130.67.177 (157.130.67.177)  76.046 ms  74.490 ms  72.995 ms
23  telecomeitalilia.alter.net (157.130.67.178)  91.447 ms  91.696 ms  90.751 ms
24  157.130.67.177 (157.130.67.177)  80.077 ms  79.323 ms  78.422 ms
25  telecomeitalilia.alter.net (157.130.67.178)  80.596 ms  82.252 ms  79.241 ms
26  157.130.67.177 (157.130.67.177)  38.849 ms  37.891 ms  37.892 ms
27  telecomeitalilia.alter.net (157.130.67.178)  35.884 ms  35.884 ms  19.907 ms
28  157.130.67.177 (157.130.67.177)  34.696 ms  33.242 ms  32.669 ms
29  telecomeitalilia.alter.net (157.130.67.178)  33.857 ms  33.362 ms  33.608 ms
30  157.130.67.177 (157.130.67.177)  30.785 ms  31.010 ms  95.395 ms