Service Availability Incident
Affected: Test Runner
Ghost Inspector Outage History
Ghost Inspector is up right nowGhost Inspector had 4 outages in the last 2 years totaling 37h 55m of downtime — averaging 0.2 incidents per month.
There were 4 Ghost Inspector outages since November 12, 2024 totaling 37h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.
Ghost Inspector outage
Affected: ApplicationHomepage
Timeline · 2 updates
- identified Jul 09, 2025, 05:54 PM UTC
We are currently experiencing an outage due to internal database issues. Please note that we may perform additional maintenance work throughout the day; however, we will make every effort to avoid further disruptions. Thank you for your patience and understanding.
- resolved Jul 09, 2025, 07:13 PM UTC
This incident has been resolved.
Internal Server Error from Test Runner Instance
Timeline · 1 update
- resolved May 15, 2025, 08:40 AM UTC
One of our test runner instances began returning intermittent Internal Server Error responses, causing some test runs to fail unexpectedly. The issue was traced to an internal fault on the runner, which we promptly identified and removed from the rotation. We have taken steps to ensure the faulty runner is no longer in use and are continuing to monitor for stability across all test executions. We sincerely apologize for the disruption and appreciate your patience.
Chrome Test Runner intermittent error
Timeline · 1 update
- resolved Nov 12, 2024, 08:03 PM UTC
Recently, our platform experienced an intermittent error due to one Chrome test runner server among many, which had entered a faulty state and was consistently failing. This issue has now been identified and resolved, and we apologize for any inconvenience this may have caused. To confirm the fix, please restart any tests that previously encountered errors. If you continue to experience any problems, please let us know. Our monitoring systems didn’t detect this sooner because the error rate across all tests stayed within limits. We take this seriously and are working to improve our monitoring to catch similar cases more effectively in the future. Thank you again for your assistance and patience.