sonic having an outage?

[Kevin Prichard]

It appears that sonic.net is not routing some traffic-

$ traceroute forecast.weather.gov
traceroute: Warning: forecast.weather.gov has multiple addresses; using 165.254.58.75
traceroute to a1380.g.akamai.net (165.254.58.75), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 92.678 ms 0.786 ms 0.855 ms
2 192.168.1.254 (192.168.1.254) 1.800 ms 3.725 ms 6.394 ms
3 70-36-139-1.dsl.dynamic.sonic.net (70.36.139.1) 17.825 ms 8.584 ms 8.596 ms
4 gig1-26.cr1.colaca01.sonic.net (70.36.228.61) 6.405 ms 8.019 ms 7.518 ms
5 po3.cr1.lsatca11.sonic.net (75.101.33.166) 7.887 ms 7.874 ms 7.658 ms
6 0.xe-5-1-0.gw.pao1.sonic.net (69.12.211.1) 9.095 ms 9.707 ms 7.602 ms
7 * * *
8 * * *
9 * * *
10 * * *

[Kevin Prichard]

Aaand, it's back. Looks like an internal prob-

$ traceroute forecast.weather.gov
traceroute: Warning: forecast.weather.gov has multiple addresses; using 165.254.58.67
traceroute to a1380.g.akamai.net (165.254.58.67), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 1.472 ms 1.787 ms 1.282 ms
2 192.168.1.254 (192.168.1.254) 1.737 ms 1.849 ms 4.661 ms
3 70-36-139-1.dsl.dynamic.sonic.net (70.36.139.1) 7.164 ms 10.078 ms 9.997 ms
4 gig1-26.cr1.colaca01.sonic.net (70.36.228.61) 6.494 ms 8.260 ms 6.743 ms
5 po3.cr1.lsatca11.sonic.net (75.101.33.166) 7.505 ms 7.579 ms 7.758 ms
6 0.xe-5-1-0.gw.pao1.sonic.net (69.12.211.1) 7.889 ms 8.779 ms 7.384 ms
7 0.xe-6-1-0.gw2.200p-sf.sonic.net (64.142.0.109) 8.476 ms 8.532 ms 8.513 ms
8 as0.gw.200p-sf.sonic.net (208.106.96.249) 8.719 ms 9.658 ms 9.029 ms
9 xe-10-1-0.bar2.sanfrancisco1.level3.net (4.53.134.9) 10.360 ms 10.385 ms 9.314 ms
10 ae-6-6.ebr2.sanjose1.level3.net (4.69.140.154) 10.994 ms 11.240 ms 14.395 ms
11 ae-72-72.csw2.sanjose1.level3.net (4.69.153.22) 10.228 ms
ae-62-62.csw1.sanjose1.level3.net (4.69.153.18) 19.211 ms
ae-72-72.csw2.sanjose1.level3.net (4.69.153.22) 10.175 ms
12 ae-3-80.edge1.sanjose3.level3.net (4.69.152.144) 11.014 ms
ae-1-60.edge1.sanjose3.level3.net (4.69.152.16) 10.494 ms 10.432 ms
13 4.68.111.250 (4.68.111.250) 9.595 ms 9.357 ms
4.68.110.50 (4.68.110.50) 9.434 ms
14 ae-8.r21.snjsca04.us.bb.gin.ntt.net (129.250.5.56) 9.435 ms 9.633 ms 10.119 ms
15 ae-1.r20.sttlwa01.us.bb.gin.ntt.net (129.250.3.38) 29.054 ms 32.233 ms 29.869 ms
16 ae-1.r04.sttlwa01.us.bb.gin.ntt.net (129.250.5.43) 29.328 ms 32.277 ms 30.248 ms
17 165.254.58.67 (165.254.58.67) 31.388 ms 30.533 ms 35.138 ms

[aw]

I experienced the same thing from two sonic connections to many servers I manage. Came back up while I was on the phone with support.

[aw]

Aah, from the MOTD:
At about 3:25PM today we detected a routing issue with an upstream provider that was causing network reachability issues for our users. We have rerouted around the issue and are closely monitoring the situation. As of 3:35PM all connectivity should be restored.

-Sonic NOC