Looks like it is recovering as i am getting 200's consistently now
$ curl -s -v https://www.instagram.com/ -o /dev/null
* Trying 31.13.70.52...
* TCP_NODELAY set
* Connected to www.instagram.com (31.13.70.52) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
*
Getting a mix of 200s, 502s, and 503s with curl here in Indianapolis, IN,
but mostly 503s. And when it does return a 200, it seems to take awhile.
Also, can't get it to load with Chrome.
-L.
On Tue, May 16, 2017 at 3:54 PM, Grant Ridder via Outages <
outages@outages.org> wrote:
> From SF bay
I can confirm it is down from here as well
On Tue, May 16, 2017 at 3:54 PM, Grant Ridder via Outages <
outages@outages.org> wrote:
> 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
Having issues from Connecticut. Seems like it's not only you.
Regards,
Cory Luba
https://www.coryluba.com/
m...@coryluba.com
On Tue, May 16, 2017 at 3:54 PM, Grant Ridder via Outages <
outages@outages.org> wrote:
> From SF bay area
>
> $ curl -s -v https://www.instagram.com/ -o /dev/null
> *
>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
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-boun...@outages.org] On Behalf Of Julian Y Koh
via Outages
Sent: 16 May 2017 16:47
To: outages@outages.org
Subject:
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
