Factory Outage History

8 incidents recorded over the last 365 days, 8 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 Factory Incident

Factory incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 18, 2026Service Disruption: User AuthenticationThe incident affecting our authentication provider, WorkOS, has been resolved. For full details regarding the resolution, please visit the WorkOS Status Page at https://status.workos.com/incidents/phs2prf38d7513 minResolved
Aug 25, 2026GLM 5.2 unavailable in our EU deploymentGLM 5.2 is available again in EU.5 minResolved
Aug 19, 2026DeepSeek V4 Flash DegradedResponse times have recovered to baseline levels.28 minResolved
Aug 11, 2026Degraded Minimax M3 availabilityMinimax M3 serving is fully restored.1h 57mResolved
Aug 7, 2026OpenAI Models Returning 431 ErrorsWe deployed a backend fix for the errors affecting OpenAI models and have confirmed that error rates returned to normal. Users can resume normal usage; no Factory CLI or Desktop update or other action is required.5h 2mResolved
Aug 1, 2026Missions API entitlement mismatchFix has been deployed in production.51 minResolved
Jul 26, 2026Login for Windows UsersWindows users faced an issue blocking login on the latest version of the Desktop App.0 minResolved
Jul 23, 2026Subscription Lifecycle Actions DownAll actions have fully recovered.20 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 Factory 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 Factory 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 Factory 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 Factory outage in this window ran 5h 2m, against a mean recovery of 1h 7m. If you depend on Factory 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.