Paragon incident

Elevated errors in API

Minor Resolved View vendor source →

Paragon experienced a minor incident on March 3, 2025 affecting Workflows, lasting 27m. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2025, 10:21 PM UTC
Resolved
Mar 03, 2025, 10:48 PM UTC
Duration
27m
Detected by Pingoru
Mar 03, 2025, 10:21 PM UTC

Affected components

Workflows

Update timeline

  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.