Siteimprove Status Page

Aug 6, 2026 · resolved Aug 14

The issue affecting the AEO Visibility & Analytics module has been resolved. The module is now operating as expected, and no further impact is expected.

Jul 16, 2026 · resolved Jul 16

Executive Summary: On July 16, 2026, some users on our EU and US platforms were unable to log in for approximately two hours. The issue was caused by an outage at a third-party authentication provider, which was itself triggered by a major operational issue at a large cloud infrastructure provider. The provider restored service by rerouting their traffic, and our platform recovered automatically. There was no data loss and no action required on our side. Incident Overview: The initial step of our password and single sign-on (SSO) login journeys is handled by a third-party authentication provider. When that provider became unreachable due to an upstream cloud infrastructure issue, users attempting those login journeys received authentication errors. Because the failure sat entirely within an external dependency, there was no component on our side to repair. The provider mitigated the issue by rerouting their traffic away from the affected infrastructure, after which our login journeys recovered on their own. Impact: Password-based and SSO logins on the EU and US platforms were mostly unavailable from approximately 2026-07-16T07:55Z to 2026-07-16T09:55Z. Users signing in through direct links were unaffected throughout, and users already logged in were able to continue working. Detection: The incident was detected at 2026-07-16T07:55Z by our automated monitoring, which flagged the authentication provider as unreachable and shortly after picked up failing login checks across both EU and US. Response: Our operations team began investigating and confirmed the failure was an outage at the third-party authentication provider, which had already published a status update acknowledging the issue. We contacted the provider directly and confirmed there was no corrective action available on our side, as the fault was entirely within their infrastructure. Root Cause: A major operational issue at a large cloud infrastructure provider disrupted the routing our third-party authentication provider depends on, making it unreachable. Because that provider handles the first step of our password and SSO login journeys, those journeys failed while the outage lasted. Next Steps While this incident originated entirely outside our systems, we are reviewing options to reduce the impact of any future third-party authentication outage, including improved alerting granularity around upstream provider health and fallback options for the login path. We are also following up with the provider on their own remediation steps.

May 6, 2026 · resolved May 6

**Executive Summary:** On May 6, 2026, an infrastructure failure in our Kubernetes environment caused SSO login failures for a subset of users for approximately 42 minutes. All other platform functionality was unaffected. The issue was caused by a loss of quorum in an internal cluster's control plane, compounded by a node that had been silently degraded. The incident was resolved by replacing the affected nodes, and the system has been operating normally since. **Incident Overview:** The issue originated from an internal infrastructure cluster that acts as a connectivity bridge between our environments. Two of the cluster's three control plane nodes became non-functional — one had been in a degraded state, and a second failed during normal operations. With two of three nodes down, the cluster could no longer coordinate its workloads, which disrupted the network path required for SSO logins for some users. Some of our internal tooling was also affected. To resolve the issue, the team replaced the unresponsive nodes, which restored normal operations. Login functionality recovered shortly after. **Impact:** Some users logging into the platform via SSO experienced failures from approximately **2026-05-06T14:34Z** to **2026-05-06T15:16Z** \(~42 minutes\). **Detection:** The incident was detected at **2026-05-06T14:34Z** when our automated monitoring system identified connectivity failures in the login journey, which alerted the operations team. **Response:** Our operations team began investigating immediately. The affected control plane nodes were identified and replaced, with full recovery confirmed via automated tests at **2026-05-06T15:16Z**. A status page update was posted during the incident. **Root Cause:** Two of three control plane nodes in an internal cluster became unavailable at the same time — one had been silently degraded, and a second failed independently. The monitoring pipeline that should have detected the degraded node ahead of time was itself not functioning correctly. Because it only logged on failure and not on success, its silence was indistinguishable from normal operation, and the team had no way to know it had stopped working. Follow-up actions updated the monitoring pipeline to emit success signals so that their absence can be alerted on, improving overall control plane monitoring coverage, and introducing scheduled control plane node replacements as a preventive measure.

May 1, 2026 · resolved May 1

**Executive Summary:** On May 1, 2026, users on our US platform experienced login failures and slowness for approximately 2.5 hours. The issue was caused by an internal service generating an excessive number of simultaneous requests to a shared backend component, which became overloaded and caused a cascading failure in the login process. The issue was resolved the same day, and the system has been operating normally since. **Incident Overview:** The issue originated from one of our internal data-processing services, which attempted to process a large volume of data for a single account all at once, rather than in manageable batches. This created an unexpectedly high load on a shared backend service that other parts of the platform depend on, including the component responsible for verifying user access during login. As the shared service became overwhelmed, the login-related service was unable to complete its checks and began failing repeatedly. This meant users trying to log in received errors or experienced significant delays. To resolve the issue, the team identified the service generating the excessive load and temporarily disabled it, since it wasn’t a real-time component. This immediately relieved the pressure on the shared backend, and the login process recovered shortly after. The service was subsequently restored with a fix applied preventing the same pattern from recurring. **Impact:** Users on the US platform experienced login failures or significant slowness from approximately **2026-05-01T14:46Z** to **2026-05-01T17:24Z** \(~2 hours 38 minutes\). The platform itself remained generally available for users who were already logged in. A status page update was posted during the incident. **Detection:** The incident was detected at **2026-05-01T14:46Z** by our automatic monitoring system, which alerted the operations team to login-related failures in the US environment. **Response:** Our operations and engineering teams began investigating immediately. Initial steps focused on scaling up the affected backend components and stabilizing the login service. Once the source of the excessive load was identified, the responsible service was temporarily disabled at **2026-05-01T17:06Z**, which resolved the issue. Login errors subsided within minutes, and the status page was updated to reflect recovery at **2026-05-01T17:24Z**. **Root Cause:** An internal data-processing service attempted to handle all data for an unusually large dataset simultaneously, without any limit on the number of concurrent operations. This generated a surge of requests that overwhelmed a shared backend service, which in turn caused the login verification process to fail. The service has since been updated to limit concurrency and prevent this pattern from recurring.

Apr 29, 2026 · resolved Apr 30

The issue causing delays with Siteimprove’s crawler and link checker processing has been resolved. Scan processing has returned to normal, and Digital Certainty Index (DCI) scores and related metrics are now updating as expected.

Is Siteimprove down right now?

No — Siteimprove is up. All systems operational as of Aug 19, 10:31 PM UTC.

What is Siteimprove's current status?

Siteimprove: All Systems Operational. Alert24 checks Siteimprove's status page continuously and can notify you the moment it changes.

How do I get alerted when Siteimprove goes down?

Alert24 monitors Siteimprove and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.