Katalon incident

Elevated errors on TestOps (US) — API, Agent, and test execution reporting

Major Resolved View vendor source →

Katalon experienced a major incident on July 16, 2026 affecting TestOps API (US) and Agent (US) and 1 more component, lasting 15h 33m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 08:29 AM UTC
Resolved
Jul 17, 2026, 12:02 AM UTC
Duration
15h 33m
Detected by Pingoru
Jul 16, 2026, 08:29 AM UTC

Affected components

TestOps API (US)Agent (US)Schedules (US)Executions (US)TrueTest API (US)

Update timeline

  1. investigating Jul 16, 2026, 08:29 AM UTC

    We are investigating an incident affecting TestOps in the US region. Users may experience timeouts or errors when accessing the TestOps API, connecting Agents, running or reporting test executions, and triggering schedules. Our engineering team is actively working on remediation. Scope: US region only. TestOps in the EU region is unaffected and fully operational, as are TestCloud, licensing, account/identity, and all Katalon websites. We will post the next update within 30 minutes or as soon as service is restored. We apologize for the disruption.

  2. identified Jul 16, 2026, 09:00 AM UTC

    We have identified the cause of the ongoing disruption affecting TestOps in the US region. Since 07:55 UTC on 16 Jul 2026, users may experience timeouts or 504 errors when accessing the TestOps web app and API, connecting Agents, and reporting test executions. The issue originates from our content-delivery provider (Amazon CloudFront), which has stopped routing requests to our services in this region. Amazon has acknowledged a corresponding event on their service health dashboard. Our infrastructure and backend services are healthy — the disruption is in the delivery path in front of them. Scope: US region only. TestOps EU is unaffected. TestCloud, licensing, and account sign-in are operating normally. We are monitoring the provider's recovery and evaluating a routing workaround to restore access sooner. Next update within 30 minutes or upon material change.

  3. identified Jul 16, 2026, 10:13 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jul 16, 2026, 10:42 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 17, 2026, 12:02 AM UTC

    This incident has been resolved.