AWS Middle East 1
Due to ongoing issues with AWS in the Middle East, we have taken the decision to remove our node in AWS Middle East 1 from our global monitoring schedules, starting Monday March 30th 2026. We will continue to monitor the situation.
Due to ongoing issues with AWS in the Middle East, we have taken the decision to remove our node in AWS Middle East 1 from our global monitoring schedules, starting Monday March 30th 2026. We will continue to monitor the situation.
We experienced a delay in processing our queues for monitoring. This started on March 25 2026 at 22:00, and began recovering around 22:25. The queue is fully recovered by 22:37. As a result of this issue, during the time period, some API calls may be called later than expected. It is possible some time-sensitive API calls may therefore returned 4xx HTTP warnings.
We experienced a delay in processing our alerting queue. This started on March 24 2026 at 04:21am, and began recovering around 05:12am. The queue was fully recovered by 5:27am. As a result of this issue, during the time period the delivery of webhooks and alerts may have been delayed.
From 1800-1810 UTC on Sunday, July 27, we will have a maintenance window. During this window, calls may be delayed. All monitoring schedules will be maintained, but results may be delayed by up to one hour.
This release introduces improved alerting functionality and other improved navigation elements. Here’s what’s new:
Our service providers have remediated their issues. All services are running normally now.
Around 19:00 UTC, we became aware of an issue impacting the platform, where no new monitoring calls are being scheduled or run currently. The root cause is failures across a number of Google Cloud services. We are working with Google on a resolution path.
Our earlier research found an issue, which has been remediated. All services are running normally now.
Around 15:30 UTC, we became aware of an issue impacting date selection in multi-step API workflows. We are investigating currently.
Our earlier research found an issue, which has been remediated. All services are running normally now.