v2.1.76

2026-03-17 · Source: Claude Code Changelog · Field: Technology & Digital — Software Development & Engineering · Depth: Fundamental Awareness, quick

Summary

The provided content indicates a user has exceeded a secondary rate limit on GitHub, prompting a temporary restriction on further requests. The system advises waiting a few minutes, potentially up to an hour, before attempting new requests. It also suggests that signing in to a GitHub account might grant a higher rate limit. Users are directed to review GitHub's Terms of Service for information on scraping and its implications, and provided links to contact support, check GitHub's status, and follow @githubstatus for updates.

Key takeaway

For developers or automated systems encountering "Too many requests" on GitHub, your immediate action should be to pause operations and wait for the rate limit to reset, which could take up to an hour. If you are not signed in, consider authenticating your requests, as this often provides a more generous rate limit, enabling continued access to GitHub resources.

Key insights

GitHub imposes secondary rate limits, requiring users to wait or sign in to continue operations.

Principles

• Rate limits protect service stability.
• Authentication can increase request allowances.

In practice

• Wait for rate limit reset.
• Sign in to GitHub for higher limits.
• Review Terms of Service for scraping.

Topics

• Rate Limiting
• GitHub API
• Error Messages
• Web Scraping

Best for: CTO, VP of Engineering/Data, Director of AI/ML, Software Engineer

Related on AIssential

• v2.1.72 — GitHub imposes secondary rate limits to manage request volume, requiring users to wait or sign in for higher access.
• OpenAI Codex referral program rewards users with extra rate resets — OpenAI's new flexible rate limits for Codex empower users and open doors for future monetization through banked resets.
• The Pulse: AI load breaks GitHub – why not other vendors? — GitHub's severe reliability issues stem from under-preparedness for AI-driven load spikes and complex infrastructure migration.
• Rate Limiter System Design: Token Bucket, Leaky Bucket, Scaling — Token Bucket algorithm is the industry standard for robust API rate limiting, balancing simplicity and effectiveness.
• Quoting Kyle Daigle — GitHub's platform activity is experiencing a significant surge, with commits reaching 1 billion in 2025 and currently tracking at 275 million per week, projecting 14 billion for 2026.
• Sorry for the outages: Bot spam is pushing our servers to the limit — Bot spam, particularly from Perplexity, is causing severe website outages and service disruptions.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Claude Code Changelog.