Services affected in me-central-1 & me-south-1

We are closing this incident on our side, since we have no more customers running in the impaired data centers. You can find further details and updates on the impacted regions here:
https://health.aws.amazon.com/health/status

We are continuing to monitor for any further issues.

Due to ongoing issues in me-central-1 & me-south-1, we have removed those regions for now as options for starting new PRTG Hosted Monitor subscriptions there.

A few PRTG Hosted Monitor instances are still running in me-central-1 inside the non-affected availability zone. Based on AWS' recommendation, we try to migrate those also to a different region, as soon as it's technically feasible.

We had no success in migrating affected instances to ap-south-1 (Mumbai), but we succeeded in migrating them now to ap-south-2 (Hyderabad). We keep monitoring the situation.

Due to ongoing issues in me-central-1 and me-south-1, we are now working on migrating affected customer instances to ap-south-1 (Mumbai).

Affected machines were moved to me-south-1 (Bahrain), but we're encountering issues now in this region as well. See also https://health.aws.amazon.com/health/status for current AWS status reports.

The affected machines have been restored to a different region while services are being restored in me-central-1 (UAE). We continue to monitor the situation closely.

We are continuing to work on restoring the affected machines and to monitor AWS services recovery.

Several services impacted in region me-central-1 (UAE), see also:
https://health.aws.amazon.com/health/status?eventID=arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5

Instances in one particular availability zone of that region are affected, we are trying to migrate affected machines to a different availability zone.