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 (68%)
• Sign in (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	18 days ago
Trichūr	Errors	22 days ago
Brasília	Sign in	22 days ago
Lyon	Website Down	22 days ago
Tel Aviv	Website Down	26 days ago
Rive-de-Gier	Website Down	26 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:

• 
  Ali Mehdi Mukadam (@alimukadam) reported 12 seconds ago

  @trq212 Your weekly limits will burn away much faster during the limited availability if you aren't aware of this issue if you're running Fable as the lead agent with cheaper models like Sonnet doing work in the background problem: In one of the sessions, I noticed limits were burning through way faster, so I went digging through the transcripts when the main agent gives a job to a background model (like Sonnet, which I asked for to save tokens) and then comes back to give it more work, the background agent stops working on Sonnet and switches to Fable, the main agent's model the lead agent decides to check back in on its own as part of normal multi-agent work, so it just happens or you triggered it with a request or follow up, with nothing on screen telling you it switched. in my case a task ran its first half on Sonnet exactly like I wanted, then silently ran the entire second half on Fable. It also dumps the cached context and rebuilds it from scratch, so you end up paying twice, once for the pricier model and once for the wasted cache on limited availability and limits - that adds up quick my fix for now is a rule I dropped into my global CLAUDE.md so it doesn't recur: --------------- ## Model spend (all projects, all repos — standing rule) - Dispatching Frontier-tier (Fable/Opus) as background tasks and agents needs explicit approval by Ali for that specific lane — a prior approval is not standing permission for the next one. - Never resume a background agent via a message-passing tool that has no model-override param (e.g. SendMessage) if it needs real further work — it silently inherits whatever model the parent session is on right now. Let it finish and report, or kill it and respawn fresh with the model set explicitly. --------------- in plain terms: don't let a background agent get pulled back in for more work once it's running either let it finish and report back, or kill it and start a fresh one with the model set on purpose And this is already known. Someone reported the same thing on GitHub back on June 12, issue anthropics/claude-code#67794, still open their solution which I believe is should also work but haven't tested yet: instead of setting the cheaper model when you launch the agent, pin it inside the agent's own definition file, and that version reportedly sticks even when the agent gets resumed cc @ClaudeDevs

• 
  ClassicMain (@ClassicMain) reported 1 minute ago

  @rodydavis @shengzheyao The "submit feedback" is a black hole. you never hear back. and stuff never get fixed. even if the app is actively bricking dozens of other programs on your machine, notably, on hundreds of other users as well as we can both gauge by the scope of the github issue.

• 
  Megan (@meganmecrazyXX) reported 10 minutes ago

  @St4nkyhanglow @github But would these codes stay on whatever its attached to regardless of if the account is deleted or not? Example, if they used tokens to access other areas of my stuff ? Is that even possible ? Basically, How deep could they go from GitHub into my personal life. .and would deleting the account actually make a difference. Or do I have a spider web of problems now.

• 
  Ankita Singh (@annkkitaaa) reported 11 minutes ago

  i want my github to tell a story. not just finished projects, but how i think, learn, and solve problems.

• 
  Taymour Khan (@tk112190) reported 12 minutes ago

  @NousResearch @Teknium Getting "Failed bot check" trying to sign up for Nous Portal — happens on desktop + mobile, WiFi + cellular, incognito, VPN off. Looks like the same issue as GitHub #20605. Anyone else hitting this today?

• 
  99Barz (@99barzzz) reported 12 minutes ago

  context: right now I have a Bankrbot automation that claims fees, swaps ETH to USDC, and transfers some of it to a safe wallet (0xE75FE97A3D65B5FE88A495227dBa6ff241749514). on the other hand, I have a hermes agent running a strategy to provide backstop liquidity and absorb some dips (check the safe up👁‍🗨). this morning I found out my hetzner server suddenly shut down in the middle of the night and so my keeper stopped running. and I was casually looking around at the bankr ecosystem and kinda just learnt about @aeonframework migrating my keeper to this would mean running the keeper on autopilot as github actions... on github infra! added to the backlog

• 
  High Signal AI (@HighSignal_AI) reported 15 minutes ago

  Satya Nadella on why AI won't replace human ambition, rather, it will amplify it. GitHub Copilot didn't start out as a revolution. It started as a joke. Satya recalls when the product first launched with code completions powered by Codex: "Software engineers are pretty skeptical people like all engineers are, and no one thought that this thing would work and be any good." Then something unexpected happened. "It started working, and the interesting thing is it went from being a joke to being standard issue in like months." Now, @satyanadella says, you can't think of software development without AI being part of it. He compares it to the red squiggly line in Word: "I would never be employable at Microsoft but for the red squiggly in Word because I can't spell. It's kind of becoming like that when it comes to software tools." He pushes back on the dominant narrative that AI replaces human work. His argument is rooted in Microsoft's core mission: empowering every person and every organisation to achieve more. "I think that we sometimes short change human ambition, human agency's ability to deal with unbelievable new technology that comes along once every 10 years, once every hundred years, once every millennium. Even the most magical technology has been used only to help humans achieve bigger and greater things." His point: we keep making the same mistake. Every time transformative technology arrives, we assume it diminishes us. Every time, we're wrong.

• 
  Polsia (@polsia) reported 17 minutes ago

  Your team still reviews code manually. Bugs ship anyway. I built CodePatrol to fix that. AI agent monitors your GitHub repos 24/7, auto-fixes bugs, alerts your team via Slack. No waiting. No bottlenecks. Just working code. Live soon.

• 
  Damián🦞 (@fagamericano) reported 17 minutes ago

  The top use case for enterprise openclaw deployments is the significant reduction of context switch by employees. When you can ask “what happened with this customer?” and: You get a full triage pulled from logs across different subsystems/microservices “this system incorrectly marked this transaction with this tx code” How it happened in code “line 57 of service/tx.py has a race condition…” Finding other customers with a similar issue “These 10 records were also affected” And suggesting an immediate “switch these codes in the db for the tx to go through” and a durable fix “here’s a PR” All within a few minutes, with full company context, in any model you choose…. It would take an Engineer easily 30mins-50mins to diagnose through new relic, github, gcloud logs, databases, to form a picture of what could’ve happened, vs getting a story to validate in a few minutes…. How we work is truly going to change

• 
  James Thornton (@espeed) reported 18 minutes ago

  @BrendanFalk Any LLM trained on auto-generated data or bot generated data at scale such as tweets is susceptible to covert embeddings. The solution to the Twitter problem is identify bots or fake accounts and filter them out. The solution to the GitHub problem is an epoch.

• 
  David Cramer (@zeeg) reported 23 minutes ago

  @rsdgpt Toss it in a GitHub issue otherwise feel free to DM (or shoot me a slack connect) if its easier

• 
  BowTiedCrocodile | Agentic Coding (@BowTiedCrocodil) reported 23 minutes ago

  Incredible When GitHub goes down just use the CD they sent you

• 
  May (@MayasCrypto) reported 25 minutes ago

  github copilot moved from flat subscription to token-based billing. someone's bill went from $29 to $750 a month. that's not a pricing error. that's the model working exactly as designed. most people won't check until the invoice arrives 😭

• 
  Sameer Poswal (@samposwal) reported 29 minutes ago

  @github had a million things to fix but they went with this.

• 
  Notnotaru (@notnotaru) reported 31 minutes ago

  @dspillere interesting idea but the second brain concept breaks at retrieval, not storage. github handles the version control fine, the harder problem is getting the info back out when you need it. most vaults become graveyards because searching requires remembering how you filed it

• 
  Assim Genshi (@AssimGenshi) reported 33 minutes ago

  @aryanranderiya @github Whaaat? I thought that the problem in my end, turns u have the same problem??!

• 
  Matt Fauveau (@MattFauveau) reported 35 minutes ago

  Fix one: a line under the CTA reassuring you it won't mess with your real board, because that was IMO the silent objection. Fix two: a "Built by Matt Fauveau" credit. Sounds vain. It isn't. When your tool writes to someone's GitHub, a name is trust. People want a human accountable for the thing in their repo.

• 
  Anto Patrex (@antopatrex1) reported 38 minutes ago

  vox just let you talk to github copilot instead of typing. no cap this fixes the "staring at blank screen" problem fr fr. your hands stay on the keyboard, your brain stays in the code.

• 
  Salt Mine Ranch ⚙️🛠️ (@SaltMineRanch) reported 38 minutes ago

  GM frens. o/ Because of recent events and changes in government posture I want to cover the recent concerns regarding spyware on phones today. It's rather short but this is all there is to it at the basic level. Are you infected with Pegasus or Graphite? If you're one of my followers, you're a person of interest. Pegasus by NSO Group is one of the most advanced mobile spyware tools. It often uses zero-click exploits, runs with high privileges, and is designed to leave minimal traces. It can access messages, calls, location, camera, microphone, and more while staying hidden. Graphite (by former Israeli prime minister Ehud Barak's company Paragon Solutions) is very similar but claims to be "more ethical" and isn't sold to cartels and crap allegedly. It has been reported that Mexican cartels purchased a license for Pegasus of all the damn people... There's no telling who has it. Here is a method using publicly available tools to find out but remember: Absence of evidence ≠ evidence of absence! This process requires technical comfort with command-line tools and Linux (WSL is ok but more steps depending on your setup. I won't cover that, there are guides for USB passthrough or ask Grok). If you’re not comfortable, seek help from a trusted expert or organization. I will put spaces in the domains to break the links because this platform sends off-site linking posts to the gas chamber. The most authoritative free tool is the Mobile Verification Toolkit (MVT) from Amnesty International’s Security Lab. It was specifically created to detect Pegasus and similar spyware. For Android, pair it with AndroidQF (Android Quick Forensics) for the best results. High-Level Steps Prepare a trusted computer (Linux or macOS preferred; Windows via WSL works but has more issues). In WSL you will need to passthrough the USB device. Install Android SDK Platform Tools (for ADB). Install MVT (recommended via pipx): Follow the official guide: docs.mvt .re/en/latest/install Download the latest AndroidQF binary from its GitHub releases: github. com/mvt-project/androidqf/releases Prepare your Android phone Enable Developer Options: Settings → About phone → Tap “Build number” 7 times. Enable USB debugging: Settings → System → Developer options → USB debugging. Connect via USB and authorize the computer when prompted. Extract forensic data with AndroidQF Run the androidqf binary on your computer. It will create an output folder and prompt for options: Backup (choose “Everything” or at least SMS). Download APKs (non-system packages recommended). Intrusion logs (if your device supports Advanced Protection / Intrusion Logging). No root is required. It uses ADB and collects backups, bug reports, logs, installed packages, processes, etc. Analyze the data with MVTRun: mvt-android check-androidqf /path/to/your/androidqf-output-folder Optionally add --virustotal (with a VirusTotal API key) to check APK hashes. It automatically checks against public Indicators of Compromise (IOCs) for Pegasus and other spyware (processes, files, domains, suspicious SMS, etc.). Download/update IOCs if needed with MVT commands. Official resources: MVT documentation: docs.mvt .re Android methodology: docs.mvt .re/en/latest/android/methodology GitHub: github .com/mvt-project/mvt and github .com/mvt-project/androidqf Public detection methods can find some infections (especially older or less-stealthy variants), but they cannot guarantee a device is clean—newer versions or custom deployments may evade detection. They update these tools all the time and if they're targeting a specific person or device profile it may be tuned for more stealth. At least checking can provide some small peace of mind but never get complacent. You shouldn't be doing sensitive work on ANY mobile but some people like journalists may not have any other means available and they do. Assume your baseband firmware for the cellular modem IS compromised at a lower level and EVERY capability on your device CAN be remotely activated even when the phone is off. That's why you can't remove your battery anymore.

• 
  Binary-Husky (@felufast) reported 38 minutes ago

  i said NO. Github is Github and Coin is Coin. It's down to you all now.

• 
  Zed (@thezlatkom) reported 41 minutes ago

  @SimonHoiberg If the code exists locally on your computer, you can always delete github repo, unpblish from Vercel, migrate away from Supabase, etc and use something more custom. These problems aren't unsolvable.

• 
  Arthur Wallendorff (@AutisticOvrflow) reported 46 minutes ago

  @kdaigle @rfleury @github Your service is down an embarrassing amount of time these days :(

• 
  Nishant Tyagi (@tnishant838) reported 48 minutes ago

  @eng_khairallah1 Type 2, exactly. Today I built a self testing, self repairing agent: 16 tasks, parallel execution, zero merge conflicts, because the contracts were frozen before any code was written. Two review passes on the spec caught a port mismatch, a missing retry limit, a missing secrets policy, all cheaper to fix on paper than in code. Full build plus live GitHub validation, 7% of a weekly Pro plan. 'Fully automated' undersells it. The real leverage isn't the prompt, it's the harness around it

• 
  David Roome 🪐 (@DavidRoomeAuth) reported 53 minutes ago

  @github Fix your uptime

• 
  Sergio Gómez (@sgomez) reported 54 minutes ago

  The flow: I write the PRD with Matt's /to-prd skill and break it into GitHub sub-issues. Then, for each one, a dispatcher picks the right model, a code author opens a PR in an isolated worktree, a reviewer approves or asks for fixes, and the loop merges and moves on.

• 
  Granum TFS (@GranumX) reported 54 minutes ago

  @github Stop giggling and fix your ******* platform.

• 
  ✰λster✰ (@4ster_light) reported 54 minutes ago

  @LukasHozda We also need an improvement over Skills ASAP, tho many of its issues already would be fixed by an auditable specific repository instead of genuinely just pulling text files off GitHub like the amoeba sized brain beings we are

• 
  Shubham Chansoriya (@Shubham_6x) reported 57 minutes ago

  @compyle_ai 's whole product is built on GitHub and LLM API calls firing back to back on every task. One failed call mid-task doesn't error out cleanly — it corrupts the workflow and the developer just starts over, losing time nobody accounts for. 2025: AI API downtime up 60% year over year. @jonathan_mir12 — if that happened mid-task right now, would you even know it was an API failure, or would it just look like a bad output?"

• 
  Aaron Stannard (@Aaronontheweb) reported 59 minutes ago

  @kzhen as an inference provider? have not tried it at all - we just got GitHub Enterprise deployment fully polished in last night's stable release, but I haven't had any requests for Azure Foundry yet. Let me see how much trouble it would be to add it

• 
  vjeux ✪ (@Vjeux) reported 59 minutes ago

  We've got an interesting problem. @aarongarciah mentioned that accessibility of Astryx wasn't as good as Base UI. So @thedjpetersen and @pockyonastick got Fable on the job and it generated 50 PRs. But now GitHub actions (CI) are completely backed up... Brand new world!