Incidents reported on status page for StorifyMe https://status.storifyme.com/ https://d1lppblt9t2x15.cloudfront.net/logos/4cfd9cf3fe6a30d4dd3b29fc55abb258.png https://status.storifyme.com/ en https://status.storifyme.com/ Sun, 10 May 2026 18:38:37 +0000 https://status.storifyme.com/#5ba043b1d9a0485d630305fea4925a4107122c46fe65318016030e64421587be Stories rendering engine recovered https://status.storifyme.com/ Sun, 10 May 2026 18:33:19 +0000 https://status.storifyme.com/#5ba043b1d9a0485d630305fea4925a4107122c46fe65318016030e64421587be Stories rendering engine went down https://status.storifyme.com/ Tue, 21 Apr 2026 09:51:48 +0000 https://status.storifyme.com/#b5cb2a5c45a2be3271225e86f45c254ab6114b8a2f5a47e911cd2c2a75f25a24 Stories rendering engine recovered https://status.storifyme.com/ Tue, 21 Apr 2026 09:46:40 +0000 https://status.storifyme.com/#284090d810c729abd22c2930231d493cfc620a43951ff0f94f3ca8df699c9fee API recovered https://status.storifyme.com/ Tue, 21 Apr 2026 09:43:12 +0000 https://status.storifyme.com/#b5cb2a5c45a2be3271225e86f45c254ab6114b8a2f5a47e911cd2c2a75f25a24 Stories rendering engine went down https://status.storifyme.com/ Tue, 21 Apr 2026 09:34:35 +0000 https://status.storifyme.com/#284090d810c729abd22c2930231d493cfc620a43951ff0f94f3ca8df699c9fee API went down https://status.storifyme.com/incident/848082 Thu, 12 Mar 2026 22:27:00 -0000 https://status.storifyme.com/incident/848082#3faf2d27883d58a934b1e0e7b717980711969a74ae47eb2656bc1e2bdff24b54 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.