Historique des pannes de Ably

1. 20 août 2026 à 19:29 UTCinvestigating

   Nous traversons un niveau élevé d'erreurs dans ap-sud-est-1 et nous examinons actuellement la question.

2. 20 août 2026 à 19:41 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

3. 20 août 2026 à 19:42 UTCidentified

   Nous continuons de travailler sur une solution à ce problème. Les taux d'erreurs ont diminué à des niveaux normaux et le service est actuellement pleinement opérationnel.

4. 20 août 2026 à 20:12 UTCmonitoring

   Un correctif a été mis en place et nous suivons le résultat. Les taux d'erreurs ont diminué à des niveaux normaux et le service est actuellement pleinement opérationnel.

5. 20 août 2026 à 20:24 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 20 août 2026 à 19:07 UTCinvestigating

   Nous connaissons un niveau élevé d'erreurs dans la région ap-sud-est-1 et nous examinons actuellement la question.

2. 20 août 2026 à 19:10 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 février 2026 à 10:19 UTCinvestigating

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

2. 17 février 2026 à 10:24 UTCidentified

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

3. 17 février 2026 à 10:30 UTCmonitoring

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

4. 17 février 2026 à 10:32 UTCresolved

   This incident has been resolved.

1. 14 février 2026 à 05:57 UTCinvestigating

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

2. 14 février 2026 à 06:00 UTCidentified

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

3. 14 février 2026 à 06:01 UTCmonitoring

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

4. 14 février 2026 à 06:05 UTCresolved

   This incident has now been resolved.

1. 21 janvier 2026 à 18:11 UTCinvestigating

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

2. 21 janvier 2026 à 18:29 UTCidentified

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

3. 21 janvier 2026 à 18:36 UTCmonitoring

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

4. 21 janvier 2026 à 19:52 UTCresolved

   This incident has been resolved.

1. 11 décembre 2025 à 18:36 UTCinvestigating

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

2. 11 décembre 2025 à 18:36 UTCidentified

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

3. 11 décembre 2025 à 18:59 UTCresolved

   This incident has been resolved.

1. 5 décembre 2025 à 08:59 UTCinvestigating

   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. 5 décembre 2025 à 09:14 UTCmonitoring

   The service is recovering, we are continuing to monitor.

3. 5 décembre 2025 à 09:18 UTCresolved

   This incident has been resolved.

1. 25 novembre 2025 à 11:38 UTCmonitoring

   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. 25 novembre 2025 à 12:01 UTCmonitoring

   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. 25 novembre 2025 à 12:04 UTCmonitoring

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

4. 25 novembre 2025 à 12:11 UTCresolved

   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.

1. 29 octobre 2025 à 08:57 UTCinvestigating

   We are experiencing an elevated level of errors impacting Ably Reactor Webhook delivery. We have identified the issue and are currently deploying a fix.

2. 29 octobre 2025 à 08:58 UTCidentified

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

3. 29 octobre 2025 à 09:21 UTCidentified

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

4. 29 octobre 2025 à 09:26 UTCidentified

   A fix has been deployed and Ably Reactor Webhook delivery service is recovering.

5. 29 octobre 2025 à 09:42 UTCresolved

   This incident has been resolved.

6. 7 novembre 2025 à 09:16 UTCpostmortem

   # Summary of incident affecting the Ably production service on 28-29 October - investigation and conclusions ## Overview There was an incident affecting Ably's service between 28 and 29 October 2025, which affected the delivery of webhooks. The impact of the incident lasted from 1134 on 28 October to 0936 on 29 October \(all times UTC\). The incident occurred as a result of the deployment of new webhook functionality that was incompatible with many already-configured webhook rules. Now we have a good understanding of the underlying problem, the various factors that led to that having customer impact, and the effectiveness of our response in this case. ## Background Ably operates a number of production clusters for its service around the globe. There is a main production cluster that services the majority of customer accounts, plus a small number of dedicated clusters for specific accounts. Each of the clusters has a presence in multiple regions in a globally federated system. ### Ably integration rules Ably processes messages that are published on channels, and directs those to realtime subscribers on those channels, and also directs them to other targets as configured by integration rules. Multiple targets are supported for egress integration rules, including message queues \(Kafka, AMQP\) and generic HTTP endpoints \(webhooks\). Rules are configured via a control plane which supports: * direct interactive \("click-ops"\) configuration in the Ably dashboard; * a [Control API](https://ably.com/docs/api/control-api); * a [Terraform Provider](https://ably.com/integrations/ably-terraform-provider) which acts through the Control API. The source of truth for integration rule definitions is Ably's core "realtime" platform, and the other services \(the website and control API service\) obtain access to that via an internal provisioning API. Integration rule definitions comprise some attributes that are generic \(such as `channelFilter` that specifies which channels the rule applies to\), and some that are specific to each type of integration rule target \(such as the target endpoint, credentials, and any protocol-specific attributes\). Some generic attributes - ie attributes that are capable of having a meaning for multiple rule types - are not universally supported, since the evolution of rule features is based on adoption and priority. As a result, the schema for integration rule definitions contains multiple optional generic attributes as well as a wide range of type-specific attributes. One generic feature is an option that enables a custom set of trust anchors \(TLS certificates\) to be configured for a rule; this is to support integrations that target TLS endpoints that have a self-signed certificate rather than certificates issued by a public Certificate Authority \(CA\). This feature is used by customers having self-hosted endpoints, either as part of development/CI infrastructure, or as internally-facing production services where the operational effort of maintaining a certificate from a public CA is not justified. At the time of the incident custom trust anchors were supported for Apache Pulsar and Kafka rules, and support had just been added for webhooks. ### Ably's service deployment process Ably adopts a staggered deployment approach whereby each change is deployed gradually, minimising the adverse impact of any regression that might exist in new software versions having escaped all prior test phases. Changes are typically deployed on a weekly basis; usually in the main \(multi-tenanted\) cluster this means that changes are deployed to the ap-southeast-2 \(Sydney\) region first, and error rates monitored, before deploying to the remaining regions starting the following day. However, if a deploy needs to be expedited for any reason, subsequent regions can be deployed after a change has been in ap-southeast-2 for only a few hours. Most monitoring is automated; metrics are gathered for a wide range of service health metrics, including the rates of logged error events, and the rate of error API responses. When error metrics exceed a threshold then on-call engineers are paged to investigate. Since the majority of Ably's infrastructure comprises immutable EC2 instances, any deploy consists of deploying new instances with the new software version in parallel with retirement of superseded instances. For a normal deploy this process happens over the course of several hours so that the number of instances being retired at any given time is small, minimising any impact of the update on existing traffic. If a deploy needs to be accelerated, such as if making an emergency rollback, then deployment would more typically involve deploying a full complement of replacement instances immediately, followed by termination of old instances at a rate that reflects the urgency of the operation. Immediate and abrupt termination of multiple instances simultaneously leads to a greater risk of loss of ephemeral channel state, so even in accelerated rollbacks the preference is for old instances to be terminated gradually so that there is an orderly shedding of load so as to avoid any data loss. ## As it happened A change to add support for custom trust anchors was implemented, and this change was part of a set of changes deployed in a staggered deployment starting on 28 October. This happened in ap-southeast-2 from 1134 and, since this change set also included a fix for an unrelated problem, it was expedited and started in other regions from around 1500. Starting at 1940 on 28 October there was a handful of customer reports of a problem with webhook delivery. There were two independent customer reports of issues on 28 October and a handful of reports overnight. At 0731 on 29 October Ably's customer support team escalated the problem reports to Ably's engineering team for investigation. At 0745 an incident was declared, on-call engineers were paged and investigation started. The problem was determined to be a regression introduced in the previous day's deploy. At 0746 a rollback process was initiated to revert the changes. Rollback was initiated first in ap-southeast-2. At 0811 rollback was initiated for all regions and dedicated clusters that had received the changes. The rollback completed at 0936 and errors dropped to zero. ## Investigation The investigation aimed to understand: * the cause of failed webhook invocations; * how Ably's testing had failed to detect the regression; * how Ably's monitoring had failed to detect the regression; * the effectiveness of the response, including the time taken to respond following the first customer problem reports. The conclusions of the investigation are summarised below. ### The cause of failed webhook invocations The new code that caused the problem was adding support for custom trust anchors for webhooks. This code would look in the rule configuration for a configured set of trust anchors and, if present, use those instead of the system set of trust anchors for public CAs. The problem was caused by the fact that a significant number of preexisting rule definitions already had an empty set of trust anchors configured. The new code then used that empty set instead of the default set and failed to verify the certificate chain for any TLS endpoint. These failures were logged internally with a severity that classifies the event as a client configuration error rather than a system error. The presence of the empty trust anchor set in existing rule definitions was due to a long-standing behaviour in the web \(dashboard and control API\) services that create and update rules via the realtime platform's provisioning API. When custom trust anchor support was first added for Pulsar rules \(in November 2021\), the set of custom trust anchors became a generic rule attribute; but the web service would configure an empty set instead of a true zero value when custom trust anchors were unset. This meant that any rules that had been created since November 2021, even for types that did not initially support custom trust anchors, would have an empty set configured. Remedial actions identified in this area are as follows. **Fix the immediate regression.** As an interim behaviour, interpret an empty custom trust anchor array as if custom trust anchors are unset \(and so use the default trust anchors\). **Correct web service behaviour.** Update the web service so that a true zero value is set instead of an empty array when custom anchors are not set. **Correct the configuration of existing rules.** Perform a database update for all existing rule definitions that have an empty array configured. ### The failure of tests to detect the regression The relevant tests are a combination of unit tests and integration tests within the test suite of the realtime platform. Unit test coverage includes test coverage of all webhook configuration options \(and new tests were included with the deployed change\), plus tests for different endpoint behaviours \(HTTP 1 vs HTTP/2 for example\). Unit tests mock different parts of the surrounding code and system in order to have tests that are as targeted as possible. Integration tests include full end-to-end tests that create integration rules via the provisioning API that point to a range of endpoints existing as part of the CI system. The reason that none of these tests identified the problem is that none used the configuration in the same way as the web service; in particular, any rule that did not have custom trust anchors would be configured with a null entry. There was no expectation in the tests that an empty set should be interpreted as having no custom configuration. There was no integration test coverage of the end-to-end behaviour when rules are created via the web service. Remedial actions identified in this area are as follows. **Improve web service testing of integrations.** This should at least include: * create web service unit tests that verify that an unset custom trust anchor configuration results in a zero value being configured. * create web service integration tests that verify end-to-end behaviour involving creation of rules via the web service, with and without custom trust anchors set. ### The failure of monitoring to detect the regression Ably monitors a wide range of service metrics and alerts relevant engineering teams when those metrics indicate a service problem. Monitored metrics include errors logged internally whilst servicing customer traffic, the rate of error responses to customer requests, and the rate of errors or failures in traffic that is generated by Ably specifically for service monitoring. For this last category, Ably operates a series of "quality of service", or QoS, traffic generators that exercise a range of service functionality, so certain classes of failure relating to deployment can be identified that would not be identifiable via CI. Errors - both those logged internally and customer-visible error responses - can be classified broadly into: * bad requests - that is, operations that fail because the arguments or parameters of the request are invalid. When these errors are associated with an error code, it is typically in the 4xx range - these include general bad requests, plus authentication and authorisation failures; * internal errors - that is, errors that arise performing some operation that ought to succeed, but fails because of an issue \(eg an unexpected exception, a failure to communicate over the network, or an assertion failure\). When these errors are associated with an error code, it is generally in the 5xx range. A high rate of internal errors - either in our internal logs, or in customer-visible responses - is an indication of a problem with the service. A high rate of bad requests is more typically a problem on the customer side; an application is attempting operations that cannot succeed. All 5xx \(internal error\) metrics are monitored and alerts are generated when they exceed a threshold indicating a problem. Many 4xx \(bad request\) metrics are monitored but in most situations these do not generate alerts. This is for several reasons: * most are not an indication of a system problem; there is simply some invalid operation being attempted by a client; * all public endpoints are subject to a very high rate of spurious requests that fail authentication and authorisation checks, so the general rate of 4xx errors is high. Similarly, problems with invocation of a webhook \(or other rule target\) are usually a result of misconfiguration of the rule, or unavailability of the target endpoint, and these are classified with a 4xx status code. There is a material background level of such errors. Given the very high rate of background 4xx errors on external endpoints, it is generally difficult to identify any pattern on those endpoints that is indicative of a system problem. Notwithstanding this, all Ably Enterprise accounts have alerts set up both for 4xx and 5xx error metrics. 4xx alerts do not generally page an engineer out-of-hours, but both engineering and customer success teams get notified when there is an unexpected elevated rate of 4xx errors for an Enterprise customer. The configuration of those accounts within Ably's monitoring and alerting systems is added when that customer is onboarded as an enterprise customer. In this incident the overall increase in rule invocation failures was not significant in comparison with the normal ambient background error rate so, based on those metrics, there was no clear signal of there being a problem, and it was not sufficient to cross the alerting threshold on any existing enterprise accounts. Many customers with the highest usage volumes had rules created before November 2021, which were unaffected by the problem. At the time of the incident, QoS monitoring simulated traffic for some integrations but not webhooks. Remedial actions identified in this area are as follows. **Improve the ability in metrics and alerts for integration rules to discriminate between Ably problems and end-user problems.** Although most errors are a result of configuration problems, or problems in end-user infrastructure, it is still clearly possible for Ably regressions to also generate errors. We need to have more intelligent metrics and alerts that identify such occasions without creating an unsustainable number of false-positives. One possibility is to create alerts based on individual metrics labelled by rule type, to ensure that an increase in error rate for an individual rule type is alerted, even if that increase is not a material fraction of errors across all rule types. Another possibility is to correlate error levels with deploy events, or with software versions, so if a variation in error rate is correlated with a code change it is more likely to trigger an alert. **Add webhook tests to QoS monitoring.** Continuous testing in a production setting of simulated traffic should be extended to include webhooks. ### The effectiveness of the response From the first customer impact of this issue to the final resolution was 22 hours. This is far too long. Ably's response in this incident led to delays at multiple stages: * from the time of the problematic code being deployed to the first reported issue was around 8 hours; * from the first report to raising an incident was around 12 hours; * the full rollback, from the time that an incident was declared, was nearly 2 hours. Of course, had there been suitable alerting for the production problem we would have reacted sooner; but this timeline reflects the fact that even with the information we did have, the response was slow. This was due to a combination of factors: * the reports received were all received outside of business hours and, given that the customers raising those reports were not enterprise customers, there was no out-of-hours process to review them; * there was some delay before the support team correlated multiple reports to conclude that there was a problem with the delivery of webhooks; * the rollback process was comparatively slow, deliberately avoiding a more disruptive abrupt rollback since the issue had impact for a relatively small number of customers. The remedial actions in this area are as follows. **Review processes for handling and escalating issue reports out-of-hours.** Customers on lower support tiers can legitimately expect slower response times to deal with any individual issues or questions they have, but when an Ably problem arises that affects them there is no means for the relevant response team to be made aware. We will review our processes with the aim of improving support in these situations. ## Conclusion The service issues were the direct result of a regression in the Ably service - specifically, an incompatibility between a new feature \(custom trust anchors for webhooks\) and the existing state of rule configurations. The cause of the extended duration of the incident was that the classification and rate of failed delivery events resulted in no alert being generated, which meant that Ably was not aware of the ongoing problem until it was reported by customers. Although it is difficult to monitor 4xx error rates effectively, because of the high background level of such errors, there is clearly a need to improve on the current situation where Ably regressions can go undetected. There was significant additional delay in triggering a response because the reports were received on a support channel that was not monitored out of business hours. Once alerted to the problem, Ably initiated the response quickly, but the operational nature of the rollback meant that it took nearly two hours until it was completed. We take service continuity very seriously, and this incident represents another opportunity to learn and improve the level of service we are committed to providing for our customers. We are sorry for the disruption that was experienced in this instance, and are committed to identifying and implementing remedial actions so that we eliminate the risk of similar failures in the future.

1. 9 octobre 2025 à 14:24 UTCresolved

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

1. 13 août 2025 à 12:47 UTCinvestigating

   We are currently investigating this issue.

2. 13 août 2025 à 13:12 UTCmonitoring

   Issue has been resolved, we are monitoring.

3. 13 août 2025 à 13:25 UTCresolved

   The incident has been resolved

1. 18 juillet 2025 à 14:58 UTCinvestigating

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

2. 18 juillet 2025 à 14:58 UTCinvestigating

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

3. 18 juillet 2025 à 15:23 UTCinvestigating

   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. 18 juillet 2025 à 15:40 UTCresolved

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

1. 3 juin 2025 à 04:25 UTCinvestigating

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

2. 3 juin 2025 à 04:50 UTCinvestigating

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

3. 3 juin 2025 à 05:03 UTCmonitoring

   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. 3 juin 2025 à 05:04 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3 juin 2025 à 05:41 UTCresolved

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

1. 9 mai 2025 à 20:03 UTCinvestigating

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

2. 9 mai 2025 à 20:46 UTCmonitoring

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

3. 9 mai 2025 à 20:50 UTCresolved

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

1. 17 février 2025 à 02:56 UTCinvestigating

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

2. 17 février 2025 à 03:04 UTCinvestigating

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

3. 17 février 2025 à 03:11 UTCresolved

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

1. 5 novembre 2024 à 10:41 UTCidentified

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

2. 5 novembre 2024 à 11:49 UTCmonitoring

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

3. 5 novembre 2024 à 14:00 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 5 novembre 2024 à 14:01 UTCresolved

   This incident has been resolved.

1. 21 octobre 2024 à 14:12 UTCidentified

   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. 21 octobre 2024 à 14:17 UTCresolved

   This incident has been resolved.

1. 11 octobre 2024 à 10:12 UTCidentified

   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. 11 octobre 2024 à 12:20 UTCresolved

   The fix for this has been fully rolled-out.

1. 8 octobre 2024 à 15:10 UTCinvestigating

   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. 8 octobre 2024 à 15:54 UTCmonitoring

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

3. 8 octobre 2024 à 16:32 UTCresolved

   This incident has now been resolved.

1. 2 octobre 2024 à 17:09 UTCresolved

   For most of the production cluster, between 13:05 and 14:02 UTC on 2024-10-01, a small proportion of SSE connections were disconnected 30 seconds after establishing a connection. For the duration of that 30s they still worked fine, and connection resumption was working correctly, so this should not have caused any missed messages. The net effect would have been a small increase in subscribe latency about once every 30s. Only the SSE endpoint was affected; websocket traffic (including anyone using an Ably SDK) was not. For customers connected to ap-southeast-2 (Sydney), the duration of the effect was much longer, between 10:06 on 2024-09-30 to 14:02 on 2024-10-01.