Retiring our Bahrain uptime checker location
Published on April 29, 2026 by Mattias Geniar
The AWS Middle East (Bahrain) region has been dealing with an extended incident, and we've decided to retire our Bahrain uptime checker location for the foreseeable future.
If Bahrain was your primary uptime check location, we've already moved you to Bangalore. It's the geographically closest remaining option, around 2,700 km away. You can pick any other location under your monitor's uptime check settings if you'd rather use something else.
Was anything actually broken? #
No, and that's worth saying out loud.
Every uptime check runs from a primary location and verifies from a secondary one before we alert you. When Bahrain was the primary and unreachable, the secondary (most often Bangalore) handled the verification and the check went through. Nobody got false alerts from this; the system did exactly what it was designed to do.
We're just no longer aiming checks at a region we know is having a rough time. One less moving part in the chain.
What changes for you #
For most customers: nothing. If you didn't pick Bahrain explicitly, you weren't using it.
If you did, your monitors are now running from Bangalore. Everything you'd expect stays in place:
- Primary plus secondary verification
- One-minute check interval
- The same alerting rules you've already configured
You can switch to any other location anytime under your monitor's uptime check settings.
Wishing the AWS team well #
Restoring a full region is a serious amount of work. Our hearts are with the AWS engineers handling this one and we wish them every success in bringing Bahrain back online. You can follow the situation on the AWS Health Dashboard.
When the region is healthy again, we'll happily bring Bahrain back as a checker option.
