Stensul Outage History

Stensul is up right now

Stensul had 2 outages in the last 2 years totaling 19m of downtime — averaging 0.1 incidents per month.

There were 2 Stensul outages since May 4, 2026 totaling 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.stensul.com

Major May 17, 2026

Elevated Errors

Detected by Pingoru
May 17, 2026, 06:29 PM UTC
Resolved
May 17, 2026, 06:48 PM UTC
Duration
19m
Affected: Web UI
Timeline · 3 updates
  1. investigating May 17, 2026, 06:35 PM UTC

    We're experiencing an elevated level of errors and are currently looking into the issue. We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring May 17, 2026, 06:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 17, 2026, 06:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 4, 2026

Users were not able to access the platform

Detected by Pingoru
May 04, 2026, 07:29 PM UTC
Resolved
May 03, 2026, 06:58 PM UTC
Duration
Timeline · 1 update
  1. resolved May 04, 2026, 07:29 PM UTC

    Components affected ---------------------- Stensul Platform Impact ------- On May 3, 2026, around 2:58 PM ET, some users were unable to access or use the Stensul platform due to an issue with a backend data service used by the application. The incident began during rolling infrastructure maintenance, when the backend service entered an unhealthy failover state. During this period, platform operations that depended on that service were unavailable or degraded. Our team investigated the issue, restarted the affected service components, and confirmed that platform functionality had returned to normal. Service was restored at approximately 3:11 PM ET, and the incident was fully resolved. Final update ------------ The issue has been resolved. The Stensul platform is operating normally. We apologize for the disruption and any inconvenience this caused.

Read the full incident report →