There have been no new issues during monitoring window. Resolving.
Posted Feb 18, 2025 - 18:26 UTC
Monitoring
We have mitigated the issue on our side. We have no longer seen any storage issue in the last 8 hours and are continuing to monitor the situation until we get final confirmation from AWS that their issue has been resolved.
Posted Feb 18, 2025 - 13:32 UTC
Update
We continue to work on the mitigation provided by AWS with well over half of the impacted deployments completed. We will provide another update in 1h, or sooner.
Posted Feb 18, 2025 - 06:10 UTC
Update
We continue to work on the mitigation provided by AWS with over half of the impacted deployments completed. We will provide another update in 1h, or sooner.
Posted Feb 18, 2025 - 05:10 UTC
Update
AWS has confirmed a degraded disk/storage issue affecting i3 instances in the ap-southeast-2a zone. We are working through a mitigation they provided. We will provide another update in 1h, or sooner.
Posted Feb 18, 2025 - 04:15 UTC
Identified
We're working closely with AWS and have identified failures with i3 instances in ap-southeast-2a. We will provide another update in 1h, or sooner.
Posted Feb 18, 2025 - 03:18 UTC
Update
We are still investigating disruptions in ap-southeast-2a. Potential impact include: Search results being incomplete. Ingesting, updating, or deleting data may fail. An update will be provided in 1h, or sooner.
Posted Feb 18, 2025 - 02:17 UTC
Investigating
We are investigating disruptions in ap-southeast-2, Asia Pacific (Sydney). We will post a new update in 1h, or sooner.
Posted Feb 18, 2025 - 01:10 UTC
This incident affected: AWS Sydney (ap-southeast-2) (APM connectivity: AWS ap-southeast-2).