Mighty Networks Outage History

Mighty Networks is up right now

Mighty Networks had 6 outages in the last 2 years — averaging 0.2 incidents per month.

There were 6 Mighty Networks outages since February 14, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mightynetworks.com

Minor June 15, 2026

Partial outage during Redis upgrade

Detected by Pingoru
Jun 15, 2026, 08:46 PM UTC
Resolved
Jun 15, 2026, 08:46 PM UTC
Duration
—
Affected: Netlify HostingNetlify CDNCustom DomainsSearchiOSStripemailgun APImailgun SMTPmailgun Outbound DeliveryVideo PlaybackZoomLookerwww.mightynetworks.comIntercom Web MessengerAPI AccessWeb AppIn-app NotificationsImage RenderingVideo UploadingEmail DeliveryPush NotificationsAndroidLivestreamingMighty Insights
Timeline · 2 updates
  1. identified Jun 15, 2026, 08:34 PM UTC

    Status: Identified A rolling upgrade of one of our Redis instances caused the site to begin serving errors Affected components Mighty Insights (Operational) Search (Partial outage) Looker (Operational) Intercom Web Messenger (Operational) mailgun Outbound Delivery (Operational) Stripe (Operational) Netlify Hosting (Operational) In-app Notifications (Operational) API (Public Network Feed) (Partial outage) iOS (Operational) Email Delivery (Operational) Video Playback (Operational) Livestreaming (Operational) Zoom (Operational) mailgun SMTP (Operational) mailgun API (Operational) Web App (Partial outage) Image Rendering (Operational) API Access (Partial outage) www.mightynetworks.com (Operational) Video Uploading (Operational) Custom Domains (Partial outage) Push Notifications (Operational) Android (Operational) Netlify CDN (Operational)

  2. resolved Jun 15, 2026, 08:46 PM UTC

    Status: Resolved The upgrade completed and error rates returned to zero Affected components API (Public Network Feed) (Operational) iOS (Operational) Email Delivery (Operational) Video Playback (Operational) Image Rendering (Operational) Search (Operational) mailgun API (Operational) API Access (Operational) Mighty Insights (Operational) Zoom (Operational) Video Uploading (Operational) Custom Domains (Operational) mailgun Outbound Delivery (Operational) Push Notifications (Operational) Android (Operational) Stripe (Operational) www.mightynetworks.com (Operational) Looker (Operational) mailgun SMTP (Operational) Intercom Web Messenger (Operational) In-app Notifications (Operational) Netlify Hosting (Operational) Netlify CDN (Operational) Livestreaming (Operational) Web App (Operational)

Read the full incident report →

Minor May 8, 2026

Elevated error rates

Detected by Pingoru
May 08, 2026, 07:58 PM UTC
Resolved
May 08, 2026, 07:58 PM UTC
Duration
—
Affected: Custom DomainsSearchWeb App
Timeline · 4 updates
  1. identified May 08, 2026, 01:22 AM UTC

    Status: Identified Investigating — Elevated error rates We're investigating elevated error rates on Mighty Networks caused by an ongoing AWS service incident. We're monitoring the situation and will post the next update within 30 minutes, or sooner if status changes. AWS Health Dashboard: https://health.aws.amazon.com/health/status Affected components Search (Degraded performance) Custom Domains (Degraded performance) Web App (Degraded performance) API (Public Network Feed) (Degraded performance)

  2. identified May 08, 2026, 03:31 AM UTC

    Status: Identified Update — Monitoring AWS is still experiencing the underlying incident, and we continue to see intermittent errors on Mighty Networks. We're monitoring AWS recovery. AWS Health Dashboard: https://health.aws.amazon.com/health/status Affected components Search (Degraded performance) Custom Domains (Degraded performance) Web App (Degraded performance) API (Public Network Feed) (Degraded performance)

  3. monitoring May 08, 2026, 12:44 PM UTC

    Status: Monitoring AWS has identified the cause as a thermal event that caused power loss in a single Availability Zone in US-EAST-1. Recovery is in progress but some EC2 and EBS resources remain impaired, and AWS expects full recovery to take several hours. Next AWS update by 6:30 AM PDT. We continue to see intermittent errors on Mighty Networks and are monitoring recovery. AWS Health Dashboard: https://health.aws.amazon.com/health/status Affected components Web App (Degraded performance) API (Public Network Feed) (Degraded performance) Search (Degraded performance) Custom Domains (Degraded performance)

  4. resolved May 08, 2026, 07:58 PM UTC

    Status: Resolved 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 in the background. Affected components Search (Operational) Custom Domains (Operational) Web App (Operational) API (Public Network Feed) (Operational)

Read the full incident report →

Minor April 14, 2026

We are experiencing an outage

Detected by Pingoru
Apr 14, 2026, 01:17 AM UTC
Resolved
Apr 14, 2026, 01:17 AM UTC
Duration
—
Affected: Netlify HostingNetlify CDNCustom DomainsSearchwww.mightynetworks.comWeb App
Timeline · 2 updates
  1. identified Apr 14, 2026, 01:07 AM UTC

    Status: Identified We are currently performing planned infrastructure maintenance on our production databases. Users may experience errors or degraded performance. We expect this to resolve within the next few minutes. Affected components www.mightynetworks.com (Degraded performance) Custom Domains (Full outage) Web App (Full outage) API (Public Network Feed) (Full outage) Netlify Hosting (Degraded performance) Netlify CDN (Degraded performance) Search (Full outage)

  2. resolved Apr 14, 2026, 01:17 AM UTC

    Status: Resolved The database maintenance has been completed and all services are operating normally. Affected components Netlify Hosting (Operational) Netlify CDN (Operational) Search (Operational) www.mightynetworks.com (Operational) Custom Domains (Operational) Web App (Operational) API (Public Network Feed) (Operational)

Read the full incident report →

Minor March 12, 2026

Degraded Message Delivery: Cohost

Detected by Pingoru
Mar 12, 2026, 08:14 PM UTC
Resolved
Mar 12, 2026, 08:14 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 12, 2026, 07:34 PM UTC

    Status: Investigating We are investigating reports of Cohost not responding to questions. Hosts may experience messages disappearing after being sent or not receiving expected responses. Our team is actively investigating.

  2. identified Mar 12, 2026, 07:39 PM UTC

    Status: Identified The team has narrowed down the issue and is working towards a resolution.

  3. resolved Mar 12, 2026, 08:14 PM UTC

    Status: Resolved Cohost is now operating normally. The issue has been resolved.

Read the full incident report →

Minor February 22, 2026

Errors When Loading Networks

Detected by Pingoru
Feb 22, 2026, 07:53 PM UTC
Resolved
Feb 22, 2026, 07:53 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 22, 2026, 06:42 PM UTC

    Status: Investigating We are experiencing issues loading Networks. Some users may see error messages when navigating to their network. We are working with our infrastructure provider to resolve the underlying cause.

  2. monitoring Feb 22, 2026, 07:13 PM UTC

    Status: Monitoring A fix has been applied, and loading errors have stopped. Error rates and performance have returned to normal levels. We are continuing to monitor to ensure stability.

  3. resolved Feb 22, 2026, 07:53 PM UTC

    Status: Resolved The 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 action is needed.

Read the full incident report →

Minor February 16, 2026

Some videos are failing to load

Detected by Pingoru
Feb 16, 2026, 07:45 PM UTC
Resolved
Feb 16, 2026, 07:45 PM UTC
Duration
—
Affected: Video Playback
Timeline · 6 updates
  1. investigating Feb 14, 2026, 04:25 PM UTC

    Status: Investigating We are aware that some videos are failing to load, we are actively investigating. Affected components Video Playback (Partial outage)

  2. identified Feb 15, 2026, 02:45 PM UTC

    Status: Identified We are currently experiencing an issue where videos may fail to play, affecting 10% of videos. We have restored functionality to about 40% of affected videos, and work is ongoing to restore full functionality. We expect full resolution by tomorrow and will provide further updates as progress continues. Affected components Video Playback (Partial outage)

  3. identified Feb 15, 2026, 11:00 PM UTC

    Status: Identified We are currently experiencing an issue where videos may fail to play, affecting 10% of videos. We have restored functionality to about 60% of affected videos, and work is ongoing to restore full functionality. We expect full resolution by tomorrow and will provide further updates as progress continues. Affected components Video Playback (Partial outage)

  4. identified Feb 16, 2026, 12:03 PM UTC

    Status: Identified We are currently experiencing an issue where videos may fail to play, affecting 10% of videos. We have restored functionality to about 80% of affected videos, and work is ongoing to restore full functionality. We expect full resolution by end-of-day and will provide further updates as progress continues. Affected components Video Playback (Partial outage)

  5. identified Feb 16, 2026, 06:08 PM UTC

    Status: Identified We are currently experiencing an issue where videos may fail to play, affecting 10% of videos. We have restored functionality to about 90% of affected videos, and work is ongoing to restore full functionality. We expect full resolution by end-of-day and will provide further updates as progress continues. Affected components Video Playback (Partial outage)

  6. resolved Feb 16, 2026, 07:45 PM UTC

    Status: Resolved We've restored access to the final videos, all affected videos are now available. Affected components Video Playback (Operational)

Read the full incident report →