Mighty Networks Outage History
33 incidents recorded over the last 365 days, 31 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Mighty Networks Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 5, 2026 | Mighty Insights™ UpdatesMaintenance has started | 1h 4m | Resolved |
| Oct 13, 2026 | Mighty Insights™ UpdatesMaintenance has started | 4h 4m | Resolved |
| Sep 14, 2026 | Mighty Insights™ UpdatesMaintenance has started | 30h 6m | Resolved |
| Sep 1, 2026 | Intermittent issues with images uploading and displayingThis issue has now been resolved. Image uploads, previews, and image display across the platform are working normally again. | 1h 30m | Resolved |
| Aug 24, 2026 | Mighty Insights™ UpdatesMaintenance has started | 32h 34m | Resolved |
| Aug 13, 2026 | Email Delivery issuesThis issue has been resolved. | 1h 40m | Resolved |
| Jul 8, 2026 | Elevated Error RatesThe issue has been resolved. | 2h 13m | Resolved |
| Jun 15, 2026 | Partial outage during Redis upgradeThe upgrade completed and error rates returned to zero | -29 min | Resolved |
| Jun 8, 2026 | Mighty Insights™ UpdatesTo roll out some new updates, Mighty Insights™ will be unavailable for a brief period. | 26h 0m | Scheduled |
| May 8, 2026 | Elevated error rates**Resolved** Mighty Networks has been operating normally now. While the underlying AWS incident is still ongoing, it is no longer impacting our service. We're marking this incident resolved and will continue to monitor… | 18h 35m | Resolved |
| Apr 27, 2026 | Mighty Insights™ UpdatesTo release some new updates, Mighty Insights™ will be inaccessible for a brief period. | 29h 3m | Scheduled |
| Apr 14, 2026 | We are experiencing an outageThe database maintenance has been completed and all services are operating normally. | 10 min | Resolved |
| Mar 12, 2026 | Degraded Message Delivery: CohostCohost is now operating normally. The issue has been resolved. | 40 min | Resolved |
| Feb 22, 2026 | Errors When Loading NetworksThe issue causing errors when loading Networks has been resolved. The root cause was a vendor infrastructure event that impacted our search service. A fix was applied and error rates have returned to normal. No further… | 1h 11m | Resolved |
| Feb 14, 2026 | Some videos are failing to loadWe've restored access to the final videos, all affected videos are now available. | 51h 19m | Resolved |
| Jan 27, 2026 | Issues loading Mighty NetworksOur third-party network provider, Cloudflare, has resolved the issue that was preventing the remaining Mighty Networks with Custom Domains mapped with A records from loading. We are marking this incident as resolved. | -2276161 min | Resolved |
| Jan 27, 2026 | Image service provider service disruptionThis incident has been resolved. | -2345741 min | Resolved |
| Jan 27, 2026 | Mighty Networks with Custom Domains registered through Cloudflare are having issuesThe team has surfaced an issue that was affecting some Mighty Networks that have Custom Domains registered through Cloudflare. We have investigated, found the root of the issue and have put out a fix. | -2359737 min | Resolved |
| Jan 27, 2026 | Issues with Mighty InsightsThis issue has been resolved by our third party data warehousing partner. Mighty Insights functionality has returned to normal. | -1952521 min | Resolved |
| Jan 27, 2026 | Issues with Email notificationsEmail notification delivery is back to normal. | -2067648 min | Resolved |
| Jan 27, 2026 | Issues loading Mighty NetworksOur CDN implemented a fix and let us know that all systems are operational. | -2076037 min | Resolved |
| Jan 27, 2026 | Issues with notificationsWe have resolved the issue and all notifications are going out as expected. Some notifications were delayed and will be sent out within the couple hours. | -2136237 min | Resolved |
| Jan 27, 2026 | Issues with LivestreamingAll Live recording notifications were sent out | -2175582 min | Resolved |
| Jan 27, 2026 | Issues loading Mighty NetworksSome Networks experiencing errors loading on the Web. We were able to deploy a fix. | -2223130 min | Resolved |
| Jan 27, 2026 | Email notifications are delayedEmail notification delivery is back to normal. | -2227341 min | Resolved |
| Jan 27, 2026 | Homepage CDN Provider intermittent errorsOur CDN Provider, Netlify had degraded performance causing some errors when loading pages on the Homepage. (see https://www.netlifystatus.com/) | -2237897 min | Resolved |
| Jan 27, 2026 | Issue with Mighty Networks websiteThis incident has been resolved. | -1814473 min | Resolved |
| Jan 27, 2026 | Issues with notification emailsThis incident has been resolved. | -1821405 min | Resolved |
| Jan 27, 2026 | Issues with requests producing errorsThe incident has been resolved. | -1830308 min | Resolved |
| Jan 27, 2026 | Issue with Realtime ProviderOur realtime provider was down due to an AWS power outage that may have caused a brief disruption to chats, notifications, and synchronization in realtime. The service has since been restored and no content was lost. | -1841727 min | Resolved |
| Jan 27, 2026 | Issues accessing NetworksThere was an issue early on 6/21/22 with accessing Networks and down time on the platform. Our web host implemented a fix that has resolved the issue. | -1895667 min | Resolved |
| Jan 27, 2026 | Issues with emailsThis incident has been resolved. | -1912520 min | Resolved |
| Jan 27, 2026 | Some email notifications are delayedWe are marking this incident as resolved as the error rates have subsided. | -1942318 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Mighty Networks incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Mighty Networks Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Mighty Networks acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Mighty Networks outage in this window ran 2d 3h, against a mean recovery of 14h 18m. If you depend on Mighty Networks in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.