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

- Provider: [Ably](https://down.guide/providers/ably)
- Confidence: Confirmed
- Impact: Operational
- lasted 2h 8m
- started 2024-10-11 10:12 UTC
- Ably Platform
- id: DWN-55cb45b51a
- Official page: https://stspg.io/ztqw94pgbg6q

## Updates from Ably
### 2024-10-11 10:12 UTC: 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.

### 2024-10-11 12:20 UTC: resolved
The fix for this has been fully rolled-out.

From the builder: does your app depend on Ably? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=ably) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Ably.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-55cb45b51a), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.