Spreedly incident

Degraded Performance on Spreedly ID

Minor Resolved View vendor source →

Spreedly experienced a minor incident on April 11, 2024 affecting app.spreedly.com, lasting 8d 4h. The incident has been resolved; the full update timeline is below.

Started
Apr 11, 2024, 03:27 PM UTC
Resolved
Apr 19, 2024, 07:51 PM UTC
Duration
8d 4h
Detected by Pingoru
Apr 11, 2024, 03:27 PM UTC

Affected components

app.spreedly.com

Update timeline

  1. investigating Apr 11, 2024, 03:27 PM UTC

    We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. We will provide updates as soon as more information becomes available.

  2. monitoring Apr 11, 2024, 07:50 PM UTC

    We observed degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO). Our team has investigated and we have implemented a workaround for users experiencing this issue. If you are still impacted, please reach out, and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused.

  3. investigating Apr 16, 2024, 03:17 PM UTC

    We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. please reach out to our support team if you are experiencing any log in issues.

  4. monitoring Apr 17, 2024, 06:02 PM UTC

    We are monitoring the degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO) connections using using OpenID Connect (OIDC). We have implemented a workaround for users experiencing this issue. If you are still impacted, please reach out and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused and are working on a longer term solution

  5. resolved Apr 19, 2024, 07:51 PM UTC

    After a period of monitoring, this incident is considered resolved. We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.