Stensul Outage History
Stensul is up right nowStensul had 4 outages in the last 2 years totaling 7h 11m of downtime, averaging 0.2 incidents per month.
There were 4 Stensul outages since January 30, 2025 totaling 7h 11m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Elevated Errors
Timeline · 4 updates
- investigating Oct 01, 2026, 05:07 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.
- identified Oct 01, 2026, 05:17 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 01, 2026, 05:21 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 01, 2026, 05:51 PM UTC
This incident has been resolved.
Users were not able to access the platform
Timeline · 1 update
- 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.
Some users are not able to access the platform
Timeline · 4 updates
- investigating Jan 30, 2025, 05:41 PM UTC
Some users are getting a 403 error when accessing the platform.
- identified Jan 30, 2025, 05:42 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 30, 2025, 06:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 30, 2025, 06:20 PM UTC
This incident has been resolved.