Paragon Outage History

Started Jul 29, 2026, 02:24 PM UTC· resolved Jul 29, 2026, 05:27 PM UTC

1. investigating Jul 29, 2026, 02:24 PM UTC

   Some customers hosted in EU cloud may see degraded performance. We are currently investigating the cause and will provide updates.

2. identified Jul 29, 2026, 03:38 PM UTC

   We have identified the root cause of this issue and are working to restore performance within the hour.

3. resolved Jul 29, 2026, 05:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 10:23 PM UTC· resolved Jul 23, 2026, 12:15 AM UTC

1. investigating Jul 22, 2026, 10:23 PM UTC

   We are currently investigating an issue impacting our Connect Portal, Task History, and Task History API.

2. identified Jul 22, 2026, 11:17 PM UTC

   We have identified the issue and have been working to resolve the impacted services.

3. identified Jul 22, 2026, 11:47 PM UTC

   We have identified some additional impacted services, with intermittent errors impacting a handful of request-based triggers. We are continuing to work towards a resolution.

4. monitoring Jul 23, 2026, 01:25 AM UTC

   Our team is currently monitoring our services and will work on some additional improvements overnight.

5. resolved Jul 23, 2026, 04:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 01:46 PM UTC· resolved May 21, 2026, 03:57 PM UTC

1. investigating May 21, 2026, 01:46 PM UTC

   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/incidents/kq85fljj12w1

2. resolved May 21, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 06, 2026, 03:51 PM UTC· resolved May 06, 2026, 04:02 PM UTC

1. investigating May 06, 2026, 03:51 PM UTC

   We are currently investigating this issue.

2. monitoring May 06, 2026, 03:57 PM UTC

   Issue identified and resolved. No disruption to any services, workflows, actions, or syncs occurred during the incident time period - only dashboard was unavailable.

3. resolved May 06, 2026, 04:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 09:40 PM UTC· resolved Nov 18, 2025, 10:49 PM UTC

1. identified Nov 18, 2025, 09:40 PM UTC

   Some Paragon features are currently affected by the ongoing Github outage and are not functional at the moment.

2. identified Nov 18, 2025, 09:40 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Nov 18, 2025, 10:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 09:30 PM UTC· resolved Nov 04, 2025, 11:58 PM UTC

1. identified Nov 04, 2025, 10:43 PM UTC

   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.

2. identified Nov 04, 2025, 10:44 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Nov 04, 2025, 11:11 PM UTC

   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.

4. resolved Nov 04, 2025, 11:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 30, 2025, 04:31 PM UTC· resolved Oct 30, 2025, 06:40 PM UTC

1. investigating Oct 30, 2025, 04:31 PM UTC

   We are seeing degraded performance in some Paragon services, including the dashboard and task history. We are investigating and will update this page accordingly.

2. resolved Oct 30, 2025, 06:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 14, 2025, 07:56 PM UTC· resolved Oct 14, 2025, 08:08 PM UTC

1. investigating Oct 14, 2025, 07:56 PM UTC

   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.

2. resolved Oct 14, 2025, 08:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2025, 04:08 PM UTC· resolved Sep 11, 2025, 09:05 PM UTC

1. investigating Sep 11, 2025, 04:08 PM UTC

   We experienced downtime on the dashboard along with some API timeouts. Our team is actively investigating the root cause and working on mitigation.

2. monitoring Sep 11, 2025, 04:16 PM UTC

   We have identified the root cause of the issue. Our team is currently monitoring the results to ensure stability.

3. resolved Sep 11, 2025, 09:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2025, 01:44 AM UTC· resolved Sep 09, 2025, 04:48 AM UTC

1. investigating Sep 09, 2025, 01:44 AM UTC

   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.

2. resolved Sep 09, 2025, 04:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2025, 12:15 AM UTC· resolved Sep 08, 2025, 07:30 AM UTC

1. investigating Sep 08, 2025, 04:12 AM UTC

   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.

2. resolved Sep 08, 2025, 06:38 AM UTC

   This incident has been resolved, affected workflow services have been fully restored. Impacted customer workflows will be notified about retry options to minimize impact.

Read the full incident report →

Started Sep 03, 2025, 06:20 PM UTC· resolved Sep 05, 2025, 04:14 AM UTC

1. identified Sep 03, 2025, 06:20 PM UTC

   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.

2. resolved Sep 05, 2025, 04:14 AM UTC

   The update to the Jira integration has been released, and functionality for all affected Actions and Triggers has been restored.

Read the full incident report →

Started Aug 12, 2025, 06:49 PM UTC· resolved Aug 12, 2025, 07:34 PM UTC

1. identified Aug 12, 2025, 06:49 PM UTC

   Some customers hosted in AWS EU cloud may see degraded workflow performance. We have identified the root cause and are deploying a fix.

2. resolved Aug 12, 2025, 07:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2025, 11:16 PM UTC· resolved Aug 06, 2025, 11:46 PM UTC

1. investigating Aug 06, 2025, 11:16 PM UTC

   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.

2. investigating Aug 06, 2025, 11:35 PM UTC

   We are continuing to investigate this issue.

3. resolved Aug 06, 2025, 11:46 PM UTC

   This incident has been resolved. Impacted customers will be notified.

Read the full incident report →

Started Jul 31, 2025, 04:50 PM UTC· resolved Jul 31, 2025, 04:57 PM UTC

1. identified Jul 31, 2025, 04:50 PM UTC

   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.

2. resolved Jul 31, 2025, 04:57 PM UTC

   This incident has been resolved as of 9:57am PST.

Read the full incident report →

Started Jul 18, 2025, 02:30 PM UTC· resolved Jul 18, 2025, 03:44 PM UTC

1. resolved Jul 18, 2025, 07:35 PM UTC

   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.

Read the full incident report →

Started Jun 25, 2025, 07:30 PM UTC· resolved Jun 25, 2025, 07:59 PM UTC

1. resolved Jul 01, 2025, 11:15 PM UTC

   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.

Read the full incident report →

Started Jun 06, 2025, 09:23 PM UTC· resolved Jun 09, 2025, 06:06 AM UTC

1. identified Jun 06, 2025, 09:23 PM UTC

   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.

2. resolved Jun 09, 2025, 06:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 06, 2025, 12:05 AM UTC· resolved Jun 06, 2025, 02:00 AM UTC

1. resolved Jun 06, 2025, 03:13 PM UTC

   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.

Read the full incident report →

Started May 20, 2025, 08:00 PM UTC· resolved May 20, 2025, 08:30 PM UTC

1. resolved May 20, 2025, 08:41 PM UTC

   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.

Read the full incident report →

Started May 05, 2025, 03:05 PM UTC· resolved May 05, 2025, 09:32 PM UTC

1. identified May 05, 2025, 03:05 PM UTC

   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.

2. monitoring May 05, 2025, 04:39 PM UTC

   We have resolved this issue, and will continue to monitor it over the next few hours.

3. resolved May 05, 2025, 09:32 PM UTC

   This incident has been resolved. Please reach out if you have any questions.

Read the full incident report →

Started Mar 03, 2025, 10:21 PM UTC· resolved Mar 03, 2025, 10:48 PM UTC

1. investigating Mar 03, 2025, 10:21 PM UTC

   We are currently investigating this issue.

2. resolved Mar 03, 2025, 10:48 PM UTC

   This incident has been resolved.

3. postmortem Mar 04, 2025, 01:15 AM UTC

   ### **Incident Report: Paragon Primary Database Disruption** On March 2, 2025 at 22:08 UTC, our primary database experienced a sharp increase in connection requests, exceeding its configured limits and causing temporary unresponsiveness. This resulted in downtime for several downstream services that rely on this including our **Dashboard** web app, the **Connect Portal** and our **Billing and Account reconciliation** systems. It did _**not**_ impact any inbound connection or non-workflow related systems. ### **Impact to Customers:** * **Service Downtime:** Customers were unable to access or perform actions within affected services for approximately 35 minutes. * **Delayed or Failed Transactions:** Some database-dependent operations, such as updates or queries, may have failed or been delayed. * **Potential Data Latency:** Any actions taken during the disruption may not have been immediately processed. ### **Resolution & Next Steps:** * **Immediate Recovery:** We restored service by increasing our allowable database connections and adjusting system-wide thresholds. * **Long-Term Improvements:** We are increasing connection capacity, enhancing auto-scaling configurations, and refining our monitoring to detect and prevent similar issues. ‌ We sincerely apologize for the inconvenience and appreciate your patience as we work to strengthen our systems for better reliability.

Read the full incident report →

Started Feb 21, 2025, 12:33 AM UTC· resolved Feb 21, 2025, 10:12 PM UTC

1. investigating Feb 21, 2025, 12:33 AM UTC

   We’ve identified issues with the Dashboard’s Test Step functionality not passing data as expected. We are actively working on a resolution.

2. identified Feb 21, 2025, 04:54 PM UTC

   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.

3. resolved Feb 21, 2025, 10:12 PM UTC

   This incident has been resolved.

4. postmortem Feb 25, 2025, 09:32 PM UTC

   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.

Read the full incident report →

Started Feb 13, 2025, 04:52 PM UTC· resolved Feb 13, 2025, 05:08 PM UTC

1. investigating Feb 13, 2025, 04:52 PM UTC

   We are currently investigating this issue.

2. resolved Feb 13, 2025, 05:08 PM UTC

   This incident has been resolved.

3. postmortem Feb 13, 2025, 11:38 PM UTC

   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.

Read the full incident report →

Started Feb 05, 2025, 07:35 PM UTC· resolved Feb 05, 2025, 08:45 PM UTC

1. investigating Feb 05, 2025, 07:35 PM UTC

   We are currently investigating this issue.

2. identified Feb 05, 2025, 08:00 PM UTC

   We are currently experiencing an incident where a number of workflows were unexpectedly un-deployed. Our team has identified the affected workflow IDs and is actively working on redeploying them now. We apologize for any disruption this may have caused and appreciate your patience as we work to resolve the issue. We will provide further updates as soon as we have more information. Thank you for your understanding.

3. identified Feb 05, 2025, 08:24 PM UTC

   We've implemented a solution and should have it shortly resolved. We apologize for any disruption this may have caused and appreciate your patience as we work to resolve this. We will continue to monitor the issue and expect the issue to be fully resolved in the next few minutes.

4. resolved Feb 05, 2025, 08:45 PM UTC

   This incident has been resolved.

5. postmortem Feb 11, 2025, 09:23 PM UTC

   # Undeployed Workflows: Public RCA ## **Summary** On Wednesday, February 5th, at approximately 19:10 UTC, we identified an issue where a subset of customer workflows were unexpectedly undeployed. Our engineering team immediately began investigating and restoring affected workflows, with full resolution completed shortly thereafter. ## **Impact** A number of customer workflows were temporarily set to an undeployed state, requiring manual reactivation. Some customers may have noticed disruptions in workflow execution during this period. ## **Root Cause** The issue was triggered by an administrative deployment management action from that did not correctly validate parameters under specific conditions. This resulted in certain workflows being marked as undeployed. ## **Resolution & Response** * Our automated monitoring systems, including BetterStack and Grafana, immediately alerted our team to the issue. * Within 1 minute of the alert, members of our executive team and key engineers began actively investigating the root cause and identifying the full scope of impact. * An internal tool was found as the source and was immediately taken offline. * A status page was posted to notify customers of the disruption. * A dedicated response team quickly developed and deployed a fix to restore all affected workflows using Paragon’s built in version and deployment history. * The issue was fully resolved in a timely manner, ensuring that customers could resume normal operations. ## **Preventative Measures** To prevent this from happening again, we have implemented the following safeguards: * **Enhanced Validation:** We have updated our deployment management process to enforce stricter input validation, preventing similar scenarios. * **Process Audits:** A comprehensive review of related administrative workflows is underway to identify and address potential gaps. * **Ongoing Monitoring Improvements:** We are strengthening our real-time monitoring and alerting systems to further reduce response times. ## **Next Steps** We are committed to continuously improving our platform’s reliability and ensuring minimal disruptions to customer operations. Our engineering team is actively reviewing additional safeguards and process improvements to enhance system resilience. We appreciate our customers’ patience and trust as we work to deliver a seamless, dependable experience. If you have any questions or concerns, please reach out to our support team.

Read the full incident report →