 neftv join:2000-10-01 Broomall, PA | reply to JeepMatt
Re: [Northeast] VZ outage? Well, I am still down and can't seem to find any news about this outage. |
|
 JeepMattC'mon the UPremium join:2001-12-28 Wilmington, DE kudos:2 | The VZ Support Twitter rep opened a ticket for me - if anyone else wants to reference it when calling in:
DEDQ034BG1
Based on my line monitor here on the site, we've been down since 3am Eastern. |
|
 mking128 join:2005-08-10 College Point, NY kudos:1 Reviews:
·Verizon FiOS
·Time Warner Cable
·RoadRunner Cable
1 edit | Working out of home office today in NYC (Queens) with same 108.xx ip as before, looks okay for the most part - our speed was all over the place last night, and IHA showed possible problem on our upstream - did all the automatic routines, plus a few more. VZ's own Fios speed test this morning suggested everything is okay ("within normally acceptable ranges" of our 25/25 bundle) & my niece's kids are watching their usual cartoons this morning downstairs.
Strange enough, ran another Fios speed test to troubleshoot and IHA froze as in "not responding" once it finished the upload & download test segments & began analyzing the results, usually with its quick pop-up.
Not getting any alerts over Twitter for NYC area on this outage. (yet) VZ's rooted smartphone is on 3G, has unlimited data and if necessary, I'll fire up the unlocked tethering Apps - checking howardforum & no 4G LTE outages being reported. There's always good, old-fashion dial-up access ... LOL, how quickly we've forgotten those days.
Benchmarking to Speakeasy's test sites showed "normal" speed of 31.9/14.6
Traceroutes are "interesting" for those who wanted to check it out ...
Tracing route to www.speakeasy.net [69.17.117.156] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 12 ms 9 ms 6 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.182 .1] 3 11 ms 10 ms 11 ms G0-13-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81. 55.92] 4 10 ms 11 ms 10 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.8 1.199.12] 5 10 ms 11 ms 11 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.2.81] 6 19 ms 18 ms 15 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137 ] 7 24 ms 23 ms 22 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 8 21 ms 23 ms 24 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
9 22 ms 24 ms 25 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1 50] 10 148 ms 24 ms 37 ms ae-22-70.car2.Washington1.Level3.net [4.69.149.6 8] 11 16 ms 17 ms 16 ms ge1-1.bbsr1.iad.megapath.net [166.90.148.2] 12 144 ms 129 ms 21 ms ae1-0.c00.ash.bb.megapath.net [155.229.57.162] 13 102 ms 104 ms 104 ms ge-3-0-0-0.c01.ash.bb.megapath.net [155.229.123. 245] 14 24 ms 23 ms 22 ms ae8-0.asbnvacz-mxc2.bb.megapath.net [155.229.101 .149] 15 44 ms 46 ms 47 ms ae2-0.chcgilgb-mxc2.bb.megapath.net [155.229.101 .169] 16 108 ms 110 ms 115 ms ae1-0.sttlwawb-mxc2.bb.megapath.net [155.229.101 .113] 17 104 ms 104 ms 104 ms ae0-0.sttlwawb-mxc1.bb.megapath.net [155.229.57. 85] 18 106 ms 104 ms 104 ms ge3-0-0.m10.stl.bb.megapath.net [155.229.101.189 ] 19 101 ms 105 ms 103 ms ve191.ge0-1-0.core1.lax.megapath.net [66.80.133. 18] 20 100 ms 104 ms 104 ms 151.ge-1-3-0.sr1.sea5.speakeasy.net [69.17.82.50 ] 21 103 ms 104 ms 104 ms www.speakeasy.net [69.17.117.156]
Trace complete.
Tracing route to www.delreports.com [208.87.35.105] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 9 ms 10 ms 6 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.182 .1] 3 11 ms 11 ms 11 ms G0-13-1-7.NYCMNY-LCR-21.verizon-gni.net [130.81. 177.98] 4 10 ms 11 ms 11 ms 130.81.199.10 5 11 ms 10 ms 11 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41] 6 59 ms 53 ms 58 ms 0.ge-7-3-0.XL3.MIA4.ALTER.NET [152.63.1.110] 7 58 ms 57 ms 58 ms TenGigE0-4-4-0.GW11.MIA4.ALTER.NET [152.63.84.16 2] 8 68 ms 70 ms 67 ms Internet-gw.customer.alter.net [152.179.26.218]
9 * * * Request timed out. 10 60 ms 64 ms 65 ms 24.244.158.2 11 60 ms 64 ms 63 ms 208-87-35-105.securehost.com [208.87.35.105]
Trace complete.
Tracing route to www22.verizon.net [67.215.65.132] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 8 ms 5 ms 6 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.182 .1] 3 11 ms 11 ms 11 ms G0-13-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81. 55.92] 4 104 ms 147 ms 7 ms so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.8 1.151.224] 5 10 ms 10 ms 11 ms 0.so-4-2-0.XT2.NYC9.ALTER.NET [152.63.10.45] 6 33 ms 29 ms 8 ms 0.xe-2-1-3.XT2.NYC4.ALTER.NET [152.63.3.46] 7 8 ms 10 ms 11 ms POS7-0.GW14.NYC4.ALTER.NET [152.63.26.237] 8 8 ms 11 ms 11 ms splice-gw.customer.alter.net [157.130.94.138] 9 9 ms 15 ms 15 ms hit-nxdomain.opendns.com [67.215.65.132]
Trace complete. |
|
|
|
 neftv join:2000-10-01 Broomall, PA Reviews:
·SIP Global Phone
·QuantumVoice
| reply to JeepMatt It surprises me that Verizon does not have a backup gateway router they can swap with the one that failed. For a multibillion dollar company this should be a non-issue since 3am come on. Get off the coffee break. well this is the worst I had in an outage on the Verizon end. It had a good uptime otherwise. |
|
 JeepMattC'mon the UPremium join:2001-12-28 Wilmington, DE kudos:2 Reviews:
·Comcast
·Verizon FiOS
| reply to mking128 MKing- VERY interesting trace routes, especially the DSL Reports one.
NYC to Miami to come back to NYC?
This lends more to my hunch that there's a major issue with the primary routing point in VA that all of the Philadelphia traffic usually hits before going out to Alter.net.
It's screwing the entire Mid-atlantic.. Outage now going on 6+ hours. -- "ONE team - ONE city - ONE dream!!" |
|
 | Its back up |
|
 mking128 join:2005-08-10 College Point, NY kudos:1 Reviews:
·Verizon FiOS
·Time Warner Cable
·RoadRunner Cable
| reply to JeepMatt Things are back to normal & certainly improved, at least stats-wise. Latency from nyc to west coast servers including some of the major *.org and *.edu sites are still slow, but manageable - download is good but upload is still a bit slower here. Maybe it's a backlog from the overnight hours when many servers were busy uploading & backing up ...
Tracing route to www.speakeasy.net [69.17.117.156] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 12 ms 9 ms 6 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.182 .1] 3 11 ms 10 ms 11 ms G0-13-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81. 55.92] 4 10 ms 11 ms 10 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.8 1.199.12] 5 10 ms 11 ms 11 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.2.81] 6 19 ms 18 ms 15 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137 ] 7 24 ms 23 ms 22 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 8 21 ms 23 ms 24 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
9 22 ms 24 ms 25 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1 50] 10 148 ms 24 ms 37 ms ae-22-70.car2.Washington1.Level3.net [4.69.149.6 8] 11 16 ms 17 ms 16 ms ge1-1.bbsr1.iad.megapath.net [166.90.148.2] 12 144 ms 129 ms 21 ms ae1-0.c00.ash.bb.megapath.net [155.229.57.162] 13 102 ms 104 ms 104 ms ge-3-0-0-0.c01.ash.bb.megapath.net [155.229.123. 245] 14 24 ms 23 ms 22 ms ae8-0.asbnvacz-mxc2.bb.megapath.net [155.229.101 .149] 15 44 ms 46 ms 47 ms ae2-0.chcgilgb-mxc2.bb.megapath.net [155.229.101 .169] 16 108 ms 110 ms 115 ms ae1-0.sttlwawb-mxc2.bb.megapath.net [155.229.101 .113] 17 104 ms 104 ms 104 ms ae0-0.sttlwawb-mxc1.bb.megapath.net [155.229.57. 85] 18 106 ms 104 ms 104 ms ge3-0-0.m10.stl.bb.megapath.net [155.229.101.189 ] 19 101 ms 105 ms 103 ms ve191.ge0-1-0.core1.lax.megapath.net [66.80.133. 18] 20 100 ms 104 ms 104 ms 151.ge-1-3-0.sr1.sea5.speakeasy.net [69.17.82.50 ] 21 103 ms 104 ms 104 ms www.speakeasy.net [69.17.117.156]
Trace complete.
Tracing route to www.delreports.com [208.87.35.105] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 9 ms 10 ms 6 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.182 .1] 3 11 ms 11 ms 11 ms G0-13-1-7.NYCMNY-LCR-21.verizon-gni.net [130.81. 177.98] 4 10 ms 11 ms 11 ms 130.81.199.10 5 11 ms 10 ms 11 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41] 6 59 ms 53 ms 58 ms 0.ge-7-3-0.XL3.MIA4.ALTER.NET [152.63.1.110] 7 58 ms 57 ms 58 ms TenGigE0-4-4-0.GW11.MIA4.ALTER.NET [152.63.84.16 2] 8 68 ms 70 ms 67 ms Internet-gw.customer.alter.net [152.179.26.218]
9 * * * Request timed out. 10 60 ms 64 ms 65 ms 24.244.158.2 11 60 ms 64 ms 63 ms 208-87-35-105.securehost.com [208.87.35.105]
Trace complete. |
|
 hhahn join:2011-06-25 Marlton, NJ | reply to JeepMatt said by JeepMatt:MKing- VERY interesting trace routes, especially the DSL Reports one.
NYC to Miami to come back to NYC?
This lends more to my hunch that there's a major issue with the primary routing point in VA that all of the Philadelphia traffic usually hits before going out to Alter.net.
It's screwing the entire Mid-atlantic.. Outage now going on 6+ hours. It's interesting that you mentioned Philadelphia traffic. I'm right outside of Philly, and I connect from my home on Verizon to my office's VPN connection on Comcast. Ever since the 1 hour outage on 4/4 at midnight (discussion here), my ping has gone from an average of about 25ms to 35ms. My traffic used to be routed through VA, but now it's being routed to NY. I don't know if this is related at all to a problem in VA. |
|