Sirv Outage History
Sirv is up right nowPingoru has recorded 36 incidents for Sirv: 19 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 11 | 15 of 720 (2%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 5 | 5 of 744 (1%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 509 (0%) |
Incidents, newest first
Minor August 13, 2026 CDN request from New York recovered –
Started Aug 13, 2026, 09:02 AM UTC· resolved Aug 13, 2026, 09:02 AM UTC
No vendor updates were posted for this incident.
Minor August 13, 2026 CDN request from Los Angeles recovered –
Started Aug 13, 2026, 08:59 AM UTC· resolved Aug 13, 2026, 08:59 AM UTC
No vendor updates were posted for this incident.
Minor August 6, 2026 Some uploads failing 5h 5m Current status by service (Sirv primary datacenter), Current status by service (Control panel at my.sirv.com), Current status by service (Sirv primary datacenter), Current status by service (Control panel at my.sirv.com)
Started Aug 06, 2026, 10:17 AM UTC· resolved Aug 06, 2026, 03:22 PM UTC
- investigating Aug 06, 2026, 10:17 AM UTC
Uploads to some Sirv accounts are failing, due to a server problem. This may also prevent images from displaying occasionally. We are working to resolve the issue as soon as possible.
- resolved Aug 06, 2026, 03:22 PM UTC
The cause of the issue was identified and it has now been fully resolved. During the period, about 25% of Sirv accounts may have experienced a proportion of file uploads failing. Retrying the uploads a short while later may have been successful because this was a only affecting a small number of requests. A review is now taking place and further information will be provided here later.
Minor June 29, 2026 CDN request from Sydney recovered –
Started Jun 29, 2026, 07:12 PM UTC· resolved Jun 29, 2026, 07:12 PM UTC
No vendor updates were posted for this incident.
Minor June 27, 2026 Control panel at my.sirv.com recovered –
Started Jun 27, 2026, 07:30 PM UTC· resolved Jun 27, 2026, 07:30 PM UTC
No vendor updates were posted for this incident.
Minor June 27, 2026 Sirv JS recovered –
Started Jun 27, 2026, 07:19 PM UTC· resolved Jun 27, 2026, 07:19 PM UTC
No vendor updates were posted for this incident.
Minor June 27, 2026 Sirv primary datacenter recovered –
Started Jun 27, 2026, 06:50 PM UTC· resolved Jun 27, 2026, 06:50 PM UTC
No vendor updates were posted for this incident.
Minor June 27, 2026 Some uploads and image processing failing due to datacentre issues 14h 29m Current status by service (Sirv primary datacenter), Current status by service (Sirv primary datacenter)
Started Jun 27, 2026, 06:34 PM UTC· resolved Jun 28, 2026, 09:03 AM UTC
- investigating Jun 27, 2026, 06:34 PM UTC
A small number of uploads and requests are returning errors due to the failure of network switches in Sirv's primary datacentre. CDN requests are working as normal. We are closely monitoring the situation and will provide updates as more information becomes available.
- investigating Jun 27, 2026, 06:34 PM UTC
A small number of uploads and requests are returning errors due to multiple network switch failures in Sirv's primary datacentre. CDN requests are working as normal. We are closely monitoring the situation and will provide updates as more information becomes available.
- resolved Jun 28, 2026, 09:03 AM UTC
This issue was caused by a core router fault affecting Sirv's primary data centre. This caused brief, intermittent outages on file storage and uploads, across all transfer types: API, S3 and FTP. Sirv automatically switched to its failover service, so file processing and delivery continued as normal. CDN requests also continued as normal. All services were restored once the datacentre had resolved the core router outage.
Minor January 30, 2026 Some slow requests in Germany 1h 42m Current status by service (Sirv primary datacenter), Current status by service (Sirv primary datacenter)
Started Jan 30, 2026, 12:46 PM UTC· resolved Jan 30, 2026, 02:28 PM UTC
- investigating Jan 30, 2026, 12:46 PM UTC
Response time for some requests in Germany are slower than normal and a small number are timing out. The issue is being investigated.
- resolved Jan 30, 2026, 02:28 PM UTC
The issue has been resolved. One of the servers serving Germany was overloaded and responding slower than usual. The server is now healthy again. We are reviewing what actions to take to reduce the chance of this happening again.
Minor March 31, 2025 Some CDN requests failing in California 44m Sirv CDN (CDN request from Los Angeles)
Started Mar 31, 2025, 02:32 PM UTC· resolved Mar 31, 2025, 03:16 PM UTC
- investigating Mar 31, 2025, 02:32 PM UTC
Some requests from California are slow and a small number (under 2%) are failing. This is being investigated and likely related to new CDN servers that were deployed today in Los Angeles.
- resolved Mar 31, 2025, 03:16 PM UTC
The issue has been resolved. The issue was caused by packet loss affecting our new Los Angeles datacenter. The datacenter traced the issue to their upstream provider, Arelion, which was experiencing network instability. The issue was resolved when Arelion was temporarily disabled as an upstream provider and traffic was rerouted through other providers. We require that our datacenters identify and reroute traffic automatically and quickly in such scenarios. However, the resolution of this issue was not fast enough and given that it occurred soon after adopting this new datacenter, we have decided to cease using it. All traffic is now being routed from our original Los Angeles datacenter (as of 7 April 2025).
Minor February 26, 2025 502 responses for some files 3m Current status by service (Sirv JS)
Started Feb 26, 2025, 09:29 AM UTC· resolved Feb 26, 2025, 09:32 AM UTC
- investigating Feb 26, 2025, 09:29 AM UTC
For a 3 minute period between 09:29 and 09:32 UTC, some requests were not returned. This issue affected only certain requests and only certain accounts. Most accounts were unaffected.
- resolved Feb 26, 2025, 09:32 AM UTC
The issue was resolved within 3 minutes. The cause was the rebooting of multiple servers at the same time, whilst only 1 server should have been rebooted. This was an oversight in our standard operating procedures. We are investigating ways to automatically protect and prevent this from recurring.
Major December 19, 2024 File uploads interrupted 3h 49m Current status by service (Sirv API), Current status by service (Control panel at my.sirv.com)
Started Dec 19, 2024, 02:20 PM UTC· resolved Dec 19, 2024, 06:09 PM UTC
- investigating Dec 19, 2024, 02:20 PM UTC
A server fault is causing some file uploads to fail for a limited number of accounts. The issue is being resolved. If you experience failed uploads, please pause and try again later.
- resolved Dec 19, 2024, 06:09 PM UTC
The issue has been resolved. An unusually large number of servers failed at the same time. Sirv is designed to continue normal operation during a server outage and all systems did continue as normal, but some file uploads failed. We are considering what possible changes could be made to assist in such situations in future.
Minor November 14, 2024 Elevated 504 responses for API upload requests 18h 50m Current status by service (Sirv API)
Started Nov 14, 2024, 09:52 AM UTC· resolved Nov 15, 2024, 04:42 AM UTC
- investigating Nov 14, 2024, 09:52 AM UTC
An elevated number of 504 timeouts are being returned for API file upload requests.
- resolved Nov 15, 2024, 04:42 AM UTC
The issue has been fully resolved. The issue started when heavy image upscaling API requests overloaded the upload API, causing some API requests to return 504 errors. This was solved but a knock-on effect caused approximately 5% of API requests to fail with a 502 response. To prevent this issue from happening again, improvements have been made to reduce the load of image upscaling and better distribute load. Changes are also being made to logging and alerting, for faster identification of such scenarios. The greatest impact of this issue was on the Sirv WordPress plugin. The plugin was sending an API request on all admin pages, which blocked the page from loading until the response had been received - typically less than 300ms but up to 20 seconds if API requests timed out. Those API requests were not required, so a new WordPress plugin version v7.3.3 was released at 1805 UTC (14 November) to remove such requests and prevent this issue from recurring: https://wordpress.org/plugins/sirv/ If you use the Sirv API, we recommend that your scripts are written to retry requests that receive a 502 response. Recommendations for handling 502 and other error responses are provided here: https://sirv.com/help/articles/sirv-rest-api/#error-handling-guide