At which hop do you see the trouble? All seems fine with GLBX here: [cary@proxy ~]$ traceroute carywiedemann.com traceroute to carywiedemann.com (209.9.228.68), 30 hops max, 40 byte packets 1 j-vl11-d1.acc.dca3.hopone.net (207.228.249.2) 1.314 ms 1.304 ms 1.301 ms 2 gec5.core2.dca3.hopone.net (209.160.62.113) 0.262 ms 0.266 ms 0.267 ms 3 gi5-0-0.ar2.wdc2.gblx.net (209.160.62.149) 2.296 ms 2.277 ms 2.261 ms 4 te1-1-10G.ar5.DCA3.gblx.net (67.16.160.206) 3.357 ms 3.351 ms 3.434 ms 5 GBLX.NET.PRYME.NET (67.217.175.17) 4.029 ms 4.185 ms 4.182 ms 6 PO10-40G.CR2.ASH1.NET.PRYME.NET (67.217.175.6) 157.480 ms 157.772 ms 157.730 ms 7 carywiedemann.com (209.9.228.68) 4.062 ms 4.092 ms 4.052 ms - Cary On Wed, Nov 11, 2009 at 6:58 PM, Travis Langtry <tlangtry@simplexity.com>wrote:
We are seeing the same thing. Opened a ticket with GC, but have not received any response yet.
TL
Sent from my iPhone
On Nov 11, 2009, at 6:51 PM, "Network Operations" <noc@clearrate.com> wrote:
Anyone else twisting in the wind on this? Looks like they have some ancient 7500 dying because the routing table is getting too full.
-Paul
Paul Timmins
Clear Rate Communications
Network Operations Department
Customer Support: (877) 877-4799
24 Hour Repair: (866) 366-4665
Network Operations: (877) 877-1250
www.clearrate.com
<ATT00001..txt>
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages