Ghost Inspector Outage History

Started Jun 17, 2026, 04:55 PM UTC· resolved Jun 17, 2026, 04:55 PM UTC

1. resolved Jun 17, 2026, 04:55 PM UTC

   Jun 17, 09:55 PDT Resolved - Early this morning, we experienced degraded performance affecting Chrome and Firefox test execution. Customers may have noticed: - Delayed test runs - Chrome and Firefox tests were queued longer than usual. - Failed results on our end; during a short window (~14:45 –15:10 UTC), some Chrome and Firefox test runs returned a failed result due to a temporary issue in our system. This is not a problem with your tests. The cause has been resolved, and we've added further system capacity to work through the delay. Test execution is catching up now, and we expect normal performance shortly. Any such failed test runs will re-run normally on their next scheduled execution and can be disregarded. All tests stuck in a queued state should be starting to run over the next 2 hours. All other Ghost Inspector functionality was not affected. We greatly apologize for this system disruption. We take system reliability seriously and will do our best to ensure this does not happen again.

Read the full incident report →

Started Oct 21, 2025, 08:49 PM UTC· resolved Oct 21, 2025, 08:49 PM UTC

1. resolved Oct 21, 2025, 08:49 PM UTC

   Oct 21, 13:49 PDT Resolved - This incident has been resolved. Oct 20, 10:26 PDT Update - We’re seeing gradual recovery as AWS continues resolving the global outage. You can try restarting tests carefully — some runs may still fail. We’re watching things closely and will update once stability is confirmed. Oct 20, 09:15 PDT Update - We’re still seeing instability from the ongoing AWS outage affecting parts of our infrastructure. Some tests may fail or time out. Our team is keeping a close eye on things and will restore full stability as soon as AWS resolves the issue. Thanks for bearing with us — we know this is frustrating and appreciate your patience. https://health.aws.amazon.com/health/status Oct 20, 03:10 PDT Update - Earlier today, a global AWS outage affected parts of our infrastructure, which caused interruptions in test execution and related services. https://health.aws.amazon.com/health/status The issue has been identified, and partial functionality was restored. While our systems have shown steady improvement, some regions are still experiencing degraded performance, which may cause certain tests to fail or time out. We recommend holding off on running additional tests for now, as performance and stability may continue to fluctuate until AWS fully resolves the issue. Our team is monitoring the situation closely and will ensure everything stabilizes before resuming normal operations. We truly appreciate your patience and sincerely apologize for the inconvenience. Oct 20, 02:40 PDT Update - We are continuing to monitor for any further issues. Oct 20, 02:00 PDT Monitoring - Service has stabilized and the test runner is operating normally. We’re continuing to monitor the situation and remain alert for any potential disruptions. Oct 20, 01:59 PDT Update - We’re seeing steady improvements and will keep monitoring the situation until everything is fully stable. Oct 20, 01:47 PDT Identified - The issue has been identified. Partial functionality of the test runner has been restored, though some disruptions may still occur. We’re closely monitoring the recovery process with our provider, which is currently experiencing a global outage. Oct 20, 01:12 PDT Investigating - Due to a global AWS outage, our services may be temporarily unavailable. We’ll keep you updated. https://health.aws.amazon.com/health/status

Read the full incident report →

Started Jul 09, 2025, 05:54 PM UTC· resolved Jul 09, 2025, 07:13 PM UTC

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

2. resolved Jul 09, 2025, 07:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2025, 06:30 AM UTC· resolved May 15, 2025, 06:30 AM UTC

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

Read the full incident report →

Started Nov 11, 2024, 10:30 AM UTC· resolved Nov 11, 2024, 10:30 AM UTC

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

Read the full incident report →