Portal Home > Knowledgebase > Articles Database > Level3 Philly Issues


Level3 Philly Issues




Posted by mainarea, 01-25-2005, 12:09 AM
I was having some problems getting to Burst for a minute, and noticed the problem started at Level3 Philly, and not Burst. Looks as if Burst dropped Level3 routes and things are fine there, but here are traces from Level3 PHL: Show Level 3 (Philadelphia, PA) Traceroute to 64.191.59.235 1 fe-0-0-0.ipa1.Philadelphia1.Level3.net (209.244.24.57) 20 msec * 20 msec 2 * * * 3 * * * 4 ge-5-0-7.hsa1.Philadelphia1.Level3.net (209.244.24.58) 12 msec * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * 60 msec 17 * * * 18 * * * 19 * * * Trace to Comcast (NJ) 1 fe-0-0-0.ipa1.Philadelphia1.Level3.net (209.244.24.57) 20 msec 20 msec 20 msec 2 * * * 3 * ge-6-1-1.mp2.Philadelphia1.Level3.net (64.159.3.33) 440 msec 444 msec 4 * * * 5 ge-7-0-0-56.gar4.NewYork1.Level3.net (4.68.97.165) 436 msec ge-7-0-0-54.gar4.NewYork1.Level3.net (4.68.97.101) 440 msec ge-7-0-0-52.gar4.NewYork1.Level3.net (4.68.97.37) 444 msec Show Level 3 (Philadelphia, PA) Traceroute to google.com (216.239.37.99) 1 * fe-0-0-0.ipa1.Philadelphia1.Level3.net (209.244.24.57) 20 msec * 2 * ge-5-0-8.hsa2.Philadelphia1.Level3.net (209.244.24.62) 484 msec * 3 * * * 4 as-3-0.bbr1.Washington1.Level3.net (64.159.3.254) 480 msec 484 msec 492 msec 5 * ge-7-0.ipcolo2.Washington1.Level3.net (4.68.121.12) 488 msec * 6 unknown.Level3.net (166.90.148.174) 480 msec * 488 msec 7 216.239.46.33 488 msec 488 msec 488 msec 8 * Any ideas about these problems with Level3? - Matt

Posted by HostJedi, 01-25-2005, 02:03 AM
Supposedly they were doing maintenance, but I know we never received a notice... :-(



Was this answer helpful?

Add to Favourites Add to Favourites    Print this Article Print this Article

Also Read
ModSec POSIX Error? (Views: 726)

Language: