Krystal incident

DNS Issues

Resolved after 3 days 17 hours, affecting Domain Name Services, on June 4, 2026.

resolved Jun 08, 2026, 05:13 AM UTC

We're happy the DNS cluster is still returning valid records, so this issue is now being closed. Thanks for your patience.

Started
Jun 04, 2026, 12:01 PM UTC
Resolved
Jun 08, 2026, 05:13 AM UTC
Duration
3d 17h
Detected by Pingoru
Jun 04, 2026, 12:01 PM UTC

Affected components

Domain Name Services

Update timeline

  1. investigating Jun 04, 2026, 12:01 PM UTC

    We're seeing issues on Zones which has been migrated on the last couple of moved. We're seeing template Zone records being returned on the secondary nodes which is resulting in bad results for Custom records such as MX or subdomains. We're currently investigating this as a priority and will update as this is progressed.

  2. monitoring Jun 04, 2026, 12:30 PM UTC

    We have now restarted the Cache node on the secondary cluster. DNS records are now being returned as expected. We're still monitoring this though. Please note: Due to DNS caching on resolvers these can take 4 hours to propagate.

  3. resolved Jun 08, 2026, 05:13 AM UTC

    We're happy the DNS cluster is still returning valid records, so this issue is now being closed. Thanks for your patience.

Your product runs on more than Krystal

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 →