Sequence incident

Elevated error rates on production

Minor Resolved View vendor source →

Sequence experienced a minor incident on May 18, 2026 affecting API and Billing and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 03:07 PM UTC
Resolved
May 18, 2026, 03:07 PM UTC
Duration
Detected by Pingoru
May 18, 2026, 03:07 PM UTC

Affected components

APIBillingUsageCustomer portalThird party integrationsDashboardCPQ

Update timeline

  1. investigating May 18, 2026, 12:55 PM UTC

    Status: Investigating We're investigating elevated error rates on our production environment across the dashboard and API Affected components Third party integrations (Degraded performance) Dashboard (Degraded performance) API (Degraded performance) Customer portal (Degraded performance) CPQ (Degraded performance) Billing (Degraded performance) Usage (Degraded performance)

  2. identified May 18, 2026, 01:23 PM UTC

    Status: Identified We've lowered our API rate limits and API performance has recovered. We're currently investigating into the root cause Affected components API (Operational) Customer portal (Operational) CPQ (Operational) Billing (Operational) Usage (Operational) Third party integrations (Operational) Dashboard (Operational)

  3. monitoring May 18, 2026, 02:46 PM UTC

    Status: Monitoring We've addressed the root cause and are continuing to monitor API health Affected components Usage (Operational) Third party integrations (Operational) Dashboard (Operational) API (Operational) Customer portal (Operational) CPQ (Operational) Billing (Operational)

  4. resolved May 18, 2026, 03:07 PM UTC

    Status: Resolved Our team have resolved the issue Affected components Customer portal (Operational) CPQ (Operational) Billing (Operational) Usage (Operational) Third party integrations (Operational) Dashboard (Operational) API (Operational)