Home
/
Status
/
Service
Automate data processes and create workflows with Parabola.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 6m ago
3
Components
0
Active incidents
0
Maintenance
11.11%
90d uptime
Visualizations slow or failing to load
Jun 10, 5:31 PM
Normalized official status-page data for incidents, maintenance, components, and history.
11.11%
Known uptime
9 known history days
3
Components tracked
0 outage, 0 degraded
48
Incidents indexed
0 active right now
10
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Flow Builder
Operational
Flow Runs
Operational
Website
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
8
outage days
0
maintenance days
81
unknown days
Latest outages and degradations detected from the official status page.
This incident, in which visualizations were not loading or taking longer than expected to load, has been resolved. The issue was occurring for some customers from 2026-06-05 through 2026-06-10. We have solved the underlying cause and are following up with more to protect going forward.
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
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.
This incident has been stabilized and is resolved.
An outage at one of our underlying providers caused failures on Custom Transforms and Prowork steps, from 2026-05-01 16:19-16:38 UTC. The issue has been fixed and we continue to monitor.
This incident has been resolved. From 2026-04-22 23:55 UTC to 2026-04-23 02:59 UTC, users were unable to build flows using the assistive chat sidebar From 2026-04-22 23:55 UTC to 2026-04-23 03:28 UTC, flow runs were failing on custom transforms, AI transforms, and some document parsing From 2026-04-23 04:00 UTC to 2026-04-23 19:20 UTC, some flow runs failed on custom transform steps, but succeed if retried. Customers with flows that failed during that window should go ahead and re-run their flows. From 2026-04-23 19:23 UTC to 2026-04-23 19:57 UTC, users were unable to build flows using the assistive chat sidebar and flow runs were failing on custom transforms, AI transforms, and some document parsing The root-cause was a misconfiguration of our LLM provider. That has been fixed -- we are reviewing to make it more robust.
This incident has been resolved.
This incident has been resolved.
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
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
This maintenance has completed. For 3 minutes, the www.parabola.io site was unavailable, user log-in was unavailable, and webhooks were missed. Flow-building, scheduled flow runs, and all other triggers continued without any outage.
This scheduled maintenance is completed. There was not downtime or impact from this maintenance
Scheduled maintenance done -- there was no production impact during this window
The scheduled maintenance has completed. A very small number of flow runs from during this maintenance window are failing, and we are reaching out to those specific owners.
The scheduled maintenance has completed. There was no impact to availability of our application or flow-runs.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Parabola status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.parabola.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 3 of 3 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Website | Operational | Component | Not recorded |
Flow Builder | Operational | Component | Not recorded |
Flow Runs | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Parabola is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
