Paragon Outage History

Paragon had 37 outages in the last 2 years totaling 984h 1m of downtime — averaging 1.5 incidents per month.

There were 37 Paragon outages since May 23, 2024 totaling 984h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.useparagon.com

Major December 20, 2024

Elevated API request errors and service unavailability

Detected by Pingoru: Dec 20, 2024, 08:49 AM UTC
Resolved: Dec 20, 2024, 04:15 PM UTC
Duration: 7h 25m

Affected: Workflow EditorTask HistoryWorkflowsConnect APIConnect Portal

Timeline · 3 updates

investigating Dec 20, 2024, 08:49 AM UTC

We are currently investigating elevated request error rates to 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.
identified Dec 20, 2024, 09:46 AM UTC

We have identified a potential issue and are working on implementing a fix.
resolved Dec 20, 2024, 04:15 PM UTC

We experienced a service disruption due to database performance issues that affected our SDK authentication system. The issue was resolved by 2:49am PST, and our team continued to monitor throughout the night to ensure stability. We've implemented additional safeguards to prevent similar incidents in the future.

Read the full incident report →

Notice December 14, 2024

Request triggers, Task History may be slow to respond

Detected by Pingoru: Dec 14, 2024, 08:16 AM UTC
Resolved: Jan 22, 2025, 03:58 PM UTC
Duration: 39d 7h

Affected: Task HistoryWorkflows

Timeline · 7 updates

investigating Dec 13, 2024, 05:31 PM UTC

We are currently investigating an issue with our services that may be causing Request-triggered Workflows and Task History views to respond slowly.
investigating Dec 13, 2024, 11:07 PM UTC

We are continuing to investigate this issue and have confirmed that its impact is limited to long-running workflow executions. Task History is not affected by this incident. If you are impacted by this incident, you may see the following error in your workflow as a false positive: “Processing has failed repeatedly due to CPU and memory constraints on the server. Please either refactor your workflow to process less records or contact support.” Replaying the workflow may resolve the issue temporarily for that execution, but the fix we are working on will prevent any false positive occurrences for this error. For almost all customers, this incident is affecting a small number of your total tasks (fewer than 1%). If we have identified your integrations as impacting a high volume of workflow executions, our team will reach out. We will provide an update by end of day Saturday, December 14. If you have any questions or concerns, please reach out to your Customer Success Manager.
investigating Dec 15, 2024, 08:16 AM UTC

We are continuing to investigate this issue and are working on a fix. At this time, this incident is still impacting a small number of total executions, and replaying the workflow may temporarily resolve any issues.
monitoring Dec 16, 2024, 04:59 AM UTC

We have resolved the issue in our systems at this time. We are continuing to monitor to ensure systems remain normal for any affected users.
monitoring Dec 19, 2024, 01:43 AM UTC

We have identified elevated error rates affecting Request-triggered Workflows and Task History views. Our team is actively monitoring the situation.
monitoring Dec 19, 2024, 02:26 AM UTC

We have resolved the issue in our systems at this time. We are continuing to monitor to ensure systems remain normal for any affected users.
resolved Jan 22, 2025, 03:58 PM UTC

This incident has been resolved.

Read the full incident report →

Minor October 10, 2024

Task History Performance Degraded

Detected by Pingoru: Oct 10, 2024, 07:25 PM UTC
Resolved: Oct 10, 2024, 09:48 PM UTC
Duration: 2h 22m

Affected: Task History

Timeline · 2 updates

investigating Oct 10, 2024, 07:25 PM UTC

For some users, task history may be delayed or have workflows appear as executing with no updates. We are currently investigating.
resolved Oct 10, 2024, 09:48 PM UTC

This incident has been resolved. A small amount of workflows have been marked as cancelled, and we're implementing a workaround to have them replayed.

Read the full incident report →

Minor October 4, 2024

Degraded workflow performance for some customers

Detected by Pingoru: Oct 04, 2024, 07:44 PM UTC
Resolved: Oct 04, 2024, 09:36 PM UTC
Duration: 1h 51m

Affected: Workflows

Timeline · 3 updates

investigating Oct 04, 2024, 07:44 PM UTC

We are currently investigating abnormally high queueing latencies for workflows in a small number of projects. If your project has been impacted, our team will reach out directly with an update.
monitoring Oct 04, 2024, 08:21 PM UTC

We have scaled up resources and are seeing lower levels of queueing latency for all impacted customers. We are continuing to monitor as the system processes executions that were delayed during the incident window.
resolved Oct 04, 2024, 09:36 PM UTC

This incident has been resolved.

Read the full incident report →

Major October 4, 2024

Task History input/output unavailable

Detected by Pingoru: Oct 04, 2024, 07:19 PM UTC
Resolved: Oct 04, 2024, 08:42 PM UTC
Duration: 1h 22m

Affected: Task History

Timeline · 4 updates

investigating Oct 04, 2024, 07:19 PM UTC

We are currently investigating an issue causing Task History input/output data views to be unavailable.
monitoring Oct 04, 2024, 07:30 PM UTC

A fix has been implemented, but Task History input/output data views may be slow to respond. We are closely monitoring and working on improvements.
monitoring Oct 04, 2024, 07:46 PM UTC

Task History input/output data availability has been restored, and our team is continuing to monitor for any changes.
resolved Oct 04, 2024, 08:42 PM UTC

This incident has been resolved.

Read the full incident report →

Minor September 19, 2024

Connect Portal Degradation

Detected by Pingoru: Sep 19, 2024, 05:33 PM UTC
Resolved: Sep 19, 2024, 06:45 PM UTC
Duration: 1h 12m

Affected: Connect Portal

Timeline · 3 updates

investigating Sep 19, 2024, 05:33 PM UTC

We are currently investigating an issue where select customers are experiencing slow load times or timeouts in the Connect Portal.
monitoring Sep 19, 2024, 06:13 PM UTC

We have resolved this issue, but are continuing to monitor for the next few hours.
resolved Sep 19, 2024, 06:45 PM UTC

This issue is confirmed to be resolved.

Read the full incident report →

Notice September 19, 2024

Redirects Timing Out

Detected by Pingoru: Sep 19, 2024, 12:03 AM UTC
Resolved: Sep 19, 2024, 12:00 AM UTC
Duration: —

Timeline · 1 update

resolved Sep 19, 2024, 12:03 AM UTC

For a brief period of time, some customers might have received 504 Gateway Timeout errors when attempting to establish a new integration connection. This incident is resolved.

Read the full incident report →

Minor September 12, 2024

Replaying Tasks Not Working as Expected

Detected by Pingoru: Sep 12, 2024, 06:05 PM UTC
Resolved: Sep 12, 2024, 10:27 PM UTC
Duration: 4h 22m

Affected: Task History

Timeline · 2 updates

identified Sep 12, 2024, 06:05 PM UTC

We've identified an issue where replaying certain types of executions can cause future executions to temporarily fail. Redeploying the impacted workflow resolves this issue. The impact is on a limited subset of workflow types, for a limited number of users. We are working on a fix and encourage users to avoid replays until the fix is released in a few hours. Please reach out if you have any questions.
resolved Sep 12, 2024, 10:27 PM UTC

This incident has been resolved. Executions can be replayed normally.

Read the full incident report →

Minor September 11, 2024

Elevated failures on Connect Proxy API

Detected by Pingoru: Sep 11, 2024, 04:25 PM UTC
Resolved: Sep 11, 2024, 03:30 PM UTC
Duration: —

Timeline · 1 update

resolved Sep 11, 2024, 04:25 PM UTC

We observed elevated failure rates for Connect Proxy requests. Requests may have intermittently failed with 504 Gateway Timeout errors. The issue is stabilized, and we are monitoring.

Read the full incident report →

Notice August 9, 2024

Duplicated Query Parameters for Some Outgoing Generic HTTP Requests

Detected by Pingoru: Aug 09, 2024, 04:38 PM UTC
Resolved: Aug 09, 2024, 10:09 PM UTC
Duration: 5h 30m

Affected: Workflows

Timeline · 2 updates

identified Aug 09, 2024, 04:38 PM UTC

Paragon identified an issue where some outgoing HTTP requests (via Paragon’s generic HTTP Request Step) include duplicate query parameters. This does not impact Paragon's Integration Request Steps. A release is underway that resolves this issue.
resolved Aug 09, 2024, 10:09 PM UTC

This incident has been resolved.

Read the full incident report →

Minor May 30, 2024

Task History Delayed and Some Queries Timing Out

Detected by Pingoru: May 30, 2024, 12:49 AM UTC
Resolved: May 30, 2024, 03:46 PM UTC
Duration: 14h 57m

Affected: Task HistoryWorkflowsConnect API

Timeline · 2 updates

identified May 30, 2024, 12:49 AM UTC

We are currently investigating an issue where some queries to Paragon endpoints are taking longer-than-expected to complete. This includes writing successful executions to task history. Paragon is scaling up resources to address this issue.
resolved May 30, 2024, 03:46 PM UTC

This incident has been resolved. After monitoring overnight and completing a review, Paragon determined that timeouts and delays were limited, and systems are operational.

Read the full incident report →

Major May 23, 2024

Task Execution Errors for Some Customers

Detected by Pingoru: May 23, 2024, 04:06 AM UTC
Resolved: May 23, 2024, 05:20 AM UTC
Duration: 1h 13m

Affected: WorkflowsConnect API

Timeline · 4 updates

investigating May 23, 2024, 04:06 AM UTC

We are currently investigating an issue where tasks are failing for some customers. Note: Paragon proactively stores all workflow data to allow tasks to be replayed.
identified May 23, 2024, 04:24 AM UTC

We have identified an issue that was causing erroneous task failures, and are observing tasks recovering. We will continue to monitor.
monitoring May 23, 2024, 04:56 AM UTC

A fix has been implemented, and all tasks should be executing as normal. We are continuing to monitor executions.
resolved May 23, 2024, 05:20 AM UTC

This incident is resolved. We’ve unblocked all affected customers. Systems should be fully operational.

Read the full incident report →