Intermittent 404s on images uploaded with API

api

#1

We uploaded an image using the REST API:

https://pbs.twimg.com/media/CQVMH9eWgAAz_sl.png

The image works from some locations, but not from others. So my colleague in DC sees it fine with this header:

X-Served-By: mtc-tw-iad2-2-TWIAD2

but here in New York I get a 404:

X-Served-By: cache-tw-nyc1-cr1-20-TWNYC1

#2

My colleague in DC says it’s alternating for him between a 200 and a 404. Here are all the headers I’m seeing from New York:

$ curl -I https://pbs.twimg.com/media/CQVMH9eWgAAz_sl.png
HTTP/1.1 404 Not Found
Date: Fri, 09 Oct 2015 18:01:46 GMT
Server: tsa_b
cache-control: max-age=10, must-revalidate
content-security-policy: default-src 'none'; img-src https://abs.twimg.com https://ssl.google-analytics.com http://www.google-analytics.com; script-src https://abs.twimg.com https://ssl.google-analytics.com https://ajax.googleapis.com http://www.google-analytics.com about:; style-src https://abs.twimg.com https://fonts.googleapis.com 'unsafe-inline'; font-src https://abs.twimg.com https://twitter.com; connect-src 'none'; object-src 'none'; media-src 'none'; frame-src 'none'; report-uri https://twitter.com/i/csp_report?a=ORTGK%3D%3D%3D&ro=false
x-connection-hash: 1097495ff47a4b9d91b32924f0af209e
x-response-time: 10
x-xss-protection: 1; mode=block
Content-Type: image/png
Content-Length: 4458
Accept-Ranges: bytes
Via: 1.1 varnish
Age: 0
X-Served-By: cache-tw-nyc1-cr1-11-TWNYC1
X-Cache: MISS
X-Cache-Hits: 0
Vary: Origin,Accept-Encoding
Expires: Sat, 24 Oct 2015 18:01:46 GMT
X-Content-Type-Options: nosniff

#3

One more detail that might be relevant: we first published the containing tweet while the account was private, then took the account public after that.