3 ms·

So, that's why HN is unreachable from Belgium at the moment (right when I was trying to figure a dns cache problem in Firefox,of course). An ssh tunnel through

So, that's why HN is unreachable from Belgium at the moment (right when I was trying to figure a dns cache problem in Firefox,of course). An ssh tunnel through OVH/gravelines is working so far. edit: Proximus. edit2: also, Orange Mobile

iso1210 6y ago
HN working for me from the UK on BT, but traceroute showing lots of different bouncing around and a lot of different hops in the US 7 166-49-209-132.gia.bt.net (166.49.209.132) 9.877 ms 8.929 ms 166-49-209-131.gia.bt.net (166.49.209.131) 8.975 ms 8 166-49-209-131.gia.bt.net (166.49.209.131) 8.645 ms 10.323 ms 10.434 ms 9 be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 95.018 ms be3487.ccr41.lon13.atlas.cogentco.com (154.54.60.5) 7.627 ms be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 102.570 ms 10 be3627.ccr41.jfk02.atlas.cogentco.com (66.28.4.197) 89.867 ms be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 101.469 ms 101.655 ms 11 be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106) 103.990 ms 93.885 ms be3627.ccr41.jfk02.atlas.cogentco.com (66.28.4.197) 97.525 ms 12 be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158) 106.027 ms be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106) 98.149 ms 97.866 ms 13 be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 120.558 ms 122.330 ms 120.071 ms 14 be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 123.662 ms be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 128.351 ms be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 120.746 ms 15 be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 145.939 ms 137.652 ms be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 128.043 ms 16 be2930.ccr32.phx01.atlas.cogentco.com (154.54.42.77) 150.015 ms be2940.rcr51.san01.atlas.cogentco.com (154.54.6.121) 152.793 ms 152.720 ms 17 be2941.rcr52.san01.atlas.cogentco.com (154.54.41.33) 152.881 ms te0-0-2-0.rcr11.san03.atlas.cogentco.com (154.54.82.66) 153.452 ms be2941.rcr52.san01.atlas.cogentco.com (154.54.41.33) 152.054 ms 18 te0-0-2-0.rcr12.san03.atlas.cogentco.com (154.54.82.70) 162.835 ms te0-0-2-0.nr11.b006590-1.san03.atlas.cogentco.com (154.24.18.190) 146.643 ms te0-0-2-0.rcr12.san03.atlas.cogentco.com (154.54.82.70) 153.714 ms 19 te0-0-2-0.nr11.b006590-1.san03.atlas.cogentco.com (154.24.18.190) 151.212 ms 145.735 ms 38.96.10.250 (38.96.10.250) 147.092 ms 20 38.96.10.250 (38.96.10.250) 149.413 ms * *
- josephb 6y ago
  Guessing the traceroute looks a bit messy because of multiple paths being available. You can use `-q 1` to send a single traceroute probe/query instead of the default 3, it might make your traceroute look a little cleaner.
  - iso1210 6y ago
    I don't normally see multi paths for a given IP, but that aside it's bouncing through far more than I'd expect. That said, it's rare I look at traceroutes across the continental U.S, maybe that many layer 3 hops are normal, maybe routes change constantly. HN has dropped off completely from work - I see the route advertised from Level 3 (3356 21581 21581) and from Telia and onto Cogent (1299 174 21581 21581). Telia is longer, so traffic goes into to Level3 at Docklands via our 20G peer to London15, but seems to get no further. Heading to Tata in India, route out is via same peer to level3, then onto the London, Marseile, and then peers with Tata in Marseille, working fine. My gut feeling is a core problem in Level3's continental US network rather than something more global.
    - RKearney 6y ago
      This is normal for Cogent. They do per-packet load balancing across ECMP links. What you're seeing is normal for the given configuration.
deleted 6y ago
[deleted]
kuroguro 6y ago
Was down from Latvia too, up now.
sgt 6y ago
It was also down from South Africa. It's luckily up now. Gasps for breath

iso1210 6y ago

HN working for me from the UK on BT, but traceroute showing lots of different bouncing around and a lot of different hops in the US 7 166-49-209-132.gia.bt.net (166.49.209.132) 9.877 ms 8.929 ms 166-49-209-131.gia.bt.net (166.49.209.131) 8.975 ms 8 166-49-209-131.gia.bt.net (166.49.209.131) 8.645 ms 10.323 ms 10.434 ms 9 be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 95.018 ms be3487.ccr41.lon13.atlas.cogentco.com (154.54.60.5) 7.627 ms be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 102.570 ms 10 be3627.ccr41.jfk02.atlas.cogentco.com (66.28.4.197) 89.867 ms be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 101.469 ms 101.655 ms 11 be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106) 103.990 ms 93.885 ms be3627.ccr41.jfk02.atlas.cogentco.com (66.28.4.197) 97.525 ms 12 be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158) 106.027 ms be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106) 98.149 ms 97.866 ms 13 be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 120.558 ms 122.330 ms 120.071 ms 14 be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 123.662 ms be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 128.351 ms be2687.ccr41.iah01.atlas.cogentco.com (154.54.28.70) 120.746 ms 15 be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 145.939 ms 137.652 ms be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 128.043 ms 16 be2930.ccr32.phx01.atlas.cogentco.com (154.54.42.77) 150.015 ms be2940.rcr51.san01.atlas.cogentco.com (154.54.6.121) 152.793 ms 152.720 ms 17 be2941.rcr52.san01.atlas.cogentco.com (154.54.41.33) 152.881 ms te0-0-2-0.rcr11.san03.atlas.cogentco.com (154.54.82.66) 153.452 ms be2941.rcr52.san01.atlas.cogentco.com (154.54.41.33) 152.054 ms 18 te0-0-2-0.rcr12.san03.atlas.cogentco.com (154.54.82.70) 162.835 ms te0-0-2-0.nr11.b006590-1.san03.atlas.cogentco.com (154.24.18.190) 146.643 ms te0-0-2-0.rcr12.san03.atlas.cogentco.com (154.54.82.70) 153.714 ms 19 te0-0-2-0.nr11.b006590-1.san03.atlas.cogentco.com (154.24.18.190) 151.212 ms 145.735 ms 38.96.10.250 (38.96.10.250) 147.092 ms 20 38.96.10.250 (38.96.10.250) 149.413 ms * *

josephb 6y ago
Guessing the traceroute looks a bit messy because of multiple paths being available. You can use `-q 1` to send a single traceroute probe/query instead of the default 3, it might make your traceroute look a little cleaner.
- iso1210 6y ago
  I don't normally see multi paths for a given IP, but that aside it's bouncing through far more than I'd expect. That said, it's rare I look at traceroutes across the continental U.S, maybe that many layer 3 hops are normal, maybe routes change constantly. HN has dropped off completely from work - I see the route advertised from Level 3 (3356 21581 21581) and from Telia and onto Cogent (1299 174 21581 21581). Telia is longer, so traffic goes into to Level3 at Docklands via our 20G peer to London15, but seems to get no further. Heading to Tata in India, route out is via same peer to level3, then onto the London, Marseile, and then peers with Tata in Marseille, working fine. My gut feeling is a core problem in Level3's continental US network rather than something more global.
  - RKearney 6y ago
    This is normal for Cogent. They do per-packet load balancing across ECMP links. What you're seeing is normal for the given configuration.

deleted 6y ago

[deleted]

kuroguro 6y ago

Was down from Latvia too, up now.

sgt 6y ago

It was also down from South Africa. It's luckily up now. Gasps for breath