GitHub API Rate Limit Exceeded

An unauthenticated call to the GitHub REST API is capped at 60 requests/hour per IP. Authenticated calls get 5,000/hour per user (up to 15,000/hour for a GitHub App on Enterprise Cloud). Past the limit, every call returns 403 with X-RateLimit-Remaining: 0 until the reset time in the response headers.

What the limits actually are

Caller typeLimit
Unauthenticated60 requests/hour per IP
Authenticated (personal token)5,000 requests/hour
GitHub App (Enterprise Cloud)up to 15,000 requests/hour
GraphQL API5,000 points/hour, cost-based, separate pool

Fix it right now

  1. Check the response's X-RateLimit-Remaining and X-RateLimit-Reset headers to see exactly when the limit clears.
  2. Add an Authorization: Bearer <token> header — this alone jumps the ceiling from 60/hour to 5,000/hour.
  3. If several CI jobs or services share one outbound IP (common on shared build infra or an office NAT), the 60/hour unauthenticated ceiling is shared across all of them — the fix is a token per caller, not waiting for a bigger shared pool.
  4. Cache responses already fetched instead of re-polling the same endpoint.

Self-hosted: no shared global limit

On a self-hosted instance like Rithub, the API isn't shared with millions of other callers worldwide — any rate limiting is scoped to your own server, set by you, not a fixed global ceiling GitHub applies to every unauthenticated caller on the internet. Combined with built-in CI runners, integrations that poll the API don't compete with unrelated traffic for the same 60-request bucket.

Sign up freeImport from GitHub