Is Katalon down?
Last checked 8m agoNo incidents right now.
Katalon is operational right now. Last checked 8m ago; the most recent incident resolved 22d ago.
Real-time Katalon status, recent outages, and incident history — pulled directly from Katalon's official status page at https://status.katalon.com every 5 minutes. Pingoru tracks 41 Katalon services and has captured 19 incidents in the last 90 days (99.51% uptime). Get email, Slack, Discord, or webhook alerts the moment Katalon reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- TestOps API (US)Agent (US)Schedules (US)Executions (US)TrueTest API (US)
Timeline · 5 updates
- 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.
- 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.
- identified · Jul 16, 2026, 10:13 AM UTC
We are continuing to work on a fix for this issue.
- monitoring · Jul 16, 2026, 10:42 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 17, 2026, 12:02 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- TestOps API (US)Executions (US)
Timeline · 4 updates
- investigating · Jul 02, 2026, 09:55 AM UTC
We are investigating an issue in TestOps Gen3 (US) where, after connecting or syncing a Git repository, newly synced test assets - test cases, test suites, test suite collections, and execution profiles - may not appear. As a result, running tests from a newly Git-synced repository may be blocked. Repositories that were previously synced and are already indexed are not affected, and no data has been lost - your repository contents in Git are safe. Our engineering team is actively working on a fix and a re-sync to restore visibility. Next update within 60 minutes.
- identified · Jul 02, 2026, 11:01 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jul 02, 2026, 11:47 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 02, 2026, 12:20 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Executions (US)
Timeline · 7 updates
- investigating · Jun 24, 2026, 12:21 PM UTC
We are investigating elevated errors (HTTP 500) when viewing test execution results in TestOps. Affected users may see failures loading individual test result details, including attempt history and console output. Other TestOps functionality remains operational. Our engineering team has identified the cause as a slow database query timing out and is actively working on a fix. We will provide an update shortly.
- investigating · Jun 24, 2026, 12:59 PM UTC
We are continuing to investigate this issue.
- identified · Jun 24, 2026, 01:27 PM UTC
The issue has been identified.
- identified · Jun 24, 2026, 01:41 PM UTC
We are continuing to work on a fix for this issue.
- identified · Jun 24, 2026, 02:11 PM UTC
We are continuing to work on a fix for this issue.
- monitoring · Jun 24, 2026, 02:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 24, 2026, 02:32 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Jul 16, 2026, 08:29 AM UTC · Resolved Jul 17, 2026, 12:02 AM UTC · 15h 33m
- Started Jul 02, 2026, 09:55 AM UTC · Resolved Jul 02, 2026, 12:20 PM UTC · 2h 24m
- Started Jun 24, 2026, 12:21 PM UTC · Resolved Jun 24, 2026, 02:32 PM UTC · 2h 11m