Chronograph incident

Incident with Amazon S3 document storage

Minor Resolved View vendor source →

Chronograph experienced a minor incident on February 10, 2026 affecting Chronograph Main API, lasting 2h 32m. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2026, 10:02 PM UTC
Resolved
Feb 11, 2026, 12:35 AM UTC
Duration
2h 32m
Detected by Pingoru
Feb 10, 2026, 10:02 PM UTC

Affected components

Chronograph Main API

Update timeline

  1. investigating Feb 10, 2026, 10:02 PM UTC

    AWS has a active issue, we are monitoring https://health.aws.amazon.com/health/status

  2. monitoring Feb 10, 2026, 10:11 PM UTC

    AWS has confirmed significant recovery for DNS resolution errors for Cloudfront distributions. Certain features of our platform rely on this to function properly and as such we have observed an increase in errors while this incident has been ongoing. We will continue to watch for AWS' full resolution of the issue.

  3. resolved Feb 11, 2026, 12:35 AM UTC

    This incident has been resolved.