100ms Outage History

100ms is up right now

100ms had 10 outages in the last 2 years totaling 23h 17m of downtime — averaging 0.4 incidents per month.

There were 10 100ms outages since August 14, 2024 totaling 23h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.100ms.live

Critical August 13, 2026

India region is facing issue for conferencing, streaming and recording

Detected by Pingoru
Aug 13, 2026, 09:41 AM UTC
Resolved
Aug 13, 2026, 01:09 PM UTC
Duration
3h 28m
Affected: APIRecordingsRooms (Conferencing system)DashboardDashboard Sample Apps
Timeline · 4 updates
  1. investigating Aug 13, 2026, 10:06 AM UTC

    There was a 10 minute downtime from 9:41 PM UTC to 9:51 PM UTC. We are investigating the root cause.

  2. investigating Aug 13, 2026, 10:15 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 13, 2026, 10:27 AM UTC

    Services are back to normal. We are monitoring the metrics

  4. resolved Aug 13, 2026, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 31, 2026

Conferencing services are not working

Detected by Pingoru
Mar 31, 2026, 05:49 AM UTC
Resolved
Mar 31, 2026, 07:14 AM UTC
Duration
1h 25m
Affected: RecordingsRooms (Conferencing system)
Timeline · 5 updates
  1. investigating Mar 31, 2026, 05:49 AM UTC

    We are currently investigating this issue.

  2. identified Mar 31, 2026, 06:21 AM UTC

    There has been an issue with our infra provider. We are fixing the issue

  3. monitoring Mar 31, 2026, 06:27 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Mar 31, 2026, 06:27 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 31, 2026, 07:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 8, 2026

Recordings are not starting

Detected by Pingoru
Jan 08, 2026, 07:00 AM UTC
Resolved
Jan 08, 2026, 09:04 AM UTC
Duration
2h 3m
Affected: Recordings
Timeline · 3 updates
  1. identified Jan 08, 2026, 08:07 AM UTC

    The issue has been identified and fix is getting implemented

  2. monitoring Jan 08, 2026, 08:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 08, 2026, 09:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 11, 2025

Users were unable to join the room in US and EU region

Detected by Pingoru
Oct 11, 2025, 05:15 AM UTC
Resolved
Oct 11, 2025, 08:40 PM UTC
Duration
15h 25m
Timeline · 1 update
  1. resolved Oct 11, 2025, 08:40 PM UTC

    A significant spike in the peer join failure metric occurred between 17:05 UTC and 18:15 UTC in US and EU region. The system stabilized and returned to normal operation at 18:15 UTC.

Read the full incident report →

Critical December 9, 2024

Session got terminated abruptly in India

Detected by Pingoru
Dec 09, 2024, 05:04 AM UTC
Resolved
Dec 09, 2024, 05:04 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 09, 2024, 06:15 AM UTC

    Sessions got terminated abruptly in India region from 10:34 AM IST to 10:38 AM IST. We have identified the root cause and deployed the fix

Read the full incident report →

Notice October 1, 2024

HLS streaming and recording down in India region

Detected by Pingoru
Oct 01, 2024, 02:30 PM UTC
Resolved
Oct 01, 2024, 03:10 PM UTC
Duration
39m
Affected: Recordings
Timeline · 4 updates
  1. investigating Oct 01, 2024, 01:07 PM UTC

    HLS streaming and recording down in India region, We suspect this due to filestore issue from GCP, We are still investigating.

  2. investigating Oct 01, 2024, 03:06 PM UTC

    The issue has been mitigated now by moving traffic to a backup cluster.

  3. investigating Oct 01, 2024, 03:08 PM UTC

    We are continuing to investigate this issue.

  4. resolved Oct 01, 2024, 03:10 PM UTC

    This incident has been resolved. We will share the RCA soon

Read the full incident report →

Notice August 28, 2024

HLS live streaming was down

Detected by Pingoru
Aug 28, 2024, 06:30 AM UTC
Resolved
Aug 28, 2024, 06:30 AM UTC
Duration
—
Timeline · 2 updates
  1. resolved Aug 28, 2024, 07:24 AM UTC

    The HLS live streaming was down from 11:41AM IST to 11:52AM IST in India region

  2. postmortem Aug 28, 2024, 10:06 AM UTC

    **Incident Summary** HLS live streaming was fully degraded from 11:40 AM IST to 11:52 AM IST on 28th August 2024. Users were seeing a black screen while streaming live sessions. **Root Cause** We use an event-driven scaling approach to scale web servers when there is a surge in requests. For web servers, we rely on Prometheus metrics for scaling up and down. During this incident, Prometheus crashed due to high memory utilization. In the event of a data source failure, we fall back to specific instances of web servers. Unfortunately, the fallback number of web server instances was inadequate to manage the volume of requests, which led to the servers being overwhelmed and ultimately crashing.

Read the full incident report →

Critical August 14, 2024

Auto start composite recordings are empty

Detected by Pingoru
Aug 14, 2024, 02:12 PM UTC
Resolved
Aug 14, 2024, 01:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 14, 2024, 02:12 PM UTC

    There was an issue with the latest web deployment, which caused the recording bot to fail in capturing the remote peers. As a result, no publishers were recorded.

Read the full incident report →

Critical August 14, 2024

Remote peers are not visible in 100ms Prebuilt App

Detected by Pingoru
Aug 14, 2024, 01:48 PM UTC
Resolved
Aug 14, 2024, 02:03 PM UTC
Duration
14m
Affected: Dashboard Sample Apps
Timeline · 4 updates
  1. investigating Aug 14, 2024, 01:48 PM UTC

    We are currently investigating this issue.

  2. identified Aug 14, 2024, 01:58 PM UTC

    We have identified the issue with the latest webapp deployment. We are reverting the deployment.

  3. monitoring Aug 14, 2024, 02:00 PM UTC

    We have reverted the web app deployment and monitoring it.

  4. resolved Aug 14, 2024, 02:03 PM UTC

    The incident has been resolved

Read the full incident report →