Including timeouts in primary rate limits

At GitHub, we’re always working to make our GraphQL API more reliable for everyone. With that in mind, we’ve made a recent change: request timeouts will now count against your primary rate limit.

How this affects your integration

Under normal usage, you’re unlikely to notice a difference. But if your integration experiences timeout, you may hit your hourly rate limit sooner than expected.

What you can do

To avoid unexpected rate limiting, we recommend the following:

• Monitor your usage: Use the response headers to track your rate limit consumption and identify patterns with timeouts.
• Review your queries: Optimize your GraphQL queries to avoid requesting excessive or unnecessary data.

Learn more about rate limiting at GitHub.