Ably Outage History

Ably is up right now

Ably had 10 outages in the last 2 years totaling 6h 23m of downtime — averaging 0.4 incidents per month.

There were 10 Ably outages since October 9, 2025 totaling 6h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ably.com

Minor August 28, 2026

Elevated API Errors - LiveObjects

Detected by Pingoru
Aug 28, 2026, 12:08 PM UTC
Resolved
Aug 28, 2026, 01:33 PM UTC
Duration
1h 24m
Affected: Ably PlatformEurope (Frankfurt)US East (Ohio)
Timeline · 6 updates
  1. investigating Aug 28, 2026, 12:08 PM UTC

    We're experiencing an elevated level of API errors in LiveObjects and are currently looking into the issue.

  2. identified Aug 28, 2026, 12:17 PM UTC

    We're mitigating the impact while investigating the root cause.

  3. identified Aug 28, 2026, 01:22 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 28, 2026, 01:26 PM UTC

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

  5. monitoring Aug 28, 2026, 01:26 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Aug 28, 2026, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 20, 2026

Elevated Errors in ap-southeast-1

Detected by Pingoru
Aug 20, 2026, 07:29 PM UTC
Resolved
Aug 20, 2026, 08:24 PM UTC
Duration
55m
Affected: Asia-Pacific (Singapore)
Timeline · 5 updates
  1. investigating Aug 20, 2026, 07:29 PM UTC

    We're experiencing an elevated level of errors in ap-southeast-1 and are currently looking into the issue.

  2. identified Aug 20, 2026, 07:41 PM UTC

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

  3. identified Aug 20, 2026, 07:42 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 20, 2026, 08:12 PM UTC

    A fix has been implemented and we our monitoring the result. Error rates have decreased to normal levels and the service is currently fully operational.

  5. resolved Aug 20, 2026, 08:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2026

Elevated Error Rate in ap-southeast-1

Detected by Pingoru
Aug 20, 2026, 07:07 PM UTC
Resolved
Aug 20, 2026, 07:10 PM UTC
Duration
2m
Affected: Asia-Pacific (Singapore)
Timeline · 2 updates
  1. investigating Aug 20, 2026, 07:07 PM UTC

    We're experiencing an elevated level of errors in the ap-southeast-1 region and are currently looking into the issue.

  2. resolved Aug 20, 2026, 07:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026

Elevated realtime publish error rate in ap-southeast-1

Detected by Pingoru
Feb 17, 2026, 10:19 AM UTC
Resolved
Feb 17, 2026, 10:32 AM UTC
Duration
12m
Affected: Asia-Pacific (Singapore)
Timeline · 4 updates
  1. investigating Feb 17, 2026, 10:19 AM UTC

    We're experiencing an elevated level of realtime publish errors in ap-southeast-1 and are currently looking into the issue.

  2. identified Feb 17, 2026, 10:24 AM UTC

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

  3. monitoring Feb 17, 2026, 10:30 AM UTC

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

  4. resolved Feb 17, 2026, 10:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 14, 2026

Elevated Attach Error Rate in eu-west-1

Detected by Pingoru
Feb 14, 2026, 05:57 AM UTC
Resolved
Feb 14, 2026, 06:05 AM UTC
Duration
8m
Affected: Europe (Ireland)
Timeline · 4 updates
  1. investigating Feb 14, 2026, 05:57 AM UTC

    We're experiencing an elevated level of attachment errors in eu-west-1 and are currently looking into the issue.

  2. identified Feb 14, 2026, 06:00 AM UTC

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

  3. monitoring Feb 14, 2026, 06:01 AM UTC

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

  4. resolved Feb 14, 2026, 06:05 AM UTC

    This incident has now been resolved.

Read the full incident report →

Minor January 21, 2026

SMS based 2FA is currently unavailable

Detected by Pingoru
Jan 21, 2026, 06:11 PM UTC
Resolved
Jan 21, 2026, 07:52 PM UTC
Duration
1h 41m
Affected: Ably Website
Timeline · 4 updates
  1. investigating Jan 21, 2026, 06:11 PM UTC

    We are currently investigating an issue impacting SMS based 2FA login to the Ably website ably.com.

  2. identified Jan 21, 2026, 06:29 PM UTC

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

  3. monitoring Jan 21, 2026, 06:36 PM UTC

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

  4. resolved Jan 21, 2026, 07:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 11, 2025

Push delivery errors for messages published in ap-southeast-2

Detected by Pingoru
Dec 11, 2025, 06:36 PM UTC
Resolved
Dec 11, 2025, 06:59 PM UTC
Duration
23m
Timeline · 3 updates
  1. investigating Dec 11, 2025, 06:36 PM UTC

    Increased level of push delivery errors for messages published in ap-southeast-2 only since 15:28 UTC, we're remediating

  2. identified Dec 11, 2025, 06:36 PM UTC

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

  3. resolved Dec 11, 2025, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2025

Ably website, customer dashboard & Control API issues

Detected by Pingoru
Dec 05, 2025, 08:59 AM UTC
Resolved
Dec 05, 2025, 09:18 AM UTC
Duration
19m
Affected: Ably Website
Timeline · 3 updates
  1. investigating Dec 05, 2025, 08:59 AM UTC

    Customers may be experiencing connectivity issues affecting our website (ably.com), customer dashboards, the Control API (control.ably.net), the Ably blog and CMS. Our realtime services are not affected by this issue at this time.

  2. monitoring Dec 05, 2025, 09:14 AM UTC

    The service is recovering, we are continuing to monitor.

  3. resolved Dec 05, 2025, 09:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 25, 2025

High pusher, pubnub and mqtt adaptor error rate

Detected by Pingoru
Nov 25, 2025, 11:38 AM UTC
Resolved
Nov 25, 2025, 12:11 PM UTC
Duration
32m
Affected: Asia-Pacific (Singapore)Asia Pacific (Sydney)Europe (Ireland)Europe (Frankfurt)US East (Northern Virginia)US East (Ohio)US West (Northern California)
Timeline · 4 updates
  1. monitoring Nov 25, 2025, 11:38 AM UTC

    There was a high error rate with pusher, pubnub, and mqtt protocol adaptors in one region for a duration of 11 minutes from 11:25 UTC in the eu-west-1 (Ireland) region. This has now been resolved. No other region was affected

  2. monitoring Nov 25, 2025, 12:01 PM UTC

    There is a high error rate for all translator protocol adaptors globally (pusher, pubnub and mqtt). We have identified the issue and are working on a fix.

  3. monitoring Nov 25, 2025, 12:04 PM UTC

    We have resolved the issue and the error rate has now dropped across all affected regions. We are continuing to monitor.

  4. resolved Nov 25, 2025, 12:11 PM UTC

    The incident is now resolved. The elevated protocol adaptor error rate affected EU regions for 36 minutes from 11.25am-12.01pm UTC, for 15 minutes in US regions from 11.50am-12.05pm UTC, and for 14 minutes in AP regions from 11.48am-12.02pm UTC.

Read the full incident report →