Is Voiceflow down? › Outage history › Mar 13, 2026
Voiceflow partial outage on Mar 13, 2026: what happened
On Mar 13, 2026, the Voiceflow status page reported "Analytics degradation". About 5 hours 19 min: from Mar 13, 2026, 15:39 UTC to Mar 13, 2026, 20:58 UTC, by the official start and resolution times.
Voiceflow right now
At our last refresh (Oct 22, 2026, 12:35 UTC) Voiceflow was up: All Systems Operational.
- Started
- Mar 13, 2026, 15:39 UTC
- Resolved
- Mar 13, 2026, 20:58 UTC
- Duration
- 5 hours 19 min
- Official impact
- Major
- Source
- Analytics degradation on the Voiceflow status page
The Voiceflow status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
What caused the Voiceflow partial outage?
The Voiceflow status page has not published a cause. When it identified the problem at 15:48 UTC on Mar 13, 2026, it said: "Transcripts affected, no new logs can currently be saved. Does not affect creator, live agents."
When was it fixed?
The Voiceflow status page marked it resolved at Mar 13, 2026, 20:58 UTC, 5 hours 19 min after it started. A fix was in place and being monitored from Mar 13, 2026, 19:37 UTC. Its resolution note: "transcripts working as normal, currently recovering transcripts"
Timeline of official updates
Every update the Voiceflow status page posted, oldest first. Times are UTC.
Mar 13, 2026, 15:39 UTC investigating
Analytics data may be slow or missing during this period. Does not affect creator, live agents or transcripts.
Mar 13, 2026, 15:48 UTC identified
Transcripts affected, no new logs can currently be saved. Does not affect creator, live agents.
Mar 13, 2026, 19:37 UTC monitoring
Transcripts logs are now being properly captured, but still issues with displaying/fetching them.
Mar 13, 2026, 20:58 UTC resolved
transcripts working as normal, currently recovering transcripts
Voiceflow partial outage questions
What caused the Voiceflow partial outage on Mar 13, 2026?
The Voiceflow status page has not published a cause. When it identified the problem (Mar 13, 2026, 15:48 UTC) it said: "Transcripts affected, no new logs can currently be saved. Does not affect creator, live agents."
When was the Voiceflow partial outage on Mar 13, 2026 fixed?
The Voiceflow status page marked it resolved at Mar 13, 2026, 20:58 UTC, 5 hours 19 min after it started. A fix was in place and being monitored from Mar 13, 2026, 19:37 UTC. Its resolution note: "transcripts working as normal, currently recovering transcripts"
How long did the Voiceflow partial outage last?
About 5 hours 19 min: from Mar 13, 2026, 15:39 UTC to Mar 13, 2026, 20:58 UTC, by the official start and resolution times.
Was Voiceflow completely down?
No. The Voiceflow status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.
Other recent Voiceflow incidents
- Atlas Currently Unavailable Sep 16, 2026, 20:18 UTC, 8 hours 43 min
- Degraded Performance - Environment Creation Aug 20, 2026, 18:06 UTC, 1 hour 41 min
- Degraded Service - Knowledge Base Retrieval Jul 8, 2026, 13:28 UTC, 7 hours 12 min
- Knowledge Base Document Uploads Failing Jun 30, 2026, 16:50 UTC, 1 hour 19 min
- Project Generation via Prompt Failing Jun 3, 2026, 13:36 UTC, 1 hour 23 min
- Secrets Variable Substitution Failing Jun 3, 2026, 13:25 UTC, duration not stated
Full Voiceflow outage history and biggest outages → · Recent outages across all services →
Quotes are the Voiceflow status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Voiceflow. Times are UTC.