SID Quota
sid-quota appears when your account has reached a limit defined by your current plan. The dashboard stays visible and existing data is unchanged, but new beacons may stop being counted until the limit resets or your plan changes.
What triggers sid-quota
Each plan on StatelessID includes defined limits — the number of sites you can register, the number of beacons your sites can send in a billing period, or both. When an incoming beacon would exceed a limit, the server applies the quota rule rather than counting the visit. The specific limit and the specific rule — whether beacons are queued, discarded, or simply not counted — depend on the plan.
The most common trigger is beacon volume: your sites collectively received more page loads than the plan allows in the current period. This can happen gradually over time as a site grows, or suddenly after a piece of content is shared widely and traffic spikes in a short window. It can also happen if you registered more sites than your plan allows, though site limits are enforced at registration time rather than at beacon time.
sid-quota is a plan-limit event, not a technical error. Your instrumentation is working correctly — beacons are reaching the server. The server is choosing not to count some of them because the plan limit has been reached. The distinction matters because the fix is a plan change, not a debugging session.
What happens to your dashboard while at quota
The dashboard remains fully accessible. All data recorded before the quota was reached is intact and visible. You can browse all your sites, review historical counts, filter by date range, and export what is there. The quota affects only the recording of new beacons going forward in the current period — it does not delete or hide existing data.
If some beacons are being discarded at quota, the page view counts in your dashboard will be lower than the actual number of page loads your site is receiving during the over-quota period. The gap between actual traffic and recorded traffic grows as long as the quota remains exceeded. This is the practical consequence of exceeding the limit: your dashboard undercounts by an increasing amount until the period resets or the plan changes.
How to check your current usage
The dashboard or the admin panel includes a usage view that shows beacon volume for the current period alongside the plan limit. Check how close your usage is to the limit and when the period resets. If you are consistently reaching the limit before the period ends, the plan is no longer sized for your current traffic.
Usage figures reflect the beacons that were counted, not the total that arrived. If you have already exceeded the limit, the usage figure shows what was counted before the limit was hit — it does not include the beacons that were dropped. The gap between what the usage figure shows and the limit is not the remaining capacity; the limit was reached when the usage figure reached the plan ceiling.
How to resolve sid-quota
There are two paths: wait for the current period to reset, or move to a plan that supports your traffic volume. If your traffic spike is temporary — a single piece of content went viral, a campaign drove unusual volume for a few days — waiting for the period reset is reasonable. Recording will resume at the start of the next period at the full plan limit.
If your traffic has grown to a point where you regularly approach or exceed the limit before the period ends, the right action is to choose a plan that fits. See the Pricing page for the current plan options and their limits. Moving to a higher plan takes effect for the remainder of the current period — you do not have to wait for the next cycle.
Troubleshooting
If you see sid-quota but believe your traffic is well below the plan limit, check whether all your registered sites are counted together toward the limit or whether each site has its own separate quota. If limits are pooled across all sites, a single busy site can exhaust the quota and affect recording for all your other sites in the same account.
If the period reset came and went but sid-quota persists, confirm that the reset date in the usage panel has actually passed and that the usage counter has reset to zero. If the counter did not reset, there may be a billing issue affecting your plan state — see the sid-billing article for guidance on resolving subscription problems that can lock plan limits in an over-quota state.
If you are testing your instrumentation and generating high beacon volume in a short period, that test volume counts toward your plan limit the same as real visitor traffic. High-volume testing on a lower-tier plan can trigger sid-quota before real traffic has a chance to grow into it. Consider testing in a development environment registered under a separate site with modest beacon expectations, or conduct load testing in a window close to the period reset.