Sirv incident

Elevated errors in some CDN...

Minor Resolved View vendor source →

Sirv experienced a minor incident on January 5, 2024 affecting Sirv CDN (CDN request from London), lasting 46m. The incident has been resolved; the full update timeline is below.

Started
Jan 05, 2024, 08:21 PM UTC
Resolved
Jan 05, 2024, 09:07 PM UTC
Duration
46m
Detected by Pingoru
Jan 05, 2024, 08:21 PM UTC

Affected components

Sirv CDN (CDN request from London)

Update timeline

  1. investigating Jan 05, 2024, 08:21 PM UTC

    A high number of requests to Sirv's 25 CDN locations are returning an error. Our engineers are working quickly to identify and resolve the issue.

  2. resolved Jan 05, 2024, 09:07 PM UTC

    The issue has been resolved. It was caused by the failure of a software daemon simultaneously on multiple servers. This is a lightweight and highly efficient service manager that has never failed in the past. During the period, between 3% and 58% of HTTPS requests returned an error, depending on which of the 25 CDN locations received the request. We are now investigating why this happened and will be taking actions to prevent this from impacting service availability in the future. Classified as severity level 2: Meaningful impact.