Chronograph incident

DNS provider instability

Resolved after 2 hours 7 minutes, affecting Chronograph Main API and DNSimple Name Servers, on February 10, 2026.

monitoring Feb 10, 2026, 07:36 PM UTC

We are continuing to monitor for any further issues.

Started
Feb 10, 2026, 05:35 PM UTC
Resolved
Feb 10, 2026, 07:43 PM UTC
Duration
2h 7m
Detected by Pingoru
Feb 10, 2026, 05:35 PM UTC

Affected components

Chronograph Main APIDNSimple Name Servers

Update timeline

  1. monitoring Feb 10, 2026, 05:35 PM UTC

    DNSimple is reporting infrastructure instability that is impacting some users' ability to resolve some of Chronograph's domain names. The impact appears to be inconsistent and not uniform across all users.

  2. monitoring Feb 10, 2026, 05:57 PM UTC

    DNSimple is reportedly implementing a fix. We will continue to monitor for recovery. In the meantime, we have observed that our status page (status.chronograph.pe) may not be resolving due to the same upstream issues.

  3. monitoring Feb 10, 2026, 07:04 PM UTC

    DNSimple expects to have their services restored shortly. We will continue monitoring in the meantime.

  4. monitoring Feb 10, 2026, 07:36 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 10, 2026, 07:43 PM UTC

    This incident has been resolved.

Your product runs on more than Chronograph

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 →