Previous incidents

Some requests from Texas, Arkansas, Louisiana and Oklahoma returned a network timeout or redirect error response, due to an outdated DNS resolver. It is estimated that this affected up to 25% of requests during the period from 13:37 to 16:10 UTC.

That DNS resolver - which is outside Sirv's control - started directing a proportion of requests to a Sirv CDN server in Dallas that had been retired 4 weeks earlier. Our engineers resolved this highly unusual issue by forcing a DNS update.

To...

The issue has been resolved. Internal connectivity issues between two servers on one particular cluster had caused it. Recently uploaded files were not stored and served correctly, so returned 415 errors for those new files. Any recently uploaded images with 0 bytes should be reuploaded. Only 6 Sirv accounts were impacted and the account owners have been informed. Fewer than 0.01% of all requests to those accounts were impacted and no other accounts were impacted.