Stability issues
Timeline · 1 update
- resolved Sep 28, 2026, 06:47 PM UTC
We experienced 90 minutes of stability issues due to a hardware problem. This has been resolved and we are taking steps to prevent this from happening in the future.
TestingBot Outage History
TestingBot partial outage View live status →TestingBot had 6 outages in the last 2 years totaling 3h 13m of downtime — averaging 0.2 incidents per month.
There were 6 TestingBot outages since September 5, 2025 totaling 3h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
Datacenter provider incident
Affected: Test Execution Platform
Timeline · 2 updates
- monitoring Sep 14, 2026, 10:30 AM UTC
Our upstream datacenter is experiencing issues causing services on TestingBot to fail. We are following up.
- resolved Sep 14, 2026, 01:44 PM UTC
This incident has been resolved.
Maestro tests on physical Android devices
Timeline · 2 updates
- resolved Sep 07, 2026, 12:09 PM UTC
Maestro tests against physical Android devices were returning errors.
- postmortem Sep 07, 2026, 12:09 PM UTC
A previous deploy introduced a bug that failed the start of Maestro tests when some conditions were met. We have added a fix, test and alert.
TestingBot Storage downtime
Timeline · 1 update
- resolved Feb 03, 2026, 07:06 PM UTC
TestingBot Storage has been experiencing issues today on February 3, 2026 from 16:20 UTC up to 19:00 UTC. This has been resolved.
Downtime all services
Timeline · 1 update
- resolved Dec 05, 2025, 10:50 AM UTC
Today between 10:19 and 10:29 we had an incident with our database which caused downtime. This was resolved and we will be making changes to prevent this from happening.
Elevated wait time
Timeline · 2 updates
- resolved Sep 05, 2025, 05:43 AM UTC
Since 1:00 UTC time we have been experiencing elevated wait times, causing some tests to wait for up to 5 minutes before they could start. We deployed a fix and are monitoring the waiting times. They are back to < 10 seconds since 04:30 UTC.
- postmortem Sep 05, 2025, 05:44 AM UTC
Today we experienced long waiting times for Windows \+ macOS machines. The issue was caused by a server issue, where memory issues were causing restarts of our hub \(h[ub.testingbot.com\)](http://hub.testingbot.com) This in turn caused the machines running the tests to fail to communicate with the hub, causing tests from clients to wait up to 5 minutes before a test could start. If your test runner is configured with a http connect timeout < 5 minutes, this may have caused issues where tests would fail to start. The memory issue was resolved and we are looking into a solution to prevent this from happening again.