Is CloudAMQP down?

Last checked 8m ago
Current status
CloudAMQP is up

No incidents right now.

Official status page: https://status.cloudamqp.com · Polled every 5 minutes · 37 components tracked

CloudAMQP is operational right now. Last checked 8m ago; the most recent incident resolved 20d ago.

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

Users who monitor CloudAMQP also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
CloudAMQP uptime 99.76% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 29m
    Started Aug 26, 2026, 01:27 PM UTC · Resolved Aug 26, 2026, 01:57 PM UTC
    Shared servers
    Timeline · 4 updates
    • investigating · Aug 26, 2026, 01:27 PM UTC

      We are currently investigating this issue.

    • identified · Aug 26, 2026, 01:28 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Aug 26, 2026, 01:41 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Aug 26, 2026, 01:57 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1d
    Started Aug 24, 2026, 11:52 PM UTC · Resolved Aug 25, 2026, 11:58 PM UTC
    DigitalOcean AMS2DigitalOcean AMS3DigitalOcean FRA1DigitalOcean LON1DigitalOcean NYC2DigitalOcean NYC3DigitalOcean SFO1DigitalOcean SGP1DigitalOcean TOR1
    Timeline · 2 updates
    • monitoring · Aug 24, 2026, 11:52 PM UTC

      DigitalOcean is currently experiencing issues with its API and control panel and you may run into errors and higher latency while the issue persists

    • resolved · Aug 25, 2026, 11:58 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 6h 15m
    Started Jul 23, 2026, 03:33 PM UTC · Resolved Jul 23, 2026, 09:48 PM UTC
    Dedicated serversMicrosoft Azure
    Timeline · 3 updates
    • investigating · Jul 23, 2026, 03:33 PM UTC

      We've received various alert notifying us about couple of servers deployed on Azure West US not being reachable. Apparently this seems to be related specific to this region impacting 25% of the servers.

    • monitoring · Jul 23, 2026, 07:50 PM UTC

      Microsoft Azure confirmed they were having network issues on West US region. For now, most of the servers are operational. We'll keep monitoring for the following hours.

    • resolved · Jul 23, 2026, 09:48 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 1d
    Started Jun 25, 2026, 02:10 PM UTC · Resolved Jun 26, 2026, 02:44 PM UTC
    Dedicated serversBackend
    Timeline · 7 updates
    • investigating · Jun 25, 2026, 02:10 PM UTC

      We are currently investigating this issue.

    • identified · Jun 25, 2026, 02:21 PM UTC

      The issue has been identified and a fix is being implemented.

    • investigating · Jun 26, 2026, 08:38 AM UTC

      We are currently investigating this issue.

    • identified · Jun 26, 2026, 09:17 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jun 26, 2026, 02:22 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Jun 26, 2026, 02:44 PM UTC

      This incident has been resolved.

    • postmortem · Jun 29, 2026, 11:22 AM UTC

      **Summary** Between June 25 and June 26, our monitoring system incorrectly reported some dedicated servers as unreachable and sent "server down" notifications for servers that were in fact operating normally. This was a monitoring-side issue only — no customer servers or services were actually down, and no data or message delivery was affected. **Impact** Affected customers received one or more alerts indicating their dedicated server was down. These alerts were false positives. The servers themselves remained healthy and fully available throughout the incident. **Root cause** Before connecting to a server, our monitoring system performs a network authorization step. A defect in how one component handled a transient network hiccup could leave a monitoring process unable to complete that step, after which it failed to connect to the servers it was responsible for checking. The servers themselves stayed healthy and available throughout — the monitoring process had simply lost its ability to reach them, and reported them as down. **Resolution** We identified the affected monitoring processes, confirmed the root cause in production, and deployed a fix that makes this authorization step resilient to such transient failures and able to recover automatically. After deploying, we monitored the system to confirm that notifications returned to normal. We apologize for the confusion these false notifications may have caused.

    Latest: **Summary** Between June 25 and June 26, our monitoring system incorrectly reported some dedicated servers as unreachable and sent "server down" notifications for servers that were…

Outage history

Past 90 days · 4 incidents View full outage history →