Demio Outage History

Demio is up right now

Demio had 3 outages in the last 2 years totaling 14h 27m of downtime — averaging 0.1 incidents per month.

There were 3 Demio outages since October 20, 2025 totaling 14h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.demio.com

Minor March 13, 2026

Degraded Services

Detected by Pingoru
Mar 13, 2026, 03:13 PM UTC
Resolved
Mar 13, 2026, 03:30 PM UTC
Duration
17m
Affected: User Dashboard
Timeline · 2 updates
  1. investigating Mar 13, 2026, 03:13 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 13, 2026, 03:30 PM UTC

    We have identified and resolved the issue affecting our systems. All services are fully operational and performing normally. We apologize for any disruption this may have caused and appreciate your patience.

Read the full incident report →

Minor October 20, 2025

Degraded Service

Detected by Pingoru
Oct 20, 2025, 10:41 AM UTC
Resolved
Oct 21, 2025, 12:51 AM UTC
Duration
14h 9m
Affected: Webinar Room APIHubSpot APIsUser DashboardWebinar Room WebSocket ServerWebinar Signaling API
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 10:41 AM UTC

    Due to Amazon Web Service outage in N.Virginia, some our services are degraded. We are actively monitoring the system

  2. monitoring Oct 20, 2025, 08:08 PM UTC

    Service recovery across all AWS services continues to improve in the affected region

  3. resolved Oct 21, 2025, 12:51 AM UTC

    As of 3:53 PM PDT, all AWS services returned to normal operations and Demio is fully operational.

Read the full incident report →

Critical October 20, 2025

Platform Outage

Detected by Pingoru
Oct 20, 2025, 07:00 AM UTC
Resolved
Oct 20, 2025, 07:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Oct 20, 2025, 10:36 AM UTC

    Amazon Web Services, the cloud provider that we use for hosting our services, partially went down in the Northern Virginia region. As a result, our application's connection to the Database was affected, and the platform temporarily went down.

Read the full incident report →