Stova incident

504 Gateway Time-out errors on North America platform

Critical Resolved View vendor source →

Stova experienced a critical incident on May 15, 2026 affecting PHP Probe and EC2 CPU, lasting 2h 19m. The incident has been resolved; the full update timeline is below.

Started
May 15, 2026, 09:01 AM UTC
Resolved
May 15, 2026, 11:21 AM UTC
Duration
2h 19m
Detected by Pingoru
May 15, 2026, 09:01 AM UTC

Affected components

PHP ProbeEC2 CPU

Update timeline

  1. investigating May 15, 2026, 08:08 AM UTC

    Investigating – 504 Gateway Time-out on North America Server We are investigating reports of 504 Gateway Time-out errors on our North America platform. The issue is being treated with high priority and our engineering team is engaged. Further updates will follow shortly.

  2. investigating May 15, 2026, 09:01 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 15, 2026, 09:01 AM UTC

    Our engineering team continues to investigate the 504 Gateway Time-out errors affecting the North America platform. Root cause analysis is in progress, and all available resources have been engaged on priority. We do not have an ETA at this time. The next update will be shared within 30 minutes, or sooner if there is meaningful progress. We sincerely apologise for the continued disruption and appreciate your patience.

  4. identified May 15, 2026, 09:59 AM UTC

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

  5. identified May 15, 2026, 10:00 AM UTC

    Monitoring– Our engineering team has identified the root cause of the 504 Gateway Time-out incident on the North America platform and corrective action has been taken. Services are progressively recovering and access is being restored for impacted clients. We are closely monitoring platform performance to ensure full and sustained recovery. A further update will be shared once services are fully stable. We sincerely apologise for the disruption caused and thank you for your patience throughout the incident.

  6. monitoring May 15, 2026, 10:50 AM UTC

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

  7. monitoring May 15, 2026, 10:52 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved May 15, 2026, 11:21 AM UTC

    This incident has been resolved.