Sirv incident

502 responses for some files

Resolved after 3 minutes, affecting section-2713 (Sirv JS), on February 26, 2025.

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.

Started
Feb 26, 2025, 09:29 AM UTC
Resolved
Feb 26, 2025, 09:32 AM UTC
Duration
3m
Detected by Pingoru
Feb 26, 2025, 09:29 AM UTC

Affected components

section-2713 (Sirv JS)

Update timeline

  1. 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.

  2. 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.

Your product runs on more than Sirv

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →