100ms Outage History

100ms is up right now

100ms had 3 outages in the last 2 years totaling 18h 54m of downtime — averaging 0.1 incidents per month.

There were 3 100ms outages since October 11, 2025 totaling 18h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

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 →