[outages] route-views.org routing loop?
John Kemp
kemp at network-services.uoregon.edu
Mon Jun 27 13:14:58 EDT 2016
Campus outage. They're back now.
John Kemp
help at routeviews.org
On 6/27/16 10:00 AM, Hugo Slabbert via Outages wrote:
>
> On Mon 2016-Jun-27 09:42:42 -0700, Peter Kranz via Outages
> <outages at outages.org> wrote:
>> Other people seeing routing loops to route-views.routeviews.org? Seem
>> sporadic.. Also periods of high packet loss. Similar behavior to
>> route-views2 and route-views3
>>
>
> Seeing fishiness here as well; A and AAAA records bouncing around (was
> 64.151.82.184 initially with no AAAA; then 128.223.51.103 &
> 2001:468:d01:33::80df:3367). Not sure if they're round-robining, but
> the single/dual-stack in returned records was odd.
>
> 64.151.82.184 went through HE via the SIX then Zayo, but died
> somewhere in ServePath before it got to UOregon:
>
> $ traceroute 64.151.82.184
> traceroute to 64.151.82.184 (64.151.82.184), 30 hops max, 60 byte packets
> 1 gateway (10.255.1.254) 0.290 ms 0.266 ms 0.259 ms
> 2 10.255.0.1 (10.255.0.1) 0.680 ms 0.659 ms 0.657 ms
> 3 ae0-757.cr0.bby0.as19171.net (208.65.235.233) 0.988 ms 0.990 ms
> 0.978 ms
> 4 v523.core1.yvr1.he.net (65.49.89.9) 50.988 ms 50.899 ms 51.073 ms
> 5 100ge4-2.core1.sea1.he.net (184.105.64.109) 4.405 ms 4.510 ms
> 4.510 ms
> 6 six.zayo.com (206.81.80.19) 4.823 ms 4.644 ms 4.611 ms
> 7 ae27.cs1.sea1.us.eth.zayo.com (64.125.29.0) 21.718 ms 21.917 ms
> 21.910 ms
> 8 ae0.cs2.sea1.us.eth.zayo.com (64.125.29.47) 32.747 ms 28.681 ms
> 32.713 ms
> 9 ae3.cs2.sjc2.us.eth.zayo.com (64.125.29.40) 26.116 ms 54.101 ms
> 54.052 ms
> 10 ae27.cr2.sjc2.us.zip.zayo.com (64.125.30.233) 23.037 ms 23.177
> ms 23.156 ms
> 11 ae3.er2.sjc2.us.zip.zayo.com (64.125.28.57) 22.164 ms 22.137 ms
> 22.155 ms
> 12 te-4-1.border-core1.sfo2.servepath.net (64.124.196.6) 22.981 ms
> 22.920 ms 23.018 ms
> 13 vl22.access17.sfo2.servepath.com (208.96.31.18) 23.602 ms 23.480
> ms 23.494 ms
> 14 * * *
> 15 * * *
> 16 * * *
> 17 * * *
> 18 * * *
> 19 * * *
> 20 * * *
> 21 * * *
> 22 * * *
> 23 * * *
> 24 * * *
> 25 * * *
> 26 * * *
> 27 * * *
> 28 * * *
> 29 * * *
> 30 * * *
>
> 128.223.51.103 and 2001:468:d01:33::80df:3367 go through Nero @ the
> SIX, then to UONET:
>
> My traceroute [v0.86]
> sg-ws-hugol
> (::) Mon
> Jun 27 09:56:20 2016
> Keys: Help Display mode Restart statistics Order of fields quit
> Packets Pings
> Host Loss% Snt Drop Last
> Avg Best Wrst StDev Jttr Javg
> 1. 2607:4100:1::1 34.5% 416 143 0.7
> 0.6 0.5 1.0 0.0 0.1 0.1
> 2. 2607:4100:0:4::1 0.0% 416 0 1.1
> 1.1 0.8 10.4 0.7 0.0 0.4
> 3. v6-seattleix.nero.net 7.7% 416 32 9.3
> 9.2 8.9 11.9 0.1 0.0 0.1
> 4. eugn-core2-gw.nero.net 2.9% 416 12 11.8
> 11.7 11.5 15.7 0.2 0.1 0.2
> 5. eugn-car1-gw.nero.net 0.0% 416 0 11.7
> 11.5 10.9 49.7 3.4 0.5 1.0
> 6. uoregon2.nero.net 2.2% 416 9 11.7
> 11.8 11.5 17.1 0.4 0.7 0.4
> 7. vl-2-gw.uoregon.edu 6.7% 415 28 12.4
> 503.2 11.3 4425. 972.9 0.9 47.8
> 8. route-views.routeviews.org 70.6% 415 293 84.0
> 19375 12.3 16697 31799 22.4 4257
>
> Telnet to 2001:468:d01:33::80df:3367 as dog slow a few minutes ago but
> did eventually connect. It's starting to be quicker on connect and
> initial banners now.
>
More information about the Outages
mailing list