Encord Outage History

12 incidents recorded over the last 365 days, 12 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 Encord status100.00% uptime history

Every Recorded Encord Incident

Encord incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026Cloud provider outage. Users unable to loginEMEA service is fully restored. No expected impacts on data integrity.5h 48mResolved
Sep 24, 2026Degraded performance across the platformWe deployed a fix that makes this operation significantly more efficient, and performance has been stable since. We apologise for the disruption.2h 59mResolved
Aug 7, 2026Degraded Data Explorer performanceResolved3h 10mResolved
Aug 7, 2026Degraded Data Explorer performanceThis incident has been resolved.21 minResolved
Aug 7, 2026Degraded Data Explorer performanceThis incident has been resolved.2 minResolved
Aug 7, 2026Degraded data explorer performancetest14 minResolved
Aug 7, 2026test incidenttest1 minResolved
Jul 31, 2026[US[ Degraded Platform PerformanceWe are currently investigating performance issues affecting the US deployment.3h 51mResolved
Jun 8, 2026Reduced stability of select data explorer functionality for some UK-hosted customersWe have resolved the issue affecting the stability of select data explorer functionality for some UK-hosted customers. All services are now operating normally.6h 31mResolved
Jun 5, 2026Degraded data explorer performanceData explorer latencies within typical range54 minResolved
Jan 9, 2026High latency across the applicationApplication latency returned to normal.-1548 minResolved
Dec 18, 2025Projects page inaccessibleAll systems working as normal-71 minResolved

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 Encord 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 Encord 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 Encord 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 Encord outage in this window ran 6h 31m, against a mean recovery of 2h 23m. If you depend on Encord 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.