Cablevision is having an outage in CT/NY right now -- intermittent connections, strange routing, etc. so I'm sure what you're seeing is related to that. Here's what we saw before (coming from Sidera in NYC going to a site in Stamford, CT - though we're having this with pretty much all sites in CT & NY): traceroute to 108.162.56.xxx (108.162.56.xxx), 30 hops max, 60 byte packets 4 172.16.0.206 (172.16.0.206) 164.413 ms 164.479 ms 164.439 ms 5 xe-8-1-1.cr1.nyc2.us.nlayer.net (69.31.95.65) 1.201 ms 1.173 ms 1.166 ms 6 vlan-78.ar2.ewr1.us.nlayer.net (69.31.34.127) 4.037 ms 3.227 ms 3.191 ms 7 451be0d5.cst.lightpath.net (65.19.113.213) 2.813 ms 2.701 ms 2.868 ms 8 64.15.0.157 (64.15.0.157) 4.695 ms 4.780 ms 4.750 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * 64.15.1.22 (64.15.1.22) 7.437 ms * 14 * * * 15 * * * 16 * * * 17 64.15.1.22 (64.15.1.22) 9.578 ms * * 18 * * * 19 * * * 20 * * * Traceroutes look better now - but reachability doesn't. -J On Tue, Aug 21, 2012 at 12:55 PM, Wallace Keith <kwallace@pcconnection.com>wrote:
Have lost connectivity to a bunch of users in CT just before noon, and again at 12:39.****
Going up and down. Can’t reach cablevision by phone (fast busy)****
** **
Tracing route to ool-4b7fe759.static.optonline.net [75.127.231.89]****
over a maximum of 30 hops:****
** **
4 3 ms 3 ms 3 ms 63.251.130.157****
5 3 ms 3 ms 3 ms 63.251.128.19****
6 3 ms 3 ms 3 ms xe-0-1-0.bos11.ip4.tinet.net [77.67.77.53]** **
7 50 ms 9 ms 9 ms xe-8-3-0.nyc30.ip4.tinet.net [89.149.183.42] ****
8 9 ms 9 ms 9 ms te0-2-0-7.ccr21.jfk07.atlas.cogentco.com[154.54.10.141] ****
9 9 ms 9 ms 9 ms te0-5-0-5.ccr21.jfk02.atlas.cogentco.com[154.54.80.173] ****
10 10 ms 9 ms 9 ms te8-1.ccr01.jfk04.atlas.cogentco.com[154.54.47.18] ****
11 * * * Request timed out.****
12 * * * Request timed out.****
13****
** **
** **
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages