Affected: Current status by service (API)Current status by service (Admin Portal)Current status by service (StorifyMe CDN)Current status by service (Stories rendering engine)Current status by service (Website)

Timeline · 1 update

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.

Read the full incident report →

Looking to track StorifyMe downtime and outages?

Pingoru polls StorifyMe's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when StorifyMe reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track StorifyMe alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring StorifyMe for free

5 free monitors · No credit card required