StorifyMe incident

DNS Resolution Issues - RESOLVED

Resolved on March 12, 2026, affecting section-117861 (API) and section-117861 (Admin Portal) and 1 more.

resolved Mar 12, 2026, 10:27 PM UTC

RESOLVED - Update 09:00 UTC: Issue has been resolved. Most users should now have access. DNS caches may take up to 24 hours to fully propagate. What happened? Between 03:00-09:00 UTC on March 11, we experienced intermittent DNS resolution issues due to a DNSSEC deployment timing window. Some DNS resolvers cached an intermediate configuration state, causing validation failures for a subset of users. Current status: - Issue fixed at 06:30 UTC - Most users restored by 09:00 UTC - Some ISP DNS caches may need up to 24 hours to refresh - Expected complete: March 12, 06:30 UTC Timeline: 03:00 UTC - DNSSEC deployment began 03:30 UTC - First customer reports 06:00 UTC - Root cause identified 06:30 UTC - Fix deployed 09:00 UTC - Most users restored We apologize for any inconvenience and have implemented monitoring and process improvements to prevent similar issues.

Started: Mar 12, 2026, 10:27 PM UTC
Resolved: Mar 12, 2026, 10:27 PM UTC
Duration: –
Detected by Pingoru: Mar 12, 2026, 10:27 PM UTC

Affected components

section-117861 (API)section-117861 (Admin Portal)section-117861 (StorifyMe CDN)section-117861 (Stories rendering engine)section-117861 (Website)section-117861 (API)section-117861 (Admin Portal)section-117861 (StorifyMe CDN)section-117861 (Stories rendering engine)section-117861 (Website)

Update timeline

resolved Mar 12, 2026, 10:27 PM UTC

RESOLVED - Update 09:00 UTC: Issue has been resolved. Most users should now have access. DNS caches may take up to 24 hours to fully propagate. What happened? Between 03:00-09:00 UTC on March 11, we experienced intermittent DNS resolution issues due to a DNSSEC deployment timing window. Some DNS resolvers cached an intermediate configuration state, causing validation failures for a subset of users. Current status: - Issue fixed at 06:30 UTC - Most users restored by 09:00 UTC - Some ISP DNS caches may need up to 24 hours to refresh - Expected complete: March 12, 06:30 UTC Timeline: 03:00 UTC - DNSSEC deployment began 03:30 UTC - First customer reports 06:00 UTC - Root cause identified 06:30 UTC - Fix deployed 09:00 UTC - Most users restored We apologize for any inconvenience and have implemented monitoring and process improvements to prevent similar issues.

Your product runs on more than StorifyMe

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