We started checking Demio on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Demio reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Demio's own status page declared. Below it, any public chatter we saw about Demio and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Demio's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Demio in the last 24 hours, which is not evidence that nothing is wrong.
Demio's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Demio's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Demio next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
429
US-West
100.00%
325
Europe
100.00%
298
Asia-Pacific
100.00%
181
Their declared record
Demio's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Mailing Service DegradationPartial outage
Oct 31, 2026, 9:20 AM UTC to Oct 31, 2026, 7:39 PM UTC (10h 19m)resolved
their latest update (Oct 31, 2026, 7:39 PM UTC): This incident has been resolved.
Email Delivery DelaysMinor incident
Oct 5, 2026, 3:14 PM UTC to Oct 5, 2026, 4:51 PM UTC (1h 37m)resolved
their latest update (Oct 5, 2026, 4:51 PM UTC): This incident has been resolved.
Degraded ServicesPartial outage
Aug 25, 2026, 5:56 PM UTC to Aug 25, 2026, 6:04 PM UTC (8 min)resolved
their latest update (Aug 25, 2026, 6:04 PM UTC): Resolved: User Dashboard service disruption
The issue affecting the User Dashboard has been resolved. We cleared the memory pressure on the affected ValKey cluster and restored normal service.
The User Dashboard is operating normally again, and we’re continuing to monitor the s…
Degraded ServicesMinor incident
Mar 13, 2026, 3:13 PM UTC to Mar 13, 2026, 3:30 PM UTC (17 min)resolved
their latest update (Mar 13, 2026, 3: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.
Degraded ServicesMinor incident
Jan 28, 2026, 8:40 AM UTC to Jan 28, 2026, 9:49 AM UTC (1h 9m)resolved
their latest update (Jan 28, 2026, 9:49 AM UTC): This incident has been resolved. Our investigation identified a resource bottleneck caused by heavy background processing tasks, which impacted the queue for recordings and slides.
Corrective Actions:
Resource Upgrade: We have increased the memory allocation for our processing …
Degraded ServiceMinor incident
Oct 20, 2025, 10:41 AM UTC to Oct 21, 2025, 12:51 AM UTC (14h 10m)resolved
their latest update (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.
Platform OutageMajor outage
Oct 20, 2025, 7:00 AM UTC to Oct 20, 2025, 7:00 AM UTC (0 min)resolved
their latest update (Oct 20, 2025, 7:00 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.
Landing page temporary outageMinor incident
Sep 30, 2024, 4:46 PM UTC to Sep 30, 2024, 5:30 PM UTC (44 min)resolved
their latest update (Sep 30, 2024, 5:30 PM UTC): This incident has been resolved.
My.demio.com is unstablePartial outage
Aug 21, 2024, 6:33 AM UTC to Aug 21, 2024, 6:52 AM UTC (20 min)resolved
their latest update (Aug 21, 2024, 6:52 AM UTC): This incident has been resolved.
Some join links are unable to access the roomMinor incident
Aug 20, 2024, 12:25 AM UTC to Aug 20, 2024, 9:37 AM UTC (9h 12m)postmortem published
their latest update (Aug 21, 2024, 1:07 PM UTC): ## **Summary**
* Released Webinar Room component code changes caused regression and partial outage for a specific group of users
## **Impact**
* Attendees couldn’t join some automated events properly.
* Only scheduled automated events with private chat preferences were affecte…
Showing the 10 most recent of 12 incidents Demio has declared in the history we hold.
These entries are Demio's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Demio's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.