rewindex

CompaniesAblyIncidents

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

No impact listedStatus: resolvedStarted Resolved (2.1 h)2 updatesstspg.io (opens in new tab)

Affected components: Ably Global Service AvailabilityAbly Platform

Timeline of updates

  1. identified

    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

    The fix for this has been fully rolled-out.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Ably, started 2024-10-11 10:12 UTC, resolved after 2.1 h, 2 update(s).

Title
Occasional anomalously-high `messages.inbound.rest.messages.refused` stat when a rest publish is refused
Vendor
Ably
Date
URL
https://rewindex.com/company/ably/incidents/yz2cz89k9q4d

Ably profileRecent Ably incidentsAll outages on October 11, 2024Ably in October 2024MarkdownJSON