Sirv Outage History
Sirv is up right nowSirv had 13 outages in the last 2 years totaling 44h 42m of downtime — averaging 0.5 incidents per month.
There were 13 Sirv outages since November 14, 2024 totaling 44h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
CDN request from Los Angeles recovered
Some uploads failing
Affected: 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)
Timeline · 2 updates
- 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.
CDN request from Sydney recovered
Control panel at my.sirv.com recovered
Sirv JS recovered
Sirv primary datacenter recovered
Some uploads and image processing failing due to datacentre issues
Affected: Current status by service (Sirv primary datacenter)Current status by service (Sirv primary datacenter)
Timeline · 3 updates
- 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.
Some slow requests in Germany
Affected: Current status by service (Sirv primary datacenter)Current status by service (Sirv primary datacenter)
Timeline · 2 updates
- 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.
Some CDN requests failing in California
Affected: Sirv CDN (CDN request from Los Angeles)
Timeline · 2 updates
- 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).
502 responses for some files
Affected: Current status by service (Sirv JS)
Timeline · 2 updates
- 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.
File uploads interrupted
Affected: Current status by service (Sirv API)Current status by service (Control panel at my.sirv.com)
Timeline · 2 updates
- 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.
Elevated 504 responses for API upload requests
Affected: Current status by service (Sirv API)