Previous incidents

The issue has been resolved. Chrome browsers started caching 307 Temporary Redirect responses, which caused a local infinite loop on the users device. 307 responses are temporary, so they should not be cached by browsers. Indeed, Sirv has always used the same 307 logic and responses have never been cached, so this may be a Chrome bug. We solved the issue by adding a header explicitly telling browsers not to cache the response. This should also prevent the issue from occurring in future.

We e...

The issue has been fully resolved.

The errors were returned by the Washington CDN server after its hard drive rapidly reached maximum capacity. Such an issue has not occurred before because each CDN server automatically deletes less-frequently accessed files, to maintain space. However, unusually heavy load of CDN MISSes outpaced the rate at which other files were deleted, causing heavy filesystem load and the failure of some requests.

The 502s occurred before the server had detected the m...

The control panel at my.sirv.com is now returning all requests as normal.

Classified as severity level 4: Minimal impact.

The issue was resolved at 1804hrs UTC, after a period of 40 minutes. The cause was a misconfiguration error in newly deployed code for improving cache logic. Additional automated and manual checks have been implemented, to prevent this from recurring.

Classified as severity level 3: Minor impact.

The sporadic API error was resolved. It impacted approximately 5% of API requests.

The issue was caused by a misconfiguration when our engineers deployed a minor update to the API. Testing of the deployment by our engineers was cut-short by a Russian missile attack on Kyiv, causing electricity and internet to be lost.

To prevent a repeat of such an issue, new deployments will now be tested by a secondary team in UK.

We would like to thank all nations who are providing air defence systems t...