Voiceflow Outage History

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

Voiceflow incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 16, 2026Atlas Currently UnavailableAtlas is back up and fully operational. We identified and fixed an issue in our tool-schema generation that was breaking Atlas conversations, and verified it's working normally.8h 43mResolved
Aug 20, 2026Degraded Performance – Environment CreationA fix for this issue has been deployed and the issue is now resolved.1h 41mResolved
Jul 8, 2026Degraded Service – Knowledge Base RetrievalThis incident has been resolved. Knowledge Base retrieval is now functioning normally.7h 11mResolved
Jun 30, 2026Knowledge Base Document Uploads FailingThis issue has been resolved. Knowledge base uploads are now functioning normally.1h 19mResolved
Jun 3, 2026Project Generation via Prompt FailingThis incident has been resolved. Project generation is operating normally.1h 23mResolved
Jun 3, 2026Secrets Variable Substitution FailingWe experienced an incident affecting secrets. A change intended to prevent secrets from being exposed in logs inadvertently broke variable substitution in certain areas of the platform. This incident is now resolved.-2425 minResolved
May 26, 2026Widget Colour Settings Reverting to DefaultThis incident has been resolved. Widget colour settings are now correctly reflecting in production as expected.1h 49mResolved
May 8, 2026Elevated errors across Voiceflow PlatformOur services are fully operational.41h 9mResolved
Apr 17, 2026Unable to Load ProjectsThis incident has been resolved. Projects are now loading as expected.2h 24mResolved
Mar 31, 2026Chat Widgets Serving Incorrect EnvironmentThis issue has been resolved. Widgets are now correctly loading the production version of projects as expected.1h 22mResolved
Mar 13, 2026Analytics degradationtranscripts working as normal, currently recovering transcripts5h 18mResolved
Mar 12, 2026Errors When Compiling ProjectsThe issue has been resolved and services are operating normally.17h 40mResolved
Feb 27, 2026Issue with Projects and WorkspacesServices are restored.7 minResolved
Feb 23, 2026Unable to Load ProjectsServices are operational, and the incident is now resolved.36 minResolved
Feb 16, 2026Degraded Knowledge Base PerformanceThe fix has been successfully deployed and the incident is now resolved. All systems are operating normally.1h 14mResolved
Feb 12, 2026Unable to load projects on the canvasServices are restored.2h 28mResolved
Jan 30, 2026Creator is DownThe issue has been resolved. Voiceflow applied several optimizations to its internal database, and following these changes, some services temporarily stopped connecting to the transcripts database. Live agents…12 minResolved
Dec 5, 2025Partial OutageCloudflare Outage has been resolved54 minResolved
Nov 18, 2025Partial Outage[The Cloudflare outage](https://www.cloudflarestatus.com/) appears to be mostly resolved, and our services are responding and stable, we will continue monitoring the situation.3h 0mResolved

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 Voiceflow 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 Voiceflow 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 Voiceflow 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 Voiceflow outage in this window ran 1d 17h, against a mean recovery of 5h 28m. If you depend on Voiceflow 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.