Paessler Outage History

Paessler degraded View live status →

Paessler had 5 outages in the last 2 years totaling 74h 16m of downtime — averaging 0.2 incidents per month.

There were 5 Paessler outages since June 18, 2024 totaling 74h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.my-prtg.com

Minor November 18, 2025

Service Disruption - Authentication Issues

Detected by Pingoru
Nov 18, 2025, 03:21 PM UTC
Resolved
Nov 18, 2025, 04:38 PM UTC
Duration
1h 17m
Affected: Authentication
Timeline · 2 updates
  1. 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.

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

Read the full incident report →

Critical October 20, 2025

Elevated error rates, subscription management unavailable

Detected by Pingoru
Oct 20, 2025, 08:02 AM UTC
Resolved
Oct 20, 2025, 01:09 PM UTC
Duration
5h 6m
Affected: AWS EC2 Instances (us-east-1 - United States - Northern-Virginia)
Timeline · 6 updates
  1. 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.

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

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

  4. monitoring Oct 20, 2025, 12:22 PM UTC

    We are continuing to monitor for any further issues.

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

  6. resolved Oct 20, 2025, 01:09 PM UTC

    All systems are back up and running again.

Read the full incident report →

Major November 14, 2024

Listing existing subscriptions & booking new subscriptions impaired

Detected by Pingoru
Nov 14, 2024, 12:02 PM UTC
Resolved
Nov 14, 2024, 02:02 PM UTC
Duration
1h 59m
Affected: Website
Timeline · 2 updates
  1. 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.

  2. resolved Nov 14, 2024, 02:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 18, 2024

Contacting Support via 'Setup | Contact Support' impaired

Detected by Pingoru
Jun 18, 2024, 07:52 AM UTC
Resolved
Jun 18, 2024, 11:32 AM UTC
Duration
3h 39m
Affected: PRTG Servers
Timeline · 4 updates
  1. investigating Jun 18, 2024, 07:52 AM UTC

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

  2. identified Jun 18, 2024, 08:43 AM UTC

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

  3. monitoring Jun 18, 2024, 10:24 AM UTC

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

  4. resolved Jun 18, 2024, 11:32 AM UTC

    This incident has been resolved.

Read the full incident report →