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 * 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 200 OK < Content-Type: text/html < X-Frame-Options: SAMEORIGIN < Set-Cookie: sessionid=; expires=Thu, 01-Jan-1970 00:00:00 GMT; Max-Age=0; Path=/; HttpOnly; Domain=instagram.com < Cache-Control: private, no-cache, no-store, must-revalidate < Pragma: no-cache < Expires: Sat, 01 Jan 2000 00:00:00 GMT < Vary: Cookie, Accept-Language, Accept-Encoding < Content-Language: en < Date: Tue, 16 May 2017 20:14:23 GMT < Strict-Transport-Security: max-age=86400 < Set-Cookie: rur=ATN; Path=/ < Set-Cookie: csrftoken=1GOYmtBpg1G2OGHRDOACyFL7ETtfnuwc; expires=Tue, 15-May-2018 20:14:23 GMT; Max-Age=31449600; Path=/; Secure < Set-Cookie: mid=WRtdnwAEAAGZsOX5VR0iTFaL7Hgj; expires=Mon, 11-May-2037 20:14:23 GMT; Max-Age=630720000; Path=/ < Connection: keep-alive < Content-Length: 9426 < { [729 bytes data] * Curl_http_done: called premature == 0 * Connection #0 to host www.instagram.com left intact $
On Tue, May 16, 2017 at 1:04 PM, Izzy Goldstein - TeleGo < [email protected]> wrote: > down from NYC, on a FiOS connection > > 5xx error > > > > > > [image: Inline image 1] > > On Tue, May 16, 2017 at 3:59 PM, Keith I Myers via Outages < > [email protected]> wrote: > >> I can confirm it is down from here as well >> >> On Tue, May 16, 2017 at 3:54 PM, Grant Ridder via Outages < >> [email protected]> 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 (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 >>> >>> >>> _______________________________________________ >>> Outages mailing list >>> [email protected] >>> https://puck.nether.net/mailman/listinfo/outages >>> >>> >> >> >> -- >> >> >> [image: --] >> Keith I Myers >> [image: http://]http://KMyers.me >> +Keith I Myers <http://plus.kmyers.me/> >> Mobile : (305)-929-3475 <(305)%20929-3475> >> >> >> >> _______________________________________________ >> Outages mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/outages >> >> > > > -- > > Izzy Goldstein > > Chief Technology Officer > > Main: (212) 477-1000 x 2085 <(212)%20477-1000> > > Direct: (929) 477-2085 > > Website: www.telego.com <http://www.telego.net/> > > > <http://www.telego.com/> > > > Confidentiality Notice: This e-mail may contain confidential and/or > privileged information. If you are not the intended recipient or have > received this e-mail in error please notify us immediately by email reply > and destroy this e-mail. Any unauthorized copying, disclosure or > distribution of the material in this e-mail is strictly forbidden. Any > views or opinions presented in this email are solely those of the author > and do not necessarily represent those of TeleGo (T). Employees of TeleGo > are expressly required not to make defamatory statements and not to > infringe or authorize any infringement of copyright or any other legal > right by email communications. Any such communication is contrary to TeleGo > policy and outside the scope of the employment of the individual concerned. > TeleGo will not accept any liability in respect of such communication, and > the employee responsible will be personally liable for any damages or other > liability arising. > > > TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w> >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
