Paragon had 37 outages in the last 2 years totaling 171h 6m of downtime — averaging 1.5 incidents per month.
There were 37 Paragon outages since May 23, 2024 totaling 171h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
Issue identified and resolved. No disruption to any services, workflows, actions, or syncs occurred during the incident time period - only dashboard was unavailable.
This incident has been resolved.
Some Paragon features are currently affected by the ongoing Github outage and are not functional at the moment.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Paragon is currently affected by the ongoing Cloudflare outage. Critical functions including Dashboard, Connect API, ActionKit, and Connect Portal are experiencing significantly degraded performance. More information regarding this outage can be found here: https://www.cloudflarestatus.com/
We are continuing to work on a fix for this issue.
This incident has been resolved.
Paragon is currently experiencing task history performance issues, including Event Logs, alongside dashboard slowness in the UX. We have identified the issue and are working towards an expedient resolution.
We are continuing to work on a fix for this issue.
Event logs functionality has returned to normal. We are still seeing some lingering issues with task history and UX slowness, and will continue to update as functionality fully returns.
This incident has been resolved.
We are seeing degraded performance in some Paragon services, including the dashboard and task history. We are investigating and will update this page accordingly.
This incident has been resolved.
Paragon is currently experiencing widespread latency while trying to load Paragon dashboard components. We are investigating and will update this page accordingly as we investigate this issue.
This incident has been resolved.
We experienced downtime on the dashboard along with some API timeouts. Our team is actively investigating the root cause and working on mitigation.
We have identified the root cause of the issue. Our team is currently monitoring the results to ensure stability.
This incident has been resolved.
We’re currently investigating an issue where Task History is not displaying new executions in the UI. Executions are processing correctly, but there are delays affecting their visibility in the UI.
This incident has been resolved.
We have identified an issue with Triggers in our system not executing as expected, specifically affecting app-event, custom-trigger and cron-based triggers. Our engineering team is actively investigating the root cause and working on a fix.
This incident has been resolved, affected workflow services have been fully restored. Impacted customer workflows will be notified about retry options to minimize impact.
We have identified an issue with Jira Search Actions and Triggers resulting in elevated error rates in ActionKit and Workflows using the following Actions or Triggers: - Actions: Search Issues by JQL, Search Issues - Triggers: Issue Created, Issue Updated, Comment Created These Actions or Triggers may fail with the following error: "The requested API has been removed." The issue is related to a dependency on deprecated API endpoints. We have a fix in progress and will provide an update once released.
The update to the Jira integration has been released, and functionality for all affected Actions and Triggers has been restored.
Some customers hosted in AWS EU cloud may see degraded workflow performance. We have identified the root cause and are deploying a fix.
This incident has been resolved.
We are seeing degraded performance for a limited scope of Paragon customers. Some workflows may fail. We are investigating and will continue to provide updates as we near resolution.
We are continuing to investigate this issue.
This incident has been resolved. Impacted customers will be notified.
Paragon services are currently experiencing degraded performance, including dashboard latency issues and long workflow queue times. API requests for api.useparagon.com and zeus.useparagon.com. Dashboard views, Connect Portal requests, and other requests to the API may fail to load due to request failures. We have identified multiple causes on this issue and are working to resolve ASAP.
This incident has been resolved as of 9:57am PST.
From 7:38am to 7:44am PST the Paragon dashboard and some services were temporarily unavailable. No data was lost during this incident and performance has recovered to normal standards.
On 6/25/25 at roughly 12:42pm PST, Paragon experienced a temporary spike in server loads that caused some workflow executions to fail and integration credentials to switch to an invalid state. This spike lasted for roughly 29min until performance was recovered and the spike was resolved. During this outage, some customers may have experienced workflow execution failure and their connected users may have seen previously valid integration credentials switch to an invalid state.
We are currently investigating an issue where requests to Paragon's Task History API are returning 500s. We have identified the cause of the issue and are working on a fix.
This incident has been resolved.
On June 6th, 2025, between 00:05 UTC and approximately 02:00 UTC, a small subset of workflow executions may have experienced degraded performance due to elevated utilization in our ElastiCache cluster. The issue has been mitigated and services are fully restored and operational.
A partial outage occurred between 20:00 UTC and 20:30 UTC impacting a number of services on Paragon's Cloud instance. This instance was related to a spike in database connections, and has since been resolved.
We are currently investigating an issue where some proxy requests are returning 500 errors for a subset of users. Our engineering team is actively working to fix the issue. We’ll share updates here as we learn more.
We have resolved this issue, and will continue to monitor it over the next few hours.
This incident has been resolved. Please reach out if you have any questions.
We’ve identified issues with the Dashboard’s Test Step functionality not passing data as expected. We are actively working on a resolution.
We've identified a fix for the issue with the Dashboard's Test Step functionality not passing data as expected. We are currently deploying the fix and anticipate the issue will be resolved this morning.
This incident has been resolved.
On February 12, 2025, we identified an issue in our Test Workflow feature where using certain Paragon variables in workflow steps caused downstream issues in testing the full workflow. Upon reports from multiple customers, we escalated the issue and deployed a hot-fix to resolve it. We have also introduced additional automated tests for this scenario to prevent similar issues in the future.
We are currently investigating this issue.
This incident has been resolved.
On February 13, 2025, at approximately 8:38 AM PST, a spike in database connections to one of our core services resulted in degraded performance across multiple parts of our system. This led to downtime affecting key product areas, including the dashboard and connect portal. The issue was identified and resolved by our engineering team within a short time frame, and all systems were fully restored. Please reach out to our Support team if you’d like a full RCA.
We are currently investigating this issue.
Cron triggers are currently stuck and not firing. We've identified the issue and looking for a root cause.
A fix has been implemented and we are monitoring the results.
All cron triggers have been restored with no data loss. Workflow triggers have resumed normal operation.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.