This is Paessler PRTG Hosted Monitor's status page, where you can get updates on how our services and features are doing. If there are any interruptions to our service, we will post a note to keep you informed.
PRTG Instances
Degraded Performance
90 days ago
100.0
% uptime
Today
PRTG Servers
Operational
PRTG Notification Emails
Operational
AWS EC2 Instances (af-south-1 - Africa - Cape Town)
Operational
90 days ago
100.0
% uptime
Today
AWS EC2 Instances (ap-east-1 - Hong Kong)
Operational
Resolved -
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
Mar 4, 06:35 UTC
Update -
We are continuing to monitor for any further issues.
Mar 3, 10:28 UTC
Update -
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.
Mar 3, 10:20 UTC
Monitoring -
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.
Mar 2, 14:51 UTC
Identified -
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).
Mar 2, 07:58 UTC
Update -
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.
Mar 2, 06:32 UTC
Monitoring -
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.
Mar 2, 00:00 UTC
Update -
We are continuing to work on restoring the affected machines and to monitor AWS services recovery.
Mar 1, 21:19 UTC
Instances in one particular availability zone of that region are affected, we are trying to migrate affected machines to a different availability zone.
Mar 1, 16:24 UTC