Paessler incident

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

Minor Resolved View vendor source →
Started
Mar 01, 2026, 04:24 PM UTC
Resolved
Mar 04, 2026, 06:35 AM UTC
Duration
2d 14h
Detected by Pingoru
Mar 01, 2026, 04:24 PM UTC

Affected components

AWS EC2 Instances (me-central-1 - UAE)AWS EC2 Instances (me-south-1 - Bahrain)

Update timeline

  1. identified Mar 01, 2026, 04:24 PM UTC

    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.

  2. identified Mar 01, 2026, 09:19 PM UTC

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

  3. monitoring Mar 02, 2026, 12:00 AM UTC

    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.

  4. monitoring Mar 02, 2026, 06:32 AM UTC

    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.

  5. identified Mar 02, 2026, 07:58 AM UTC

    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).

  6. monitoring Mar 02, 2026, 02:51 PM UTC

    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.

  7. monitoring Mar 03, 2026, 10:20 AM UTC

    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.

  8. monitoring Mar 03, 2026, 10:28 AM UTC

    We are continuing to monitor for any further issues.

  9. resolved Mar 04, 2026, 06:35 AM UTC

    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

Looking to track Paessler downtime and outages?

Pingoru polls Paessler's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Paessler reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Paessler alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Paessler for free

5 free monitors · No credit card required