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

What to do

• Check whether you use Ably Ably Platform. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 8m it lasted.

  Anything that failed between 2024-10-11 10:12 UTC and 2024-10-11 12:20 UTC may need a replay.

• Subscribe to Ably's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ably works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ably 2

1. identifiedOct 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.

   provider

2. resolvedOct 11, 2024, 12:20 PM UTC

   The fix for this has been fully rolled-out.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.