Quick answer
GitHub Copilot documents monthly reset as 1st of each month at 00:00:00 UTC. Unused requests do not carry into the next month.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| monthly resetUnused requests do not carry into the next month. | 1st of each month at 00:00:00 UTC | Request-based billing | GitHubAug 22, 2026 |
Why does this limit matter?
Teams should use UTC rather than local midnight when forecasting when a depleted allowance returns.
This value is scoped to Request-based billing; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Check the account billing model, current counter, UTC time, and any additional-request budget.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Additional metered requests and included models can change what remains usable after the allowance is exhausted.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related