Demio Outage History

13 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Demio Incident

Demio incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 7, 2027Regular MaintenanceWe regularly upgrade our infrastructure to maintain our services' best reliability and stability. We highly recommend to avoid running any events during the maintenance window. If you decide to run your running event…3h 0mScheduled
Jul 3, 2027Regular MaintenanceWe regularly upgrade our infrastructure to maintain our services' best reliability and stability. We highly recommend to avoid running any events during the maintenance window. If you decide to run your running event…4h 0mScheduled
Apr 3, 2027Regular MaintenanceWe regularly upgrade our infrastructure to maintain our services' best reliability and stability. We highly recommend to avoid running any events during the maintenance window. If you decide to run your running event…3h 0mScheduled
Jan 2, 2027Regular MaintenanceWe regularly upgrade our infrastructure to maintain our services' best reliability and stability. We highly recommend to avoid running any events during the maintenance window. If you decide to run your running event…4h 0mScheduled
Oct 31, 2026Mailing Service DegradationThis incident has been resolved.10h 19mResolved
Oct 5, 2026Email Delivery DelaysThis incident has been resolved.1h 36mResolved
Aug 25, 2026Degraded ServicesResolved: 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…7 minResolved
Aug 1, 2026Regular MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jul 4, 2026Regular MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Apr 4, 2026Regular MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 13, 2026Degraded ServicesWe 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.17 minResolved
Jan 28, 2026Degraded ServicesThis 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…1h 8mResolved
Jan 3, 2026Regular MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Demio incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Demio Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Demio acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Demio outage in this window ran 10h 19m, against a mean recovery of 3h 11m. If you depend on Demio in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.