Parabola had 26 outages in the last 2 years totaling 55h 7m of downtime — averaging 1.1 incidents per month.
There were 26 Parabola outages since October 7, 2025 totaling 55h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
from 2026-10-05 15:52 UTC to 2026-10-05 16:03 UTC, the Prowork-building web-app was down. It has since recovered and we are monitoring & root-causing to investigate further.
This incident has been resolved.
We are investigating reports of intermittent failure with Prowork chat
We have identified the issue is with our underlying model provider. Retrying chat messages should succeed. We are continuing to investigate.
This incident has been resolved.
We are investigating an issue blocking user-login and some prowork chats, since 2026-09-08 18:10 UTC
We have mitigated the issue as of 2026-09-08 19:41 UTC and are now monitoring
This incident is now resolved. We will do a postmortem to understand.
We have identified slowness in Prowork chat completion and are continuing to investigate the impact from upstream providers on our service.
This incident has been resolved
We are investigating reports of Prowork chat slowness.
We have identified Prowork chat slowness and are pursuing changes to fix it.
A fix has been deployed as of 2026-08-03 17:40 UTC (1:40pm EDT; 10:40am PDT) -- we are monitoring to ensure prowork chats continue to improve.
This incident has been resolved.
Team is working on a resolution
Prowork chat is recovering.
Issue resolved
We are investigating reports of issues with the Custom Transform step
The issue has been identified and a fix is being implemented.
A fix has been implemented, any failing steps should succeed on next run.
The Pull From Excel step, if you build a new integration, is broken since Tuesday afternoon, 2026-06-23 4:30pm Pacific Time (2026-06-23 23:30 UTC) We are working on a fix and will have it deployed soon.
This incident has been resolved.
We're currently investigating reports of visualizations not loading, or taking longer than expected to load, within Parabola. The issue appears to be intermittent and does not affect all visualizations or all users.
The issue with visualizations has been identified and a fix is being developed
This incident has been resolved!
From 13:24 to 13:32 UTC 2026-06-09, a small number of offline/scheduled runs failed, and some flow content saves may not have synced to the editor as expected. This was due to a brief disruption in a third-party service; the underlying service has fully recovered, and our systems have been stable since 13:32 UTC with no recurrence. If you ran a flow during this window and are unsure whether it completed, we recommend checking the flow's Run History and re-running the flow is necessary.
We have detected and identified errors in chatting with the assistive chat sidebar Prowork 2026-06-02 20:20-21:10 UTC. They are now resolved; users may resume conversations
We're currently investigating reports of issues with sending and receiving emails. We're actively looking into the cause and will provide updates as we learn more.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved. Email sending through Parabola has been fully restored, and flows that send email are operating normally. Earlier today, a subset of outbound emails failed to send. We identified the cause, took corrective action, and confirmed that delivery is back to normal. We're still working to identify and resend emails that were queued or failed during the affected window. We'll follow up with impacted customers directly as we complete this cleanup.
From 2026-05-21 20:37 - 20:45 UTC, the Parabola application was unavailable and flow runs were failing. During that time, webhook flow triggers were lost. Flows can now be retried.
This incident has been stabilized and is resolved.
An outage at one of our underlying providers caused failures on Custom Transforms and Prowork steps. The issue has been fixed and we are monitoring going forward
We are currently investigating a situation where the chat assistant and custom transforms are not working, as of 2026-04-23 02:20 UTC
This incident has been resolved.
An issue at our underlying AI provider is causing increased errors in some Custom Transform and Email file-parsing steps.
This incident has been resolved.
We are investigating reports of increased failures in CSV/Excel parsing steps
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Microsoft integrations have been failing since 2026-02-03 16:00 UTC -- we have identified the cause and are working to resolve it
This incident has been resolved. Integrations with Microsoft Excel, Sharepoint, and Dynamics were failing 2026-02-03 16:00 UTC - 2026-02-04 16:19 UTC
Custom Transforms are failing to execute; we are investigating and have identified the root issue.
The fix has been deployed and the impact is over The Custom Transform step was broken from 2026-01-08 19:22 - 21:00 UTC
This incident has been fully resolved. The Custom Transform step was broken from 2026-01-08 19:22 - 21:01 UTC
There is an issue which is causing scheduled flow runs, triggered flow runs, and editing & saving flows to fail. Errors building and saving were 21:28 - 21:41 UTC 2025-12-15 . We are mitigating further impact on flow runs. Scheduled runs as of 21:28 UTC 2025-12-15 are delayed.
We are continuing to work on a fix for this issue.
A fix has been implemented and both flow building and flow runs should be fully functional. There were errors building and saving 21:28 - 21:41 UTC 2025-12-15 There were 400 Flows that have failed -- they had been scheduled for 21:28 - 22:25 UTC 2025-12-15
This incident has been resolved.
We are addressing reports of delayed runs and slower steps.
We have implemented a fix and are seeing step and flow run times return to normal levels.
Access to the Parabola application is failing as of 2025-10-31 20:38 UTC. We are investigating the root-cause and working to stabilize.
The issue is identified and stabilized. The application was inaccessible from 2025-10-31 20:37 - 20:45 UTC. The root-cause was an operations error. Webhook uploads at this time may have failed.
This incident has been resolved.
Some documentation pages were unavailable this morning
We are investigating reports of flow runs failing, starting around 2025-10-20 12:50 UTC
The issue has largely been resolved, we are continuing to monitor to confirm.
This incident has been resolved.
From 2025-10-19 00:48 - 02:09 UTC , no scheduled runs were running. This incident is now stabilized; scheduled runs have resumed. We are investigating to confirm any additional impact. The root cause was an infrastructural configuration error.