Mailing List Archive

Yipes connectivity issues?
Sprintlink LookingGlass out to 209.213.221.1/32 (also a Yipes) shows an
issue too. I show LGs also for Level3 and Above.net. All show issues with
Yipes routers.

sl-bb20-chi>trace 209.213.221.1

Type escape sequence to abort.
Tracing the route to 209.213.221.1

1 sl-st20-chi-13-0.sprintlink.net (144.232.20.3) 36 msec
sl-st20-chi-12-0.sprintlink.net (144.232.8.219) 20 msec
sl-st20-chi-13-0.sprintlink.net (144.232.20.3) 40 msec
2 144.232.8.114 124 msec 8 msec 0 msec
3 ae-1-53.bbr1.Chicago1.Level3.net (4.68.101.65) [AS 3356] 0 msec 8 msec
ae-1-55.bbr1.Chicago1.Level3.net (4.68.101.129) [AS 3356] 4 msec
4 so-3-0-0.mp1.Philadelphia1.Level3.net (64.159.0.141) [AS 3356] 28 msec
60 msec
so-1-0-0.mp2.Philadelphia1.Level3.net (209.247.8.65) [AS 3356] 100 msec
5 so-10-0.hsa1.Philadelphia1.Level3.net (64.159.0.146) [AS 3356] 32 msec
28 msec 148 msec
6 unknown.Level3.net (63.209.178.162) [AS 3356] 40 msec 28 msec 44 msec
7 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) [AS 6517] 168 msec 24 msec
24 msec
8 o0-4bd1.phl004bd02.yipes.com (66.54.175.165) [AS 6517] 124 msec 64 msec
108 msec
9 o0-4bd2.phl005bd02.yipes.com (66.54.175.158) [AS 6517] 32 msec 96 msec
104 msec
10 209.213.221.1 [AS 6517] 200 msec 44 msec 60 msec
sl-bb20-chi>

Out to 66.227.46.1 from Sprint...

sl-bb20-chi>trace 66.227.46.1

Type escape sequence to abort.
Tracing the route to 66.227.46.1

1 sl-st20-chi-12-0.sprintlink.net (144.232.8.219) 12 msec
sl-st20-chi-13-0.sprintlink.net (144.232.20.3) 4 msec
sl-st20-chi-12-0.sprintlink.net (144.232.8.219) 8 msec
2 144.232.8.114 36 msec 56 msec 68 msec
3 ae-1-51.bbr1.Chicago1.Level3.net (4.68.101.1) [AS 3356] 48 msec
ae-1-55.bbr1.Chicago1.Level3.net (4.68.101.129) [AS 3356] 20 msec 12
msec
4 so-1-0-0.mp2.Philadelphia1.Level3.net (209.247.8.65) [AS 3356] 196 msec
so-3-0-0.mp1.Philadelphia1.Level3.net (64.159.0.141) [AS 3356] 36 msec
so-1-0-0.mp2.Philadelphia1.Level3.net (209.247.8.65) [AS 3356] 80 msec
5 so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) [AS 3356] 28 msec
so-10-0.hsa1.Philadelphia1.Level3.net (64.159.0.146) [AS 3356] 68 msec
so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) [AS 3356] 228 msec
6 unknown.Level3.net (63.209.178.162) [AS 3356] 220 msec 228 msec 48 msec
7 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) [AS 6517] 200 msec 212
msec 200 msec
8 o0-4bd1.phl005bd01.yipes.com (66.54.175.162) [AS 6517] 212 msec 216
msec 88 msec
9 o4-5bd1.phl038ap01.yipes.com (66.54.175.66) [AS 6517] 32 msec 44 msec
168 msec
10 o4-38ap1.phl067ap01.yipes.com (66.54.175.90) [AS 6517] 44 msec 132 msec
36 msec
11 * * *
12 *
66.54.173.62 [AS 6517] 52 msec *
sl-bb20-chi>


Going thru Above.net:

Router: mpr1.dca2.us.above.net
Command: traceroute 66.227.46.1



traceroute to 66.227.46.1 (66.227.46.1), 30 hops max, 40 byte packets
1 so-0-0-0.cr1.dca2.us.above.net (64.125.29.121) 0.568 ms 0.461 ms
0.544 ms
2 so-6-0-0.mpr1.iad1.us.above.net (64.125.28.126) 0.826 ms 0.800 ms
0.839 ms
3 so-3-0-0.mpr2.iad2.us.above.net (64.125.28.214) 0.974 ms 1.227 ms
0.981 ms
4 so-3-0-0.mpr2.iad10.us.above.net (64.125.30.121) 1.414 ms 1.529 ms
1.425 ms
5 so-2-0-0.edge2.Washington1.Level3.net (4.68.127.49) 1.559 ms 1.523 ms
1.569 ms
6 so-1-1-0.bbr2.Washington1.Level3.net (64.159.3.65) 3.894 ms
so-1-1-0.bbr1.Washington1.Level3.net (64.159.3.61) 1.952 ms 1.822 ms
7 so-1-0-0.mp1.Philadelphia1.Level3.net (209.247.8.69) 5.214 ms
so-3-0-0.mp2.Philadelphia1.Level3.net (64.159.0.142) 13.817 ms
so-1-0-0.mp1.Philadelphia1.Level3.net (209.247.8.69) 5.183 ms
8 so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) 5.166 ms
so-10-0.hsa1.Philadelphia1.Level3.net (64.159.0.146) 5.330 ms
so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) 5.185 ms
9 unknown.Level3.net (63.209.178.162) 5.468 ms 5.339 ms 5.370 ms
10 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) 391.775 ms 36.027 ms
8.147 ms
11 o0-4bd1.phl005bd01.yipes.com (66.54.175.162) 67.080 ms 5.905 ms 5.807
ms
12 o4-5bd1.phl038ap01.yipes.com (66.54.175.66) 6.971 ms 7.676 ms 7.276
ms
13 o4-38ap1.phl067ap01.yipes.com (66.54.175.90) 9.894 ms 10.450 ms 9.759
ms
14 * 66.54.173.62 (66.54.173.62) 29.631 ms *
Show Level 3 (Cincinnati, OH) Traceroute to 66.227.46.1 1
so-7-0-0.mp1.Cincinnati1.Level3.net (4.68.124.237) 0 msec 0 msec 0 msec
2 so-3-0-0.mp1.Philadelphia1.Level3.net (64.159.0.141) 28 msec
so-1-0-0.mp2.Philadelphia1.Level3.net (209.247.8.65) 28 msec
so-3-0-0.mp1.Philadelphia1.Level3.net (64.159.0.141) 28 msec
3 so-10-0.hsa1.Philadelphia1.Level3.net (64.159.0.146) 28 msec 28 msec
so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) 28 msec
4 unknown.Level3.net (63.209.178.162) 32 msec 28 msec 28 msec
5 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) [AS6517 {YIPESCOM}] 28 msec
28 msec 32 msec
6 o0-4bd1.phl005bd01.yipes.com (66.54.175.162) [AS6517 {YIPESCOM}] 28 msec
28 msec 160 msec
7 o4-5bd1.phl038ap01.yipes.com (66.54.175.66) [AS6517 {YIPESCOM}] 36 msec
28 msec 32 msec
8 o4-38ap1.phl067ap01.yipes.com (66.54.175.90) [AS6517 {YIPESCOM}] 32 msec
40 msec 32 msec
9 *
66.54.173.62 [AS6517 {YIPESCOM}] 52 msec *
Show Level 3 (Cincinnati, OH) Traceroute to 65.175.38.1

1 so-7-0-0.mp1.Cincinnati1.Level3.net (4.68.124.237) 0 msec 4 msec 0 msec
2 so-1-0-0.mp2.Philadelphia1.Level3.net (209.247.8.65) 28 msec 28 msec 32
msec
3 so-11-0.hsa1.Philadelphia1.Level3.net (64.159.0.154) 28 msec 28 msec 28
msec
4 unknown.Level3.net (63.209.178.162) 28 msec 28 msec 28 msec
5 o0-4jp1.phl004bd01.yipes.com (66.54.175.194) [AS6517 {YIPESCOM}] 28 msec
32 msec 28 msec
6 o0-4bd1.phl005bd01.yipes.com (66.54.175.162) [AS6517 {YIPESCOM}] 28 msec
36 msec 196 msec
7 o4-5bd1.phl038ap01.yipes.com (66.54.175.66) [AS6517 {YIPESCOM}] 28 msec
32 msec 28 msec
8 o4-38ap1.phl067ap01.yipes.com (66.54.175.90) [AS6517 {YIPESCOM}] 32 msec
32 msec 36 msec
9 66.7.133.154 [AS6517 {YIPESCOM}] 32 msec 80 msec 32 msec
10 * * *


----- Original Message -----
From: "Paul Laudanski" <paul@castlecops.com>
To: <outages at isotf.org>
Sent: Friday, January 19, 2007 1:59 PM
Subject: Yipes connectivity issues?


> Out to:
>
> 66.227.46.0/24
> 65.175.38.0/24
>
> It started around 8:30/9AM EST today. I'm getting consistent packet loss
> and high latency.
>
> (I won't get replies at the moment...)
>
> Paul Laudanski, Microsoft MVP Windows-Security
> Phish XML Feed: http://www.castlecops.com/article6619.html
> Phish Takedown: http://castlecops.com/pirt
> LinkedIn: http://www.linkedin.com/pub/1/49a/17b
> www.CastleCops.com | de.CastleCops.com | wiki.CastleCops.com
>
Yipes connectivity issues? [ In reply to ]
Out to:

66.227.46.0/24
65.175.38.0/24

It started around 8:30/9AM EST today. I'm getting consistent packet loss
and high latency.

(I won't get replies at the moment...)

Paul Laudanski, Microsoft MVP Windows-Security
Phish XML Feed: http://www.castlecops.com/article6619.html
Phish Takedown: http://castlecops.com/pirt
LinkedIn: http://www.linkedin.com/pub/1/49a/17b
www.CastleCops.com | de.CastleCops.com | wiki.CastleCops.com