Resolved after 16 minutes, on April 8, 2025.
On 08 April 2025 from 20:05 UTC to approximately 20:16 UTC, Wasabi services in our London (eu-west-3) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 20:05 UTC, our Operations Team was notified by our internal monitoring service that customer traffic was being impacted within the region. Upon investigation, it was found that internal DNS routing within the eu-west-3 region was failing to resolve internal hosts. Wasabi's Operations Team re-deployed the DNS stack and once re-deployment was completed at 20:16 UTC, customer connections to the region was restored.
Update timeline
- resolved Apr 11, 2025, 03:16 PM UTC
On 08 April 2025 from 20:05 UTC to approximately 20:16 UTC, Wasabi services in our London (eu-west-3) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 20:05 UTC, our Operations Team was notified by our internal monitoring service that customer traffic was being impacted within the region. Upon investigation, it was found that internal DNS routing within the eu-west-3 region was failing to resolve internal hosts. Wasabi's Operations Team re-deployed the DNS stack and once re-deployment was completed at 20:16 UTC, customer connections to the region was restored.
Your product runs on more than Wasabi
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services