Having issues from Connecticut. Seems like it's not only you. Regards, Cory Luba https://www.coryluba.com/ me@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 * 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 Outages@outages.org https://puck.nether.net/mailman/listinfo/outages