StorifyMe Outage History

StorifyMe is up right now

Pingoru has recorded 5 incidents for StorifyMe: 5 in the last 12 months and 0 in the last 90 days.

Source: status.storifyme.com

5incidents recorded
5last 12 months
0last 90 days
under a minutetypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking StorifyMe in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202620 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202610 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 523 (0%)

Incidents, newest first

Minor July 20, 2026 Stories rendering engine recovered –

Started Jul 20, 2026, 04:30 AM UTC· resolved Jul 20, 2026, 04:30 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 21, 2026 API recovered –

Started Apr 21, 2026, 09:46 AM UTC· resolved Apr 21, 2026, 09:46 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 12, 2026 DNS Resolution Issues - RESOLVED – Current status by service (API), Current status by service (Admin Portal), Current status by service (StorifyMe CDN), Current status by service (Stories rendering engine) and 6 more

Started Mar 12, 2026, 10:27 PM UTC· resolved Mar 12, 2026, 10:27 PM UTC

  1. 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 →