Sprint/Cogent Peering Issue?

2008-09-19 Thread Craig Holland
Hi, We are seeing traffic getting dropped between our Cogent and Sprint connect DC's. One of them is getting shutdown, so we just have a Cogent link there :| Anyone seeing anything similar? From: 91.102.40.18 traceroute to ops1.scc.rnmd.net (208.91.188.136), 30 hops max, 38 byte packets 1

Re: Sprint/Cogent Peering Issue?

2008-09-19 Thread Marshall Eubanks
No apparent problems from Cogent in Northern Virginia : tme$ traceroute ops1.scc.rnmd.net traceroute to ops1.scc.rnmd.net (208.91.188.136), 64 hops max, 40 byte packets 1 dmz-mct2 (63.105.122.1) 0.754 ms 0.278 ms 0.485 ms 2 gi0-7.na21.b002176-1.dca01.atlas.cogentco.com (38.99.206.153)

Re: Sprint/Cogent Peering Issue?

2008-09-19 Thread Roy Badami
I'm seeing issues with traceroutes dying at Sprint in London, too. From our site here in the UK (transit from NTL Telewest Business) I can't reach cisco.com (but I know cisco.com is up - I can reach it from elsewhere). Apparently customers of XS4ALL in the Netherlands are seeing similar

Re: Sprint/Cogent Peering Issue?

2008-09-19 Thread Andrew Mulholland
On Fri, Sep 19, 2008 at 06:02:37AM -0400, Marshall Eubanks wrote: No apparent problems from Cogent in Northern Virginia : Fine from Cogent in DC. Not so fine from Cogent in the Netherlands. traceroute to ops1.scc.rnmd.net (208.91.188.136), 64 hops max, 40 byte packets 1 38.105.91.2

Re: Sprint/Cogent Peering Issue?

2008-09-19 Thread Roy Badami
FWIW, the Sprint routing issues we were seeing seem to have been resolved now, AFAICS. -roy