Labelbox Outage History

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

Every Recorded Labelbox Incident

Labelbox incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 26, 2026Labelbox Scheduled Maintenance Window September 26, 2026Verification is currently underway for the maintenance items.30 minScheduled
Aug 3, 2026Labeling queues in the annotation platform are degraded.We have confirmed the fix was successful and are moving the status to resolved.1h 20mResolved
Jul 11, 2026Labelbox Scheduled Maintenance Window July 11, 2026The scheduled maintenance has been completed.2h 0mScheduled
May 9, 2026Labelbox Scheduled Maintenance Window May 9, 2026The scheduled maintenance has been completed.3h 0mScheduled
Apr 13, 2026Delayed task queue updates in labeling workflowsThis incident has been resolved.5h 59mResolved
Mar 20, 2026Annotation LatencyThis incident has been resolved.54 minResolved
Feb 12, 2026Increased API LatencyThis incident has been resolved.1h 43mResolved
Jan 28, 2026Issue with logging into LabelboxThe incident has been resolved52 minResolved
Jan 17, 2026Labelbox Scheduled Maintenance Window 01/17, 2026The scheduled maintenance has been completed.30 minScheduled
Jan 10, 2026Labelbox Scheduled Maintenance Window January 10, 2026The scheduled maintenance has been completed.1h 0mScheduled
Dec 5, 2025Temporary Downtime Caused by Cloudflare IssueThis incident has been resolved.13 minResolved
Nov 15, 2025Labelbox Scheduled Maintenance Window Nov 15, 2025The scheduled maintenance has been completed.1h 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 Labelbox 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 Labelbox 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 Labelbox 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 Labelbox outage in this window ran 5h 59m, against a mean recovery of 1h 35m. If you depend on Labelbox 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.