Parabola had 20 outages in the last 2 years totaling 72h 13m of downtime — averaging 0.8 incidents per month.
There were 20 Parabola outages since May 22, 2025 totaling 72h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are investigating reports of increased errors for the Custom Transform step.
Our underlying LLM provider is experiencing issues. As a result, Custom Transforms are failing more frequently.
A fix has been implemented and Custom Transform executions are succeeding again.
We are currently investigating display issues of the Microsoft Sharepoint and OneDrive integrations
We have resolved the issue with editing and reviewing Microsoft integrations
Custom Transform steps are currently experiencing elevated error rates due to an upstream OpenAI error.
We are continuing to investigate this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Running flows are not finishing, which blocks further flows from running and blocks the ability to edit flows in the UI. We have identified the issue and are implementing a fix.
The flows affected by this incident are being unblocked or restarted
This incident has been resolved, flows are running again
From 2025-06-10 07:30 - 17:00 UTC, our chat side-bar and AI features had degraded or delayed performance. The root-cause was with our AI/LLM provider; we are monitoring
The parabola.io website and documentation is unavailable for many users. The root-cause is our CMS provider. The flow-builder Application, parabola.io, had some slowness and unavailability from 2025-06-03 14:00 - 17:00 UTC Scheduled flow-runs and backend processes are unaffected
The parabola.io website and documentation is unavailable for many users. The root-cause is our CMS provider. The flow-builder Application, parabola.io, had some slowness and unavailability from 2025-06-03 14:00 - 17:00 UTC Scheduled flow-runs and backend processes are unaffected
The parabola.io website is unavailable (root-cause: our CMS provider). The flow-builder Application is online after an earlier degration. Scheduled flows are unaffected.
This incident has been resolved.
From 2025-05-22 18:45 - 19:20 UTC, many customers were unable to log in to Parabola. During this time, the scheduled runs for those customers also failed. Run retries after the incident proceeded as normal; users do not need to do anything. The root cause was a coding error.