GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Haarlem	Sign in	19 hours ago
Villemomble	Website Down	19 hours ago
Bordeaux	Website Down	5 days ago
Ingolstadt	Errors	9 days ago
Paris	Website Down	10 days ago
Berlin	Website Down	11 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Cynthia Ozumba (@CynthiaOzumba) reported 6 minutes ago

  Stop telling them you're a "Fast Learner." Show them a screen recording of a dashboard you built, a 1-page strategy you wrote, or a technical problem you solved. Link your Notion Portfolio or GitHub at the very top. Let the work speak before they even see your Location.

• 
  schwiftyrick (@schwiftyrick0) reported 7 minutes ago

  @mattpocockuk How do you keep GitHub issues in sync when you roll back commits? I use commits as an undo trail, but closed issues stay closed even after the implementing commit is gone. Curious how you handle the drift.

• 
  mina (@minallkamel) reported 8 minutes ago

  do rust coreutils developers even like that an lts ubuntu is using it, wouldn't that put a massive amount of pressure on them and their github issues is gonna be filled with angry ********

• 
  vikivirgon (@VikiVirgon) reported 9 minutes ago

  Yang bikin gue impressed: Qwen3.6-27B GGUF bikin 26 tool calls, nriage 15 GitHub issues dan fix dalam 1 run. Cuma butuh 12GB RAM. Local AI agent workflow yang actually work - bukan hype

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 10 minutes ago

  @FirstSquawk Anysphere passing on Microsoft to stay independent tracks. A Microsoft acquisition would push Cursor into GitHub/Copilot orbit and probably slow their release velocity. The valuation math only works if they keep shipping faster than Copilot, which needs autonomy.

• 
  Dr. Luke in China (@96Stats) reported 13 minutes ago

  Just went through their paper - REALLY smart. They might have less money to use compared to US rivals but their innovation is way better. What did they do? Well, normal AI gets expensive when your messages get long especially if you use PDFs or github codebases, because the model has to search through a hugeeee memory database every time it generates a new word. So either it becomes slow or it just doesn't read alll of what you sent. Now, check this figure out in DeepSeek's paper. Their new trick is to compress older text into smaller memory blocks, then use a lightweight “Lightning Indexer” to find only the most relevant blocks. So instead of looking at everything, it focuses on what matters. It also keeps recent text uncompressed, so it still remembers nearby details clearly. Because its all opensource/openweighted now, ChatGPT and Claude will 100% be using this too as they solved a huge problem.

• 
  Shrish Dwivedi (@Shhdwi) reported 14 minutes ago

  If you are a "VIBE CODER", you need to stop building RIGHT NOW for a whole week. yes i'm serious. you've built enough ****. your github is full of half-dead projects with 3 stars from your alt accounts. the problem isn't that you need to build more. it's that you're scared of the part that actually matters. so here's what you do: week 1 - 100% marketing. no code. zero. i don't care if you get an idea. write it down and ignore it. week 2 onwards - 80% growth, 20% building. flip the script permanently. Think hard, if just building products would make you rich, or win, why isn't everyone with Cursor or Claude Code winning. building is comfortable. posting feels like begging. i get it. but nobody's gonna stumble onto your app in a dream. you have to shove it in their face. the best product with no distribution loses to the okay product that won't shut up about itself. stop hiding in your code editor

• 
  Zakir Mavlyanov (@mavlyanov_zakir) reported 18 minutes ago

  @github Hello, My account has been suspended, and I am unable to contact support because SMS verification is not working in my country (Uzbekistan). I cannot receive the verification code on my phone number. Could you please provide an alternative way to verify my identity?

• 
  Kevin Yang (@ShanghaiYang) reported 18 minutes ago

  GitHub outage anybody?

• 
  nick (@NicsTwitz) reported 21 minutes ago

  @github the real global developer event is when github goes down and everyone discovers they cant actually code without copilot

• 
  Incarnas (@_Incarnas_) reported 21 minutes ago

  Shipped an Obsidian plugin that syncs GitHub data into the vault. Smoke tested against real GitHub. Profile sync returning 404s on every repo. Paginated calls worked fine. Issues, PRs, releases, Dependabot alerts. All clean. Just the direct calls failing.

• 
  JYN (@jynxbt) reported 22 minutes ago

  internet discovery is dead its just an endless loop of the exact same garbage > startup raises $10 m? an overengineered clone of something that already exists > repo hits 40K GitHub stars? just another rag / ai agent slop entirely generated by claude (a wrapper of wrappers) > influencer pumping a tool? a $20/mo subscription for a basic gpt-5 wrapper. the problem isn't that new things are hard to find. its that you have to sift through an ocean of absolute trash its literally just spam at this point

• 
  mobilife new (@NewMobilife888) reported 24 minutes ago

  🚨 GitHub is down. Multiple services hit by outage — developers worldwide feeling the pain. The platform that powers millions of repos just showed us why redundancy matters. Who's affected? #GitHub #DevOps #Cloud

• 
  ReversingLabs (@ReversingLabs) reported 24 minutes ago

  Attackers have hidden their changes within files that pretend to improve extensions #MCP server support. Instead their code fetches additional malicious payload from an impostor commit on @github . The compromise likely originated from the cx-bot-ghpublic service account. Spectra Assure Community users have been protected by ReversingLabs threat research team that continues to monitor the situation.

• 
  James Andrew Gardner (@JGardner7082) reported 25 minutes ago

  @sakir_bulu99159 thinking how did some uneducated sob pull this off? #motives#gatekeeper🦅🦅🦈 the fix. permantly sits in github. no more distrabution ever after 11:59 tonite its gone forever. can not ever reproduce anything. it will be a dead code. only the chosen will get it. re writing morals.

• 
  David Van Dijcke (@packlesshepherd) reported 28 minutes ago

  @_joaodias @CoarseDotInk Glad you like it and find it useful! Resuming the review is currently not implemented but seems worthwhile to do, I've added a GitHub issue for future versions. For now I'd recommend setting the reasoning effort lower or using the online version with an API key (pricier)

• 
  Magimetal 👨‍💻🤖 (@MagiMetal) reported 29 minutes ago

  @UnslothAI I'm trying to understand the language here because you mentioned that it does 26 toolcalls, but I don't see a world where any model can triage 15 GitHub issues, fix a few of them, reproduce them with tests first, and verify the fix in 26 toolcalls. That doesn't make any sense.

• 
  harderthanfire (@harderthanfire) reported 30 minutes ago

  @chribjel Does anyone seriously use copilot anymore? You get absolutely nothing in terms of usage for the price and the ecosystem has been easily surpassed. Only time I use it at work or personally is when I accidentally trigger it in the increasingly terrible github UI xD

• 
  Dinu Nair (@dinunair) reported 33 minutes ago

  @github - Quite bad support experience. Have a billing issue with a teams account and its more than 2 weeks with not even a single acknowledgment on the ticket. Are only enterprise SLAs golden ? (ticket 4261643 - if that helps)

• 
  Vácslav Turing (@TCult777) reported 37 minutes ago

  @neohk852 @peter_szilagyi yep. 30K+ views on Reddit & X just on my case, still nothing from Anthropic. GitHub is still full of issues. No replies on bunch of mails. apparently the only fix is if @bcherny personally DMs you as we can see in comments here. billion dollar company btw.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 44 minutes ago

  🇺🇸 GitHub Issues slows.. Issues platform reports degraded performance, team probes causes Hits developers midweek amid high usage, echoes past outages straining workflows on open-source projects Fix eyed soon, but prolonged delays could snag code reviews, merges ahead of weekend sprints

• 
  Florian (@FlorianCaesar) reported 45 minutes ago

  @realamlug @saltyAom Do you even realize how incredibly disrespectful it is to reply to all of this with LLM slop? Same with GitHub issues. And again, half of this reply is slop garbage and incorrect. Incredible. I’m out.

• 
  Josh (@joshmanders) reported 47 minutes ago

  My AI assistant goal is to get my version in @dunnbot to a point that I'm managing it by creating github issues and reviewing PR's. When I approve and all checks are green it'll auto merge and deploy. The real kicker is that I'll be also using Dunnbot to plan and create the issues if they aren't bug reports from the platform support system, basically allowing me to go from coding to product management.

• 
  Vishwanath Patil (@patilvishi) reported 47 minutes ago

  API Rate Limiting by Plan - Controlling Usage at Scale This is: - Used by Stripe, GitHub, OpenAI, AWS - Critical for multi-tenant SaaS - Protects systems from abuse + overload - Strong system design interview topic Let’s go deep 👇 The Core Problem Without limits, a single tenant can: Send 1M requests/sec → overload system → impact other tenants This causes: System outages Noisy neighbor problem Unfair resource usage Increased cost What Is Rate Limiting? Rate limiting restricts: How many requests a user/tenant can make in a given time window. Example: Free Plan → 100 requests/min Pro Plan → 1,000 requests/min Enterprise → 10,000 requests/min Types of Limits 1. Per User Limit User A → 100 req/min 2. Per Tenant Limit (Most Important in SaaS) Tenant Acme → 10,000 req/min 3. Per API Key / Token API key → limit enforced 4. Global Limit Protects entire system: Total system → 1M req/sec Where Rate Limiting Happens 1. Edge (API Gateway / CDN) - First line of defense - Fast rejection - Prevents backend overload 2. Application Layer - Business-aware limits - Plan-based logic 3. Service Level - Internal service protection - Circuit breaking Rate Limiting Algorithms 1. Fixed Window 100 requests per minute Resets every minute. ❌ Problem: burst at boundary 2. Sliding Window Tracks requests over rolling window. Better accuracy. 3. Token Bucket (Most Popular) Tokens added over time. Request consumes token. Bucket = 100 tokens Refill = 10/sec Allows bursts + smooth control. 4. Leaky Bucket Processes requests at constant rate. Prevents spikes. Real SaaS Flow Request: User → API Gateway → Rate Limit Check → Backend Steps: 1. Identify tenant 2. Fetch plan limits 3. Check usage counter 4. Allow or reject Example Tenant Acme (Pro plan): Limit = 1000 req/min Current = 998 Requests: - 999 → allowed - 1000 → allowed - 1001 → rejected ❌ Data Storage for Counters Common options: 1. Redis (Most Common) - Fast - Supports atomic counters - TTL support 2. In-Memory (Per Node) - Fast but not global - Needs sync 3. Distributed Systems - Kafka + aggregation - More complex setups Key Design Considerations 1. Tenant-Aware Limits Always include: tenant_id Avoid cross-tenant interference. 2. Plan-Based Limits Limits must come from entitlement system: Pro → 1000 req/min 3. Burst Handling Allow short spikes. Token bucket helps. 4. Graceful Degradation Instead of hard reject: - Queue requests - Return 429 with retry-after - Reduce response quality 5. Real-Time Feedback Return headers: X-RateLimit-Limit: 1000 X-RateLimit-Remaining: 12 X-RateLimit-Reset: 60s Common Mistakes - Hardcoding limits in code - Not using distributed counters - No tenant isolation - Ignoring retries - No monitoring Architect-Level Insight Rate limiting is not just protection. It is: A product feature + monetization control It enforces plan boundaries. Real-World Examples GitHub - API limits per token - Higher limits for paid users OpenAI - Token-per-minute limits - Tier-based rate control Stripe - Per-account request throttling Final Insight Good rate limiting achieves: Fairness Stability Monetization control It protects both system and business.

• 
  AI slop cleaner (@sehz_ai) reported 48 minutes ago

  @swapnakpanda Before AI: Curse when AWS or github is down After AI: Anthropic is down or hitting token usage

• 
  AK (@abhishek_ko) reported 50 minutes ago

  @signulll I think the better question is how is github copilot so terrible with access to literally all the code

• 
  AI Highlight (@AIHighlight) reported 57 minutes ago

  Stop wasting hours on server configuration just to launch a simple app. Hostinger now offers 1-click GitHub deployment for Node.js at a flat $3.99 monthly rate. It is the fastest way to turn your code into a live URL without the usual DevOps headaches.

• 
  Jay Ghiya (@BeLikeBumblebee) reported 1 hour ago

  @badlogicgames 1. does not have adequate information apologies. 2. Twitter is not an issue tracker usually. i never talk about it here usually but this got v annoying so yea :) so was recording a video tool and will attach the same in github.

• 
  Robin Ebers | AI Coach for Founders (@robinebers) reported 1 hour ago

  @FactoryAI @badlogicgames the real question is, why do you support BYOK but you don’t support login either ChatGPT or GitHub Copilot? that’d be a killer feature.

• 
  Growth Investor (@growthinvesto13) reported 1 hour ago

  @bstaples Why do you not hire people from cursor, Claude, codex and GitHub copilot to fix the issues you guys have with gitlab duo. You should have the customers feedback on why they are not choosing Gitlab as thier ai agent. Is is the cost that prevents you?