TestingBot Outage History
TestingBot is up right nowPingoru has recorded 35 incidents for TestingBot: 6 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 4 | 4 of 720 (1%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 19 (0%) |
Incidents, newest first
Major September 28, 2026 Stability issues –
Started Sep 28, 2026, 05:00 PM UTC· resolved Sep 28, 2026, 05:00 PM UTC
- resolved Sep 28, 2026, 05:00 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.
Critical September 14, 2026 Datacenter provider incident 3h 13m Test Execution Platform
Started Sep 14, 2026, 10:30 AM UTC· resolved Sep 14, 2026, 01:44 PM UTC
- 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.
Critical September 14, 2026 Datacenter provider incident 31m Website, API, TestingBot Tunnel, Visual Testing and 20 more
Started Sep 14, 2026, 09:05 AM UTC· resolved Sep 14, 2026, 09:36 AM UTC
- identified Sep 14, 2026, 09:05 AM UTC
Our datacenter provider is experiencing issues, causing tests on TestingBot to fail. You are currently not able to log in or run tests. We will update this section as soon as we get more information.
- identified Sep 14, 2026, 09:33 AM UTC
The datacenter has recovered. Cause was a broken router.
- resolved Sep 14, 2026, 09:36 AM UTC
This incident has been resolved.
Major September 6, 2026 Maestro tests on physical Android devices –
Started Sep 06, 2026, 10:30 PM UTC· resolved Sep 06, 2026, 10:30 PM UTC
- resolved Sep 06, 2026, 10:30 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.
Notice February 3, 2026 TestingBot Storage downtime 2h 40m
Started Feb 03, 2026, 04:20 PM UTC· resolved Feb 03, 2026, 07:00 PM UTC
- resolved Feb 03, 2026, 04:30 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.
Notice December 5, 2025 Downtime all services 10m
Started Dec 05, 2025, 09:19 AM UTC· resolved Dec 05, 2025, 09:29 AM UTC
- resolved Dec 05, 2025, 09:30 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.
Major September 5, 2025 Elevated wait time 3h 30m
Started Sep 05, 2025, 01:00 AM UTC· resolved Sep 05, 2025, 04:30 AM UTC
- 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.