Billing / At the limit
Overages & Limits
There is no metered overage charge. When a limit is reached, requests stop being served normally until the cycle resets or you upgrade.
Behavior
What happens at 100%
- The metric stops
- Only the metric that hit its limit is affected. Writes and queries have separate pools, so one can continue while the other is exhausted.
- Requests still return 200
- By default an over-limit call returns a successful empty payload rather than an error.
- Usage stops growing
- Over-limit requests are not counted, so your usage figure stays at the limit.
- Stored memory is untouched
- Reaching a limit never deletes, expires, or hides anything you have already written.
Not happening
What does not happen
- No per-request overage charge is added to your invoice for exceeding a monthly limit.
- No automatic upgrade to a larger plan.
- No retroactive billing for requests that were not served.
Your invoice reflects the plan you are subscribed to. Check the invoices page for what a paid invoice contains.
Recovery
Getting back to normal
- Confirm which metric is exhausted on the usage dashboard — writes and queries fail differently in your product.
- Reduce avoidable calls: cache repeated identical queries, and stop writing text that is not durable.
- Upgrade if the workload is genuinely larger than the plan. An upgrade takes effect immediately.
- Otherwise wait for the cycle reset, and add an alert so the next month is not a surprise.
Was this page helpful?