Paessler Outage History
Paessler is up right nowPingoru has recorded 13 incidents for Paessler: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 509 (0%) |
Incidents, newest first
Minor March 1, 2026 Services affected in me-central-1 & me-south-1 2d 14h AWS EC2 Instances (me-central-1 - UAE), AWS EC2 Instances (me-south-1 - Bahrain)
Started Mar 01, 2026, 04:24 PM UTC· resolved Mar 04, 2026, 06:35 AM UTC
- 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.
- identified Mar 01, 2026, 09:19 PM UTC
We are continuing to work on restoring the affected machines and to monitor AWS services recovery.
- 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.
- 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.
- 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).
- 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.
- 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.
- monitoring Mar 03, 2026, 10:28 AM UTC
We are continuing to monitor for any further issues.
- 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
Minor November 18, 2025 Service Disruption - Authentication Issues 1h 17m Authentication
Started Nov 18, 2025, 03:21 PM UTC· resolved Nov 18, 2025, 04:38 PM UTC
- investigating Nov 18, 2025, 03:21 PM UTC
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.
- resolved Nov 18, 2025, 04:38 PM UTC
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.
Critical October 20, 2025 Elevated error rates, subscription management unavailable 5h 6m AWS EC2 Instances (us-east-1 - United States - Northern-Virginia)
Started Oct 20, 2025, 08:02 AM UTC· resolved Oct 20, 2025, 01:09 PM UTC
- investigating Oct 20, 2025, 08:02 AM UTC
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.
- monitoring Oct 20, 2025, 09:39 AM UTC
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.
- monitoring Oct 20, 2025, 09:48 AM UTC
We see continous recovery on the subscription service, reducing severity from major outage to degraded performance and continue monitoring.
- monitoring Oct 20, 2025, 12:22 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 12:24 PM UTC
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.
- resolved Oct 20, 2025, 01:09 PM UTC
All systems are back up and running again.
Major November 14, 2024 Listing existing subscriptions & booking new subscriptions impaired 1h 59m Website
Started Nov 14, 2024, 12:02 PM UTC· resolved Nov 14, 2024, 02:02 PM UTC
- identified Nov 14, 2024, 12:02 PM UTC
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.
- resolved Nov 14, 2024, 02:02 PM UTC
This incident has been resolved.