Is AI-Media down?
Last checked 2m agoNo incidents right now.
AI-Media is operational right now. Last checked 2m ago; the most recent incident resolved 3d ago.
Real-time AI-Media status, recent outages, and incident history — pulled directly from AI-Media's official status page at https://statuspage.eegcloud.tv every 5 minutes. Pingoru tracks 18 AI-Media services and has captured 8 incidents in the last 90 days (99.81% uptime). Get email, Slack, Discord, or webhook alerts the moment AI-Media reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · Jul 30, 2026, 09:03 PM UTC
At approximately 3:15 PM EDT on July 29, an AWS host-level failure caused one Lexi worker instance to be replaced automatically. Because the instance was terminated forcefully, jobs running on it could not be requeued and were left in a state where they appeared active but were no longer producing captions. 16 jobs were affected, and captioning resumed on restart. All affected jobs have been cleared, and Lexi is operating normally.
Latest: At approximately 3:15 PM EDT on July 29, an AWS host-level failure caused one Lexi worker instance to be replaced automatically. Because the instance was terminated forcefully, job…
-
-
Timeline · 1 update
- resolved · Jul 30, 2026, 08:44 PM UTC
On July 24, an expired backend credential left the iCap Connection Stability and iCap Server Cluster Reconnects metrics blank for approximately 15 hours. This overlapped with the relay disconnects reported separately, so customers checking these metrics that morning had no visibility into connection health. Metrics for this window show a gap.
Latest: On July 24, an expired backend credential left the iCap Connection Stability and iCap Server Cluster Reconnects metrics blank for approximately 15 hours. This overlapped with the r…
-
-
Timeline · 1 update
- resolved · Jul 30, 2026, 08:43 PM UTC
At 06:56 AM EDT on July 24, an AWS routing issue in us-west-2 caused several client connections to drop across two US relays within a three minute window. All affected clients reconnected cleanly to other US relays. Sydney relays were unaffected. Connection stability returned to normal following the reconnects.
Latest: At 06:56 AM EDT on July 24, an AWS routing issue in us-west-2 caused several client connections to drop across two US relays within a three minute window. All affected clients reco…
-
- Started Jul 30, 2026, 09:03 PM UTC · Resolved Jul 29, 2026, 07:00 PM UTC · —
- System Metrics ResolvedStarted Jul 30, 2026, 08:44 PM UTC · Resolved Jul 24, 2026, 11:00 AM UTC · —
- Started Jul 30, 2026, 08:43 PM UTC · Resolved Jul 24, 2026, 11:00 AM UTC · —