Is Uptime.com down?

Last checked 4m ago
Current status
Uptime.com has degraded performance

2 active incidents: Degraded Performance Across Multiple Probe Locations, Global Probe Server Expansion (11 June 2026)

Official status page: https://status.uptime.com · Polled every 5 minutes · 139 components tracked

Uptime.com is reporting degraded performance right now (last checked 4m ago). Services are up but slower or partially failing.

Real-time Uptime.com status, recent outages, and incident history — pulled directly from Uptime.com's official status page at https://status.uptime.com every 5 minutes. Pingoru tracks 139 Uptime.com services and has captured 38 incidents in the last 90 days (99.84% uptime). Get email, Slack, Discord, or webhook alerts the moment Uptime.com reports a new incident — free for 5 monitors, no credit card.

Users who monitor Uptime.com also follow these Monitoring services: Kaseya NinjaOne LogicMonitor SolarWinds ControlUp xMatters Liongard AlertMedia GitHub Enterprise Cloud EU Meltwater View all 6,000+ providers
Uptime.com uptime 99.84% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incident 1

  1. Ongoing ● 1d 6h
    Started Jun 12, 2026, 01:57 PM UTC
    Timeline · 2 updates
    • investigating · Jun 12, 2026, 01:57 PM UTC

      We are currently investigating an issue affecting multiple monitoring probe locations, resulting in degraded performance and connectivity disruptions in a subset of our global monitoring network. Our Engineering team has identified that several probe locations are currently unavailable and is actively working to determine the root cause. At this time, the majority of monitoring locations remain operational and continue to perform checks as expected. Customers may observe reduced monitoring coverage, delayed check execution, or intermittent probe-related anomalies for checks assigned to affected locations. We are prioritizing this investigation and will provide additional updates as more information becomes available. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

    • monitoring · Jun 12, 2026, 05:51 PM UTC

      A fix has been successfully applied and deployed to resolve the issues affecting our monitoring probe locations. All impacted probe nodes have re-established stable connections, and delayed check queues are now clearing. At this time, all global monitoring locations have returned to normal operational baselines and are executing scheduled tests as expected. Our engineering teams will continue to closely monitor system telemetry and network stability to ensure performance remains sustained. We will officially mark this incident as resolved once we verify long-term stability across all infrastructure. Thank you for your patience and understanding.

    Latest: A fix has been successfully applied and deployed to resolve the issues affecting our monitoring probe locations. All impacted probe nodes have re-established stable connections, an…

Recent outages & incidents

Past 90 days
  1. Resolved 1h 30m
    Started Jun 09, 2026, 04:00 PM UTC · Resolved Jun 09, 2026, 05:30 PM UTC
    Timeline · 1 update
    • resolved · Jun 09, 2026, 05:52 PM UTC

      We are retroactively updating our status page for transparency regarding a resolved metrics collection issue. Between 16:00 and 17:30 UTC, check metrics were not collected in our production environment. Checks continued to run during this period, but some response time and related metric data may be unavailable in the dashboard for the affected window. The issue was identified and resolved, and metrics collection has resumed. No further impact is expected.

    Latest: We are retroactively updating our status page for transparency regarding a resolved metrics collection issue. Between 16:00 and 17:30 UTC, check metrics were not collected in our p…

  2. Resolved 2d 1h
    Started Jun 08, 2026, 05:20 PM UTC · Resolved Jun 10, 2026, 07:10 PM UTC
    Timeline · 3 updates
    • investigating · Jun 08, 2026, 05:20 PM UTC

      We are investigating an issue affecting checks using vault items on select monitoring locations recently updated as part of our Global Probe Server Expansion. Vault-backed values are not currently being resolved correctly on the affected locations. This may cause checks that rely on vault items, such as custom headers, credentials, or other check configuration fields, to fail incorrectly. The currently identified affected locations are: - Australia-Sydney - Chile-Santiago - Japan-Osaka - Japan-Tokyo - South Africa-Johannesburg - US-CA-Fremont Checks running from other monitoring locations are not currently known to be affected. As a temporary workaround, affected customers can select alternative monitoring locations where suitable. Our engineering team has identified the issue and is working on a fix. We will provide further updates as remediation progresses.

    • identified · Jun 09, 2026, 05:49 PM UTC

      We have identified the issue affecting vault item resolution on select monitoring locations. A fix has been prepared and is pending deployment. Once deployed, checks using vault-backed values should resume working as expected from the affected locations. As a temporary workaround, affected customers can continue to use alternative monitoring locations where suitable. We will provide a further update once the fix has been deployed and validated.

    • resolved · Jun 10, 2026, 07:10 PM UTC

      A fix has been deployed and validated. Checks using vault-backed values are now resolving correctly on the affected monitoring locations. We will continue to monitor for any further issues. Thank you for your patience while we worked to resolve this.

    Latest: A fix has been deployed and validated. Checks using vault-backed values are now resolving correctly on the affected monitoring locations. We will continue to monitor for any furthe…

  3. Resolved 2d 23h
    Started Jun 05, 2026, 05:36 PM UTC · Resolved Jun 08, 2026, 05:18 PM UTC
    Timeline · 2 updates
    • investigating · Jun 05, 2026, 05:36 PM UTC

      We are currently investigating intermittent network connectivity issues affecting some Asia based monitoring locations. Initial findings indicate the issue is related to Telstra Global transit and is affecting both IPv4 and IPv6 connectivity. Checks may only be affected when traffic is routed over this transit provider, which may result in intermittent timeouts or false positive alerts from specific monitoring locations. Our team is monitoring the situation and will provide further updates as needed.

    • resolved · Jun 08, 2026, 05:18 PM UTC

      The intermittent network connectivity issues affecting some Asia based monitoring locations have now been resolved. Connectivity over the affected Telstra Global transit routes has stabilised, and both IPv4 and IPv6 connectivity are operating normally. We will continue to monitor for any further issues. Thank you for your patience.

    Latest: The intermittent network connectivity issues affecting some Asia based monitoring locations have now been resolved. Connectivity over the affected Telstra Global transit routes has…

  4. Resolved 3d 5h
    Started May 29, 2026, 07:04 PM UTC · Resolved Jun 02, 2026, 12:25 AM UTC
    Timeline · 2 updates
    • monitoring · May 29, 2026, 07:04 PM UTC

      We experienced a brief period of degraded application performance, including a short period where the application was unavailable for some users. Application performance has now recovered, and we are monitoring closely to ensure stability. We are reviewing the incident internally and will implement any necessary follow-up actions. We apologize for any inconvenience caused.

    • resolved · Jun 02, 2026, 12:25 AM UTC

      Application performance has remained stable following the earlier brief period of degraded performance and intermittent availability issues. We are marking this incident as resolved. We have reviewed the incident internally and will implement any necessary follow-up actions. We apologize for any inconvenience caused.

    Latest: Application performance has remained stable following the earlier brief period of degraded performance and intermittent availability issues. We are marking this incident as resolve…

  5. Resolved 10h 27m
    Started May 27, 2026, 12:25 PM UTC · Resolved May 27, 2026, 10:52 PM UTC
    Timeline · 2 updates
    • identified · May 27, 2026, 12:25 PM UTC

      We are currently facing connection issues with the `AU-Brisbane(NextDC)-1` probe server. Our service provider is reporting an ongoing network connectivity interruption on their data centre, which is impacting some servers. Their networking team is actively working to resolve the issue and restore service to the affected systems as soon as possible. Our Engineering team is working closely with the provider to resolve the issue swiftly. We will provide updates as soon as they become available. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

    • resolved · May 27, 2026, 10:53 PM UTC

      We’re pleased to confirm that the connection issues with our `AU-Brisbane(NextDC)-1` probe server have been resolved. All systems are back online and functioning as expected. Thank you for your patience while we worked with our provider to restore connectivity.

    Latest: We’re pleased to confirm that the connection issues with our `AU-Brisbane(NextDC)-1` probe server have been resolved. All systems are back online and functioning as expected. Thank…

See the full Uptime.com outage history

15 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Uptime.com outage history →

Or sign up free to get alerts when Uptime.com breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 20 incidents View full outage history →