Stensul Outage History

Stensul is up right now

Pingoru has recorded 41 incidents for Stensul: 5 in the last 12 months and 2 in the last 90 days.

Source: status.stensul.com

41incidents recorded
5last 12 months
2last 90 days
95 minutestypical duration
Incidents per month
012MayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct1%
Pingoru began tracking Stensul in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202620 of 744 (0%)
June 202600 of 720 (0%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202627 of 521 (1%)

Incidents, newest first

Major October 21, 2026 Resolved — Stensul service fully restored 5h 47m Web UI, Stensul Website

Started Oct 21, 2026, 03:50 PM UTC· resolved Oct 21, 2026, 09:37 PM UTC

  1. identified Oct 21, 2026, 03:50 PM UTC

    The Stensul service remains temporarily unavailable as a precaution. Please disregard the earlier notification that maintenance was completed. Service has not yet been restored. We are continuing to validate and deploy the patches for the PHP2Shell security vulnerabilities. You can read the official PHP announcements here: https://www.php.net/archive/2026.php For immediate assistance, please contact Stensul Support at [email protected] Next update: By 12:30 p.m. ET, or sooner if there are significant developments. Previous updates: https://status.stensul.com/incidents/p8pk5fk3r0f4

  2. identified Oct 21, 2026, 04:51 PM UTC

    The Stensul service remains temporarily unavailable as a precaution. Our engineering team continues to work on validating and deploying the security patches for the PHP2Shell vulnerabilities. We are working to restore service as quickly as possible and appreciate your continued patience. For immediate assistance, please contact Stensul Support at [email protected]. Next update: By 1:30 p.m. ET, or sooner if there are significant developments.

  3. identified Oct 21, 2026, 05:36 PM UTC

    Final testing of the security patch The Stensul service remains temporarily unavailable as a precaution. We've made significant progress implementing the PHP security updates and are now completing the final round of testing and validation to ensure the platform is operating securely and reliably before restoring service. For immediate assistance, please contact Stensul Support at [email protected]. Next update: By 2:30 p.m. ET, or sooner if there are significant developments.

  4. identified Oct 21, 2026, 06:33 PM UTC

    The Stensul service remains temporarily unavailable as a precaution. We've made further progress implementing the PHP security updates and are continuing our final testing and validation to ensure the platform is operating securely and reliably before restoring service. For immediate assistance, please contact Stensul Support at [email protected]. Next update: By 3:30 p.m. ET, or sooner if there are significant developments.

  5. monitoring Oct 21, 2026, 08:11 PM UTC

    Stensul is fully available. We have implemented the PHP security updates and verified that they address the vulnerabilities. Our preliminary investigation has found no indication that Stensul services or data were compromised. You can read the official PHP announcements for more information: https://www.php.net/archive/2026.php We are monitoring closely. If you experience any issues, please contact Stensul Support at [email protected]. Next update: By 5:00 p.m. ET, or sooner if there are significant developments.

  6. resolved Oct 21, 2026, 09:37 PM UTC

    Resolved — Stensul service fully restored Stensul service has been fully restored, and we've confirmed the platform is operating normally following the deployment of the PHP security patches. We appreciate your patience and understanding during this interruption. If you experience any issues, please contact Stensul Support at [email protected].

Read the full incident report →

Major October 1, 2026 Elevated Errors 44m Web UI

Started Oct 01, 2026, 05:07 PM UTC· resolved Oct 01, 2026, 05:51 PM UTC

  1. 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.

  2. identified Oct 01, 2026, 05:17 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 01, 2026, 05:21 PM UTC

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

  4. resolved Oct 01, 2026, 05:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 3, 2026 Users were not able to access the platform –

Started May 03, 2026, 06:58 PM UTC· resolved May 03, 2026, 06:58 PM UTC

  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 →

Major January 30, 2025 Some users are not able to access the platform 39m Web UI

Started Jan 30, 2025, 05:41 PM UTC· resolved Jan 30, 2025, 06:20 PM UTC

  1. investigating Jan 30, 2025, 05:41 PM UTC

    Some users are getting a 403 error when accessing the platform.

  2. identified Jan 30, 2025, 05:42 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 30, 2025, 06:02 PM UTC

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

  4. resolved Jan 30, 2025, 06:20 PM UTC

    This incident has been resolved.

Read the full incident report →