US2 will undergo scheduled maintenance for infrastructure improvements. A brief service interruption may happen during the 1-hour window.
We will perform a scheduled maintenance on the Archiver service in all regions to update an internal service. No customer-facing impact is expected. Archive jobs will continue to run as scheduled.
in progress
During this window, there is a potential for temporary downtime affecting our services. The following may be unavailable:
Recover and Accelerate services.
The user interface for Recover, Accelerate, Archive-App and Discover.
All Own API usage.
For Your Jobs and Data:
Manual jobs (e.g., seeding, restores) will be paused. We recommend you start any manual jobs well before this window.
Scheduled backups will resume automatically after maintenance. Any backups that fail will be manually restarted by our team.
After maintenance, please monitor and re-run any affected jobs as needed.
We apologize for any inconvenience this may cause and thank you for your understanding.
The incident has been resolved. We are closely monitoring the service to verify its full recovery.
We're currently experiencing an issue affecting the Archive service. Customers may be unable to search archived data, and the UI for accessing and managing archive policies is unavailable. We are continuing to work on a fix for this incident
We are currently investigating this incident. Customers may experience high latency while using Archive on Azure CA4
The Archive search service is fully restored. The upstream Microsoft Azure outage has been resolved, our Elastic Cloud cluster is healthy, and rebalancing is complete. No customer action is required. Thank you for your patience.
The search service has been restored to full capacity. Working with Elastic support, we completed the recovery actions and the cluster is healthy. Background rebalancing across the cluster is still in progress. We are monitoring until it completes.
Microsoft Azure has confirmed a datacenter power outage as the source. Elastic Cloud (hosted on Azure) is degraded, which is impacting our cluster performance. Customer-facing services are not affected at this time. We are waiting on Elastic Cloud to confirm recovery
Root cause identified: an active Microsoft Azure incident is impacting upstream dependencies for our services. We are assessing scope and affected components.
We are investigating reports of degraded service. Upstream provider (Microsoft Azure) is reporting an active incident, and we are assessing impact on our services.
Upgrade RDS archive
May 2026 to Jul 2026
Next
