Istoricul incidentelor Paessler

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.

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

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.

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.

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

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 & 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 are continuing to monitor for any further issues.

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 currently experiencing login issues affecting PRTG hosted instances. This is due to an ongoing Cloudflare outage impacting our Auth0 authentication service. We are actively monitoring the situation and working with our service providers to restore normal operations as quickly as possible. We apologize for any inconvenience this may cause.

We are pleased to confirm that login issues affecting PRTG hosted instances have been resolved. The Cloudflare outage impacting our Auth0 authentication service has been addressed, and all systems are now operating normally. We appreciate your patience and understanding during this incident. If you continue to experience any issues, please don't hesitate to contact our support team.

We are currently seeing elevated error rates impacting several services. Services related to booking/managing subscriptions are impaired as well. Existing subscriptions are currently also not showing.

Issues are related to an outage in one AWS region that affected some of our own and also relevant 3rd party services. See also https://health.aws.amazon.com/health/status Listing existing subscriptions/instances on app.my-prtg.com might be still impaired, same goes for booking new subscriptions or starting PRTG Hosted Monitor trials. Recovery is currently ongoing, we monitor the situation and post an update.

We see continous recovery on the subscription service, reducing severity from major outage to degraded performance and continue monitoring.

We are continuing to monitor for any further issues.

Subscription Service is fine again. We notice occasional issues with EC2 instances in us-east-1 when being restarted, being stuck in stopping state. We're actively working on recovering those machines as fast as possible.

All systems are back up and running again.

Currently it is not possible to list details of existing subscriptions or book new subscriptions. The issue has been identified, we're working on a solution.

This incident has been resolved.

When trying to send logs/contact support via 'Setup | Contact Support' from a PRTG Hosted Monitor instance, it fails with error '403 forbidden'

A potential configuration issue has been identified, a fix is on its way.

A fix has been implemented, we are monitoring the situation.

This incident has been resolved.

Browsing on app.my-prtg.com leads to error messages like "Request failed with status code 500". We're investigating the issue.

This incident has been resolved.

Logins to PRTG Hosted Monitor instances currently impaired, users get stuck at a loading screen. We are investigating the issue. Logins via Desktop application and mobile apps are working.

Issue fixed. Root cause was a misconfigured access policy.

New instances cannot be created in the Frankfurt hosting region, existing instances are not affected.

A fix is being deployed, we are monitoring the situation.

The incident has been resolved.

We are currently investigating the issue. Logins to PRTG Hosted Monitor Instances are not affected.

Logins are possible again, we are monitoring the situation currently.

The incident has been resolved.

Authentication impaired on https://app.my-prtg.com and PRTG Hosted Monitor instances. The service recovered one hour later at 08:05 UTC.

AWS reported an issue with EBS volumes in one availability zone in its Northern-Virginia region. This lead to a few PRTG Hosted Monitor instances not running properly, because their data volumes were not attached properly. At around 07:30 (UTC) all affected instances were operational again.

We are currently working on this issue.

This incident has been resolved.

We are currently upgrading all instances to the new version of PRTG.

We are currently upgrading all instances to the new version of PRTG.

Updating will continue tomorrow.