CrewAI Enterprise 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 CrewAI Enterprise Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Automations failing to be created/updatedSolved! Everything back to normal! | 31 min | Resolved |
| Sep 15, 2026 | Crew Deployments FailureThe patch have been pushed to production and the fix did work. | 2h 15m | Resolved |
| Aug 7, 2026 | Network issues in production clusterThis incident has been resolved. | 1h 44m | Resolved |
| Jul 1, 2026 | Intermittent issues with new deploymentsAll systems back to normal. | 15 min | Resolved |
| Jun 29, 2026 | Partial outage on automationsWe are investigating an issue affecting deployed automations. Some automations may be unavailable. | -24 min | Resolved |
| May 29, 2026 | Issues with the CrewAI Studio assistantThis incident has been resolved. | 1 min | Resolved |
| Mar 24, 2026 | Resolving Dependency IssuesSystems are back online, any external dependencies compromised were removed from references. - We have confirmed that no customer on SaaS have been affected by this from a security standpoint. - We have fixed the… | 3h 54m | Resolved |
| Feb 25, 2026 | Crews and Flows deployment outageThis incident has been resolved. | 51 min | Resolved |
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 CrewAI Enterprise 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 CrewAI Enterprise 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 CrewAI Enterprise 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 CrewAI Enterprise outage in this window ran 3h 54m, against a mean recovery of 1h 22m. If you depend on CrewAI Enterprise 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.