Where it is raised
- Errors ingest (/api/errors/v1/ingest)
What triggers it
The batch was parsed and every event was refused for quota, so none were accepted. A batch that is only partly over quota returns 200 with counters (droppedOverQuota, droppedOverBudget) instead. When a paid overage budget is exhausted the message says Monthly overage budget reached.
Example response
POST /api/errors/v1/ingest/<key>
HTTP 429
Retry-After: 3600
{
"error": "Monthly event quota reached. Dropped events are counted and shown on your Errors dashboard.",
"reason": "over_quota",
"code": "RU-4001",
"resetsAt": "<ISO 8601 time>"
}Common causes
- An error spike consumed the month's quota.
- A noisy, known error group left unresolved and re-reported on every request.
How to fix it
- Check the Errors dashboard's drop counters to see what consumed the quota.
- Resolve or rate-limit the noisiest issue at the source.
- Upgrade the plan if your normal volume genuinely exceeds the quota; SDKs stop retrying until `resetsAt`.