Ably Outage History

Ably is up right now

Ably had 21 outages in the last 2 years totaling 18h 31m of downtime — averaging 0.9 incidents per month.

There were 21 Ably outages since October 8, 2024 totaling 18h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ably.com

Major October 1, 2026

Elevated API Errors

Detected by Pingoru
Oct 01, 2026, 03:36 PM UTC
Resolved
Oct 01, 2026, 04:03 PM UTC
Duration
26m
Timeline · 3 updates
  1. investigating Oct 01, 2026, 03:36 PM UTC

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

  2. resolved Oct 01, 2026, 04:03 PM UTC

    Between 15:30 UTC to 15:36 UTC there were elevated errors affecting token requests in all regions resulting in 503 error responses.

  3. postmortem Oct 01, 2026, 05:20 PM UTC

    On October 1, a distributed denial-of-service \(DDoS\) attack caused elevated token-request errors across all Ably Realtime regions for approximately six minutes and intermittent unavailability of [ably.com](http://ably.com). We restored token-request service by increasing capacity and added targeted traffic-blocking and rate-limiting rules to mitigate the attack. We are strengthening endpoint protection and reviewing our firewall controls to reduce the risk of recurrence.

Read the full incident report →

Major September 7, 2026

Ably documentation pages - ably.com/docs

Detected by Pingoru
Sep 07, 2026, 11:25 AM UTC
Resolved
Sep 07, 2026, 11:32 AM UTC
Duration
7m
Affected: Ably Website
Timeline · 3 updates
  1. investigating Sep 07, 2026, 11:25 AM UTC

    Customers may be experiencing issues viewing documentation pages on our website ably.com/docs. Our realtime services are not affected by this issue at this time.

  2. monitoring Sep 07, 2026, 11:28 AM UTC

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

  3. resolved Sep 07, 2026, 11:32 AM UTC

    This incident has been resolved.

Read the full incident report →

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 →

Major August 13, 2025

Elevated Realtime errors in EU regions

Detected by Pingoru
Aug 13, 2025, 12:47 PM UTC
Resolved
Aug 13, 2025, 01:25 PM UTC
Duration
37m
Affected: Push Notifications - Europe (Ireland)Europe (Ireland)Europe (Frankfurt)
Timeline · 3 updates
  1. investigating Aug 13, 2025, 12:47 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 13, 2025, 01:12 PM UTC

    Issue has been resolved, we are monitoring.

  3. resolved Aug 13, 2025, 01:25 PM UTC

    The incident has been resolved

Read the full incident report →

Minor July 18, 2025

Elevated Realtime Publish Errors - eu-west-1

Detected by Pingoru
Jul 18, 2025, 02:58 PM UTC
Resolved
Jul 18, 2025, 03:40 PM UTC
Duration
41m
Affected: Europe (Ireland)
Timeline · 4 updates
  1. investigating Jul 18, 2025, 02:58 PM UTC

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

  2. investigating Jul 18, 2025, 02:58 PM UTC

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

  3. investigating Jul 18, 2025, 03:23 PM UTC

    We are continuing to investigate an elevated level of realtime publish errors in eu-west-1 for a single customer. There is no wider impact.

  4. resolved Jul 18, 2025, 03:40 PM UTC

    We have identified the issue which relates to an internal error rate. While this was elevated, there was no impact to customers.

Read the full incident report →

Minor June 3, 2025

Elevated Errors in us-east-1

Detected by Pingoru
Jun 03, 2025, 05:41 AM UTC
Resolved
Jun 03, 2025, 05:41 AM UTC
Duration
—
Affected: Push Notifications - US East (North Virginia)US East (Northern Virginia)
Timeline · 5 updates
  1. investigating Jun 03, 2025, 04:25 AM UTC

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

  2. investigating Jun 03, 2025, 04:50 AM UTC

    We are continuing to investigate. We have also identified issues with push delivery in us-east-1 and are investigating.

  3. monitoring Jun 03, 2025, 05:03 AM UTC

    The us-east-1 region has been disabled, so realtime connections and API traffic should be handled without issue in other regions. Push delivery is also back to normal. We are continuing to monitor.

  4. monitoring Jun 03, 2025, 05:04 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 03, 2025, 05:41 AM UTC

    Service is restored in us-east-1 and all services are operating normally.

Read the full incident report →

Minor May 9, 2025

Elevated Push Notification Error Rate

Detected by Pingoru
May 09, 2025, 06:00 PM UTC
Resolved
May 09, 2025, 08:50 PM UTC
Duration
2h 50m
Affected: Push Notifications - US East (North Virginia)
Timeline · 3 updates
  1. investigating May 09, 2025, 08:03 PM UTC

    We're experiencing an elevated level of push notification errors and are currently investigating the issue.

  2. monitoring May 09, 2025, 08:46 PM UTC

    Some push notification messages may be delayed. We have deployed a fix and are now monitoring.

  3. resolved May 09, 2025, 08:50 PM UTC

    Push notification errors have reduced and this issue is now resolved.

Read the full incident report →

Notice February 17, 2025

Elevated error rates for some applications in us-east-2

Detected by Pingoru
Feb 17, 2025, 02:56 AM UTC
Resolved
Feb 17, 2025, 03:11 AM UTC
Duration
14m
Affected: US East (Ohio)
Timeline · 3 updates
  1. investigating Feb 17, 2025, 02:56 AM UTC

    We're investigating elevated error rates for some applications in us-east-2. We will update with more information when we have it

  2. investigating Feb 17, 2025, 03:04 AM UTC

    Error rates are back to normal. We are continuing to investigate what the issue was.

  3. resolved Feb 17, 2025, 03:11 AM UTC

    Error rates have been back to normal since 0255 (UTC).

Read the full incident report →

Notice November 5, 2024

Some ingress integration rules not running in eu-central-1

Detected by Pingoru
Nov 05, 2024, 10:41 AM UTC
Resolved
Nov 05, 2024, 02:01 PM UTC
Duration
3h 19m
Affected: Integrations
Timeline · 6 updates
  1. identified Nov 05, 2024, 10:41 AM UTC

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

  2. monitoring Nov 05, 2024, 11:49 AM UTC

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

  3. monitoring Nov 05, 2024, 12:08 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Nov 05, 2024, 12:28 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Nov 05, 2024, 02:00 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Nov 05, 2024, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2024

Elevated channel attach failure rates in ap-southeast-2

Detected by Pingoru
Oct 21, 2024, 01:47 PM UTC
Resolved
Oct 21, 2024, 02:08 PM UTC
Duration
20m
Affected: Asia Pacific (Sydney)
Timeline · 2 updates
  1. identified Oct 21, 2024, 02:12 PM UTC

    At 13:47 UTC we observed elevated failure rates of channel attaches to some channels in the ap-southeast-2 (Sydney) region. We have identified what we believe to be the cause and rolled out a mitigation, which completed at 14:08. No other regions were affected.

  2. resolved Oct 21, 2024, 02:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 11, 2024

Occasional anomalously-high `messages.inbound.rest.messages.refused` stat when a rest publish is refused

Detected by Pingoru
Oct 11, 2024, 10:12 AM UTC
Resolved
Oct 11, 2024, 12:20 PM UTC
Duration
2h 7m
Affected: Ably Platform
Timeline · 2 updates
  1. identified Oct 11, 2024, 10:12 AM UTC

    Since Monday 7th, a REST publish that was refused by Ably's servers (for example, for being above the maximum message size) had a small probability of contributing an incorrect, anomalously high message inbound refused stat (key `messages.inbound.rest.messages.refused`) to app and account stats. Since refused messages do not count towards a customer's chargeable message quota, this bug did not result on anyone being charged more or having their quota used up. However, in a couple of cases it did momentarily trigger a customer's account-wide instantaneous message rate limit (`messages.maxRate`), for which we apologise. We are rolling out a fix for this currently.

  2. resolved Oct 11, 2024, 12:20 PM UTC

    The fix for this has been fully rolled-out.

Read the full incident report →

Minor October 8, 2024

Elevated rates of 502 responses

Detected by Pingoru
Oct 08, 2024, 03:10 PM UTC
Resolved
Oct 08, 2024, 04:32 PM UTC
Duration
1h 21m
Affected: Ably Platform
Timeline · 3 updates
  1. investigating Oct 08, 2024, 03:10 PM UTC

    We have been alerted to an issue where our edge proxy (CloudFront) is responding to requests with 502 errors at an elevated (but still low) rate, and are investigating. If you are experiencing any issues, please let us know at https://ably.com/support.

  2. monitoring Oct 08, 2024, 03:54 PM UTC

    We have identified and mitigated this issue and are now monitoring.

  3. resolved Oct 08, 2024, 04:32 PM UTC

    This incident has now been resolved.

Read the full incident report →