DNSSEC 解析失败
- monitoring
我们发现一个问题 影响一个子集的Catchpoint测试 从2026年10月11日开始, 在协调世界时16: 30, 这个问题影响了使用DNSSEC验证的测试,导致DNS解析失败. 不使用 DNSSEC 验证的测试不受影响. 我们的工程组已经部署一个固定装置,我们正在积极监测这些装置,以确保DNS分辨率和测试执行恢复正常.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
56 Catchpoint incidents · 2025年5月 — official updates, affected components, duration and resolution details.
我们发现一个问题 影响一个子集的Catchpoint测试 从2026年10月11日开始, 在协调世界时16: 30, 这个问题影响了使用DNSSEC验证的测试,导致DNS解析失败. 不使用 DNSSEC 验证的测试不受影响. 我们的工程组已经部署一个固定装置,我们正在积极监测这些装置,以确保DNS分辨率和测试执行恢复正常.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个影响中国节点可用性的问题。 CN区域的节点可能在门户中出现脱机. 我们的小组正在努力恢复正常服务,并将在获得更多信息后提供进一步的最新资料.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查一个影响欧洲-地中海区域节点的问题。 该期于协调世界时2026年9月12日02:45左右开始. 我们的小组正在积极调查这个问题。 一旦获得更多信息,我们将提供更多最新情况.
已实施固定,受影响的数据已成功回填。 我们将继续密切监测这些服务,以确保持续稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查一个影响门户网站的问题,它影响到我们极少数用户。 我们正在与我们的工程团队合作解决这个问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
We identified and resolved an issue affecting SSL tests running on the US East Backbone and Cloud nodes from August 14, 2026, at 10:28:00 UTC to 13:14:10 UTC.
我们正在调查一个影响澳大利亚骨干节点的问题。 所有其他节点都正常运行. 我们正在同我们的区域提供方合作,以尽快解决这一问题,并将在获得最新情况后提供最新情况.
我们完成了所有悉尼和墨尔本监测节点的不铺放工作,现已全面运作。 阿德莱德,布里斯班和珀斯的其余节点定于下星期不停车. 一旦完成,我们将提供另一个更新。 感谢你们耐心地继续恢复在其余地点的服务.
此事件现已解决,所有节点现已暂停.
自动翻译自官方事件更新。
We have identified an issue where certain alert emails may not be delivered to recipients. Our team is looking into this on priority and is currently investigating the cause and impact. We will provide an update as soon as we have more information. Please contact us at [email protected] if you need any further assistance or information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue affecting nodes in the APAC region (excluding China) that began around 11:20 UTC. Impacted nodes may not be running tests as expected. Our team is actively working to resolve the issue and restore normal operations.
A fix was implemented around 11:46 UTC for the issue. Data collection and test execution have resumed, and we are continuing to monitor the services.
This incident has been resolved.
We identified an issue that affected a small number of users and API requests, impacting data loading on Record, Smartboard, and the REST API between 10:07 and 10:17 ET. A fix has been deployed and the issue is now resolved. We are continuing to monitor the system to ensure stability.
This incident has been resolved.
We are currently investigating an intermittent issue affecting capture server data collection for a subset of test runs, including Film Strip, screenshots, headers, and response content. Our team is actively working to identify the root cause and resolve the issue as quickly as possible. We will continue to share updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue affecting capture server data collection, including Film Strip, screenshots, headers, and response content. Our team is actively working to identify the root cause and resolve the issue as quickly as possible. We will provide updates as more information becomes available.
We are continuing to investigate this issue.
This incident has been resolved.
We have identified and resolved an issue that affected a subset of enterprise node customers between 07:09 and 08:42 UTC. Our investigation confirms that there was no impact to customer data. All services are now operating normally. We will continue to monitor the system to ensure stability.
This incident has been resolved.
We are currently experiencing an issue with our email support channel, which may impact our ability to receive or respond to emails in a timely manner. In the meantime, we request you to reach out to us using Live Chat or by opening a ticket through the Resource Center in the portal for faster assistance. Our team is actively working to resolve this issue and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some Chrome-based tests were temporarily switched to Chrome Stable Version 89 between March 10, 2026 – 19:52 UTC and 20:15 UTC. As a result, tests configured to run on a higher Chrome browser version may have experienced failures during this time due to the version downgrade impacting monitoring behaviour. The issue has been resolved and all affected tests have been restored to their intended configurations.
This incident has been resolved.
We are currently investigating an issue where recent modifications to tests are not going live. We will share updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A subset of historical capture data in the US-West region is currently unavailable. All real-time capture data is working expected.
This incident has been resolved.
We have identified an issue that resulted in a data gap between 14:37:22 and 14:49:01 UTC. The affected data has backfilled and We are closely monitoring the situation and will share updates as needed.
This incident has been resolved.
We are currently investigating an issue impacting the catchpoint portal. Some users may experience a blank page after logging in or when attempting to view records. Please note that tests and alerts continue to function as expected. Our team is actively working to resolve this as quickly as possible.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an increase in reported ISP-related incidents in Internet Sonar. Further updates will be shared as soon as more information is available.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating an issue that affected the REST API calls during 14:53 - 15:03 UTC. The tests and alerts were running as expected but the REST API calls might have failed intermittently.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.