May 2017 - Outages - Outages Lists

Level3 Outage?
by Dan English 30 May '17

30 May '17

Seeing issues with Level3 starting around 10 PM EST in NY. Anyone else? Dan English Plexicomm - Internet Solutions dan(a)plexicomm.net | 1.866.759.4678 x103

2 1

Vodafone Wholesale VOIP Issues
by Phil Lavin 20 May '17

20 May '17

Seeing 90% packet loss to Vodafone SBCs at 195.59.158.246 and 195.59.158.230. Needless to say, calls are failing. Anyone else seeing issues?

1 1

Level3 Boston
by William Porter 18 May '17

18 May '17

Hi, is anyone seeing internet issues with Level3 in the Boston area?

2 2

Level3
by Pete Eisengrein 18 May '17

18 May '17

Lost sight of several Level3 SIP gateways 05/18/2017 09:06:36 - 09:08:52 EDT. Anyone else?

5 5

Verizon drops in Dallas to NYC ckt
by Bobin Joseph 17 May '17

17 May '17

Anybody seeing issues on connectivity going from Dallas to NYC over Verizon. We have clients that are reporting slowness. We switched traffic over our secondary provider and slowness still prevails. We started seeing lots of retransmission to clients traversing these links. Here are the hops we see that are common. Over Level3 7. AS3356 verizon-level3-2x10g.dallas3.level3.net (4.68.62.166) 8. AS??? ??? 9. AS701 gigabitethernet6-0-0.gw8.nyc8.alter.net (152.63.21.77) And over Cogent 8. AS174 verizon.dfw03.atlas.cogentco.com (154.54.12.206) 9. AS??? ??? 10. AS701 gigabitethernet7-0-0.gw8.nyc8.alter.net (152.63.21.81)

2 1

Instagram returning 503
by Grant Ridder 16 May '17

16 May '17

>From SF bay area $ curl -s -v https://www.instagram.com/ -o /dev/null * Trying 31.13.77.52... * TCP_NODELAY set * Connected to www.instagram.com (31.13.77.52) port 443 (#0) * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: *.instagram.com * Server certificate: DigiCert SHA2 High Assurance Server CA * Server certificate: DigiCert High Assurance EV Root CA > GET / HTTP/1.1 > Host: www.instagram.com > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 503 No server is available for the request < Content-Type: text/html; charset=utf-8 < Access-Control-Allow-Origin: * < Date: Tue, 16 May 2017 19:53:14 GMT < Connection: close < Content-Length: 105 < { [105 bytes data] * Curl_http_done: called premature == 0 * Closing connection 0 $ 3 207.88.13.13.ptr.us.xo.net (207.88.13.13) 5.888 ms 6.005 ms 6.104 ms 4 pax-brdr-01.inet.qwest.net (63.146.26.177) 6.080 ms 5.826 ms 6.093 ms 5 snj-edge-04.inet.qwest.net (67.14.34.82) 6.222 ms 5.976 ms 6.366 ms 6 198.233.122.154 (198.233.122.154) 9.064 ms 9.014 ms 9.403 ms 7 po131.asw04.sjc1.tfbnw.net (157.240.32.34) 6.167 ms po131.asw01.sjc1.tfbnw.net (157.240.32.28) 6.319 ms po131.asw02.sjc1.tfbnw.net (157.240.32.30) 6.201 ms 8 po231.psw02.sjc2.tfbnw.net (74.119.79.73) 5.914 ms po211.psw02.sjc2.tfbnw.net (74.119.79.59) 5.953 ms po221.psw03.sjc2.tfbnw.net (74.119.79.93) 5.863 ms 9 173.252.67.123 (173.252.67.123) 5.805 ms 5.847 ms 173.252.67.181 (173.252.67.181) 5.980 ms 10 instagram-p3-shv-01-sjc2.fbcdn.net (31.13.77.52) 5.761 ms 5.756 ms 6.044 ms

5 5

Inbound calls to CenturyLink SIP not completing
by Jim Witherell 16 May '17

16 May '17

We're having issues with inbound calls from PSTN to our SIP numbers in the 785-825 NPA-NXX. All other TNs seem OK. Anyone else seeing this? Sent from Yahoo Mail on Android

1 0

Level3 voice outage?
by Julian Y Koh 16 May '17

16 May '17

Anyone seeing issues with Level3’s voice network? We use them for long distance/international calling, and long distance at least is failing for us starting around 9:45am Central Time today. -- Julian Y. Koh Associate Director, Telecommunications and Network Services Northwestern Information Technology 2001 Sheridan Road #G-166 Evanston, IL 60208 +1-847-467-5780 Northwestern IT Web Site: <http://www.it.northwestern.edu/> PGP Public Key: <https://bt.ittns.northwestern.edu/julian/pgppubkey.html>

1 1

Re: [outages] Level3 voice outage?
by Phil Lavin 16 May '17

16 May '17

Looks OK here. Is this SIP? Which destinations are failing what response code are you getting on the failed calls? -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Julian Y Koh via Outages Sent: 16 May 2017 16:47 To: outages(a)outages.org Subject: [outages] Level3 voice outage? Anyone seeing issues with Level3’s voice network? We use them for long distance/international calling, and long distance at least is failing for us starting around 9:45am Central Time today. -- Julian Y. Koh Associate Director, Telecommunications and Network Services Northwestern Information Technology 2001 Sheridan Road #G-166 Evanston, IL 60208 +1-847-467-5780 Northwestern IT Web Site: <http://www.it.northwestern.edu/> PGP Public Key: <https://bt.ittns.northwestern.edu/julian/pgppubkey.html> _______________________________________________ Outages mailing list Outages(a)outages.org https://puck.nether.net/mailman/listinfo/outages

1 0

Akamai/GTT issues in NYC area
by Dustin Ward 14 May '17

14 May '17

We're having issues communicating with a 3rd party service utilizing Akamai over both Zayo and Level3 in the New York City area. The Akamai address (88.221.139.55) appears to go through GTT. Traceroute results from New York, NY to 88.221.139.55(a88-221-139-55.deploy.akamaitechnologies.com) 1 0.0.0.0 * * * 2 IntelQ-Tinet-level3-1ge.NewYork1.Level3.net (4.68.110.78) 0.668 ms 0.641 ms 0.788 ms 3 et-11-1-0.cr8-nyc3.ip4.gtt.net (89.149.138.213) 71.6 ms 76.3 ms 71.2 ms 4 0.0.0.0 * * * 5 0.0.0.0 * * * 6 0.0.0.0 * * * 7 0.0.0.0 * * * 8 0.0.0.0 * * * >From our Chicago facilities over both Zayo and Level3 it fully goes through Traceroute results from Chicago, IL to 88.221.139.55(a88-221-139-55.deploy.akamaitechnologies.com) 1 ae-1-3507.ear4.Chicago2.Level3.net (4.69.142.105) 0.912 ms 0.766 ms 0.803 ms 2 ae10.cr1-chi1.ip4.gtt.net (199.229.229.133) 0.815 ms 0.854 ms 0.912 ms 3 xe-2-2-0.cr0-dub2.ip4.gtt.net (89.149.186.218) 95.9 ms 95.8 ms 95.9 ms 4 as5580-gw.cr0-dub2.ip4.gtt.net (46.33.92.54) 97.4 ms 105 ms 96.6 ms 5 ae21.edge02.fra06.de.as5580.net (78.152.53.219) 113 ms 114 ms 113 ms 6 78.152.56.90 (78.152.56.90) 122 ms 118 ms 118 ms 7 a88-221-139-55.deploy.akamaitechnologies.com (88.221.139.55) 119 ms 122 ms 122 ms Anyone else having this issue?

1 0