TestingBot Outage History

TestingBot is up right now

TestingBot had 3 outages in the last 2 years — averaging 0.1 incidents per month.

There were 3 TestingBot outages since September 5, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.testingbot.com

Notice February 3, 2026

TestingBot Storage downtime

Detected by Pingoru
Feb 03, 2026, 07:06 PM UTC
Resolved
Feb 03, 2026, 04:30 PM UTC
Duration
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice December 5, 2025

Downtime all services

Detected by Pingoru
Dec 05, 2025, 10:50 AM UTC
Resolved
Dec 05, 2025, 09:30 AM UTC
Duration
Timeline · 1 update
  1. 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.

Read the full incident report →

Major September 5, 2025

Elevated wait time

Detected by Pingoru
Sep 05, 2025, 05:43 AM UTC
Resolved
Sep 05, 2025, 05:43 AM UTC
Duration
Timeline · 2 updates
  1. 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.

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

Read the full incident report →