Elucidat Outage History

13 incidents recorded over the last 365 days, 9 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.

Live Elucidat status100.00% uptime history

Every Recorded Elucidat Incident

Elucidat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 7, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
May 29, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
May 11, 2026We’re aware of an issue affecting ElucidatThis incident has been resolved44 minResolved
Apr 28, 2026Third party service is causing issues with our app.This incident has been resolved.15h 38mResolved
Apr 24, 2026We’re aware of an issue affecting ElucidatThis incident has been resolved.77h 38mResolved
Apr 13, 2026We’re aware of an issue affecting ElucidatThis incident has been resolved.42h 20mResolved
Apr 8, 2026Unable to log into the Elucidat appThis incident has been resolved.1h 10mResolved
Apr 2, 2026Unable to log into the Elucidat appThis incident has been resolved.1h 54mResolved
Mar 17, 2026Posthog service issuesOur feature flag service, Posthog is currently experiencing issues meaning that some features in Elucidat may not be available. The incident was resolved by Posthog at 11:50am GMT. Posthog incident…0 minResolved
Jan 29, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jan 28, 2026We’re aware of an issue affecting ElucidatThis incident has been resolved.2h 15mResolved
Jan 7, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 18, 2025We are aware of an issue affecting ElucidatThe Cloudflare outage is now reported as resolved.1h 50mResolved

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 Elucidat 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 Elucidat 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 Elucidat 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 Elucidat outage in this window ran 3d 5h, against a mean recovery of 11h 21m. If you depend on Elucidat 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.