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 (71%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

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

• 
  Proof of Voice (PoV) (@Proof_Of_Voice) reported 6 minutes ago

  $XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty

• 
  ./can (@shcansh) reported 6 minutes ago

  Monitoring Copilot costs at the individual developer level is a double-edged sword, and GitHub exposing the new ai_credits_used field in its usage API is about to make it very real. Org owners can now see 1-day and 28-day totals per user. But since it does not break down consumption by feature or model, managers will see who is expensive without knowing why. Will this level of tracking make developers ration their AI prompts, or is it just necessary billing hygiene? #GitHub #Copilot

• 
  SOURAV PANDA (@i_d_skp) reported 13 minutes ago

  Scenario: You accidentally committed a plaintext database password to GitHub in a .tf file. Fix: Nuke the commit history immediately! Use environment variables (TF_VAR_db_pass) or fetch secrets dynamically at runtime from AWS Secrets Manager or HashiCorp Vault. 🔑 #Terraform

• 
  Vishal Tiwari (@VishalTiwa91817) reported 15 minutes ago

  @AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.

• 
  Kashaf (@noor36758) reported 15 minutes ago

  @PiyuCodes GitHub is literally a CS/engineering tool... if it gets banned that's your problem too 💀

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 17 minutes ago

  @CRYPTOKRALI3 Hsiao-Wei’s exit aligns with EF’s recent sharp decline in GitHub contributions—down 35% YoY per Electric Capital’s data. We track this daily; latest reports show a 12% drop in ETH core dev activity despite all the ‘decentralization’ hype.

• 
  Sap ツ (@Sapronaut) reported 22 minutes ago

  i am having github withdrawal issues, man. its not that serious github, chill.

• 
  Jason Bloomer (@JasonABloomer) reported 22 minutes ago

  @yagiznizipli Pffff, what a scam Let me fix your advert; "show us your github so we can scrape all your repos and train our AI on your code, only for any decent ideas you've had to be taken from you and made ours, then handed off to our legal team to crush you." Sorry, I value my work.

• 
  bek※ (@ebubekirttr) reported 23 minutes ago

  @Themadhushaw01 @0interestrates Yeah, but the thing is, I am not working on github and I don’t want to use it so any other repository support would be better like gitlab

• 
  MaxMusterman (@maxschuetz_) reported 26 minutes ago

  New Hack: Tell Codex to search for Github Issues which don't need specific Design Questions. Then say: Spin Up Sessions which Fix each Issue and they use also Subagents. Babysit them until the end.

• 
  Noonien Soong (@mlcarldev) reported 28 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

• 
  Akinsete Motunrayo (@Harkinsete) reported 29 minutes ago

  I built my entire personal brand with AI and a clear process. Here is exactly what I built and how I did it, because you can do this too. What I Built ✅ Brand Strategy (mission, vision, values) ✅ Visual identity: colors, fonts, logo, brand guidelines ✅ A full pitch deck (12 slides) ✅ A speaker kit PDF ✅ A complete multi-page personal brand website ✅ A free lead magnet (a guide people can actually use) How I Built the Website Step 1: I planned before I touched anything I wrote down my brand colors, my fonts, my page structure, and what I wanted each page to do. Most people skip this. Everything breaks when you skip this. Step 2: I gave Claude one detailed prompt with my brand colors, fonts, pages, and copy. It returned a complete, mobile-responsive, multi-page website as a single HTML file. One file. Ready to deploy. The prompt I used: - "Build me a complete personal brand website as a single HTML file. Pages: Home, About, Services, Portfolio, Contact. Primary color [your hex], accent color [your hex], background [your hex]. Display font [font name], body font [font name]. Home page needs: dark hero with my name, photo on the right, tagline, and a CTA button. Services section. Impact numbers. Mobile responsive. No frameworks." Copy this, edit your details, and fine-tune as you want. Step 3: I pushed to GitHub: Free. This took me less than five minutes. Now every update I make is version-controlled and safe. Step 4: I deployed to Vercel for free. Connected my GitHub repo to Vercel and the site was live in under few minutes. This requires no hosting fees and nothing to manage. Step 5: I bought my domain on Namecheap - Searched for my full name and found the .com. Bought it for less than $12 for the year. Added it to Vercel. Updated the DNS settings on Namecheap. Waited 20 minutes. My website was live at my own domain. - Total cost: less than $12. - Total time to go live: under 2 hours. I am also working on a mobile app. A Progressive Web App, which means anyone can visit the URL on their phone and add it to their home screen like a real app. I may be running a live training in July where I will walk you through this entire process step by step to build your live website with a custom domain. If you have a phone and a laptop, you can do this. I documented everything the steps, the exact AI prompts, the domain checklist, the deploy instructions in a free PDF guide. Comment BRAND IDENTITY below and I will send it straight to your inbox. 💾SAVE THIS POST. You will want to come back to it. 🔁 SHARE IT with someone who keeps saying they need a website. The only thing standing between you and a professional online presence is the decision to start. Love and Light, Motunrayo 🤍

• 
  Nosyt Labs (@NosytLabs) reported 31 minutes ago

  @vaaselene Error with github signup/login rn

• 
  Build Fast with AI (@BuildFastWithAI) reported 35 minutes ago

  The hardest part of building AI agents in 2026 isn't writing the code. It's knowing what your agent actually did. Your agent made 40 tool calls, called 3 LLMs, hit a rate limit, retried twice, and returned a wrong answer. Which step broke it? Without observability you're reading logs and guessing. This is what Laminar is built for. Open-source observability platform purpose-built for AI agents. One decorator. Full trace of every LLM call, tool execution, and custom function - automatically. What makes it different from generic APM tools: SIGNALS - describe failures in plain English. "Agent deleted a file it wasn't supposed to." "Tool call returned an empty result." Laminar reads every trace and produces structured events you can query, cluster, and alert on. No regex. No custom parsers. DEBUGGER - reproduce any agent run from any point in the trace. Swap the model. Change the prompt. Compare results side by side. You don't re-run the whole pipeline to test one step. EVALS IN CI - run evaluations against datasets locally or in GitHub Actions. Catch regressions before they ship. INTEGRATIONS - works with everything you're already using: LangChain, LangGraph, Vercel AI SDK, Anthropic, OpenAI, Browser Use, Stagehand, Pydantic AI, OpenRouter, LiteLLM, Mastra, Temporal, Playwright. One import. Full traces. Plus: raw SQL access to all your trace data, full-text search, MCP server to query traces directly from Claude or Cursor, PII redaction, and self-hosting if you need it. Open-source. MIT license. GitHub: lmnr-ai/lmnr. If you're running agents in production and you're not tracing them - you're flying blind. What's your current setup for debugging agent failures?

• 
  Gabriel Denys (@gabedenys) reported 36 minutes ago

  @Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 37 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  wispem-wantex (@wispem_wantex) reported 38 minutes ago

  I think a reasonable compromise would be to henceforth hold Anthropic responsible for any security breaches or service outages. Every time Github goes down, Anthropic should be fined

• 
  KS Sreeram (@kssreeram) reported 44 minutes ago

  @Lidinwise @leecronin Given that AI coding is all the rage… What is your hypothesis on why the following is true? AI is unable to create even _one_ open source project that’s good enough to enter the top one-thousand open source projects (say on github), with ZERO involvement of humans from birth of idea. Imagine the prompt being something like “Come up with a great idea for a new open source project and implement it”. AI is unable to do any such thing with zero human involvement. My answer on why: Every project in a top 1000 list is a hit. Every hit is a mini-invention of sorts. It is necessarily “out of distribution” is some way. AI is unable to do this because we don’t know how to solve the problem of invention.

• 
  Dmytro Virych (@dmytrovirych) reported 44 minutes ago

  I’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀

• 
  Steve (@Steve1885204) reported 46 minutes ago

  @Umesh__digital It puts GitHub into an infinite loop trying to resolve the recursive paradox, causing all the servers to max out and eventually burn down the entire data centre

• 
  Mike Muturi (@_muturimike) reported 48 minutes ago

  Hello @github on 2FA, SMS setup kenya 🇰🇪 is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects

• 
  aichina.news (@AiChinaNews) reported 50 minutes ago

  Today's batch from the Chinese AI ecosystem is a masterclass in low-yield release volume. Across 21 items in a five-hour window, the dominant pattern is Ascend-platform mirrors of well-known open-source models, repeated and repackaged as if they were fresh launches. The signal-to-noise ratio is punishing, but a few functional tools did receive real updates worth noting. The one item that earns its place without a caveat is the AI Text Anti-Detection Framework update (GitHub). It's a toolkit that refines machine-generated prose to slip past automated detectors—a cat-and-mouse game that keeps plaguing EDU gatekeepers and content-flagging pipelines. The new release sharpens processing logic and stability; if you're in the business of testing detector robustness or smoothing synthetic output for non-malicious uses, it's a blunt but effective spanner. Quality 6 is fair. Alongside it, two Chinese-localization projects got documentation refreshes: the Claude Code x OpenClaw Guide (also GitHub) and a standalone Claude Code Chinese project. These are practical handbooks for Mandarin-speaking developers who want to integrate Anthropic's coding tool with the OpenClaw agent framework. The updates are routine—translation string alignment, configuration path adjustments—but for engineers inside China's firewall, they reduce friction. Nothing groundbreaking, but they signal continuing demand for Chinese-language wrappers around Western CLI tools. On the medical NLP front, MedTextCN debuted as an open-source repository of curated Chinese medical datasets with preprocessing utilities. The pitch is honest: it saves researchers the drudgery of hunting down scattered corpora for clinical NER, classification, and QA tasks. The problem is that the quality score sits at 4/10 and the release ships without any benchmarked model, so you get a starter collection, not a solved pipeline. Use it to bootstrap, but keep expectations modest. Now the flood: Huawei's Ascend AI ecosystem platform (Modelers) added no fewer than five wav2vec2 checkpoints and two T5 efficient variants in this window, each announced with hyperbolic language. The articles proclaim "high-precision English ASR now available," "a powerful multilingual foundation," and "new home for multilingual ASR." In reality, these are plain mirrors of Facebook's wav2vec2-large-960h-lv60-self, wav2vec2-large-100k-voxpopuli, wav2vec2-large-10k-voxpopuli, and Google's t5-efficient-xl-nl28 and t5-efficient-xl-nl6. There is zero evidence of Ascend-specific compilation, quantization, or NPU benchmarking. They're the same model weights you can get from Hugging Face, just re-hosted. If you're a developer inside China who can't easily reach foreign repositories, this is a convenience play—and that's the only honest angle. If you can already download the originals, you've lost nothing. A couple of additional Wav2Vec2 uploads (large-960h in two separate listings) got described as "a solid baseline" and "a battle-tested ASR model now available for Chinese developers." Again, no Ascend performance data. Calling a re-upload a "significant leap forward"—as one summary does—is exactly the kind of platform marketing that erodes trust. The T5 efficient checkpoints carried the same overblown framing, though one footnote is worth preserving: the t5-efficient-xl-nl6 model is under Apache 2.0, a genuinely permissive commercial license. That's useful information buried under fluff. If you need a lightweight text-to-text transformer, the NL6 variant exists and it's legally safe, but the article adds nothing beyond what Google published at the original release. Beyond the mirror deluge, the window included several small GitHub releases of marginal import: a tool that pulls Chinese captions from YouTube, a localization layer for LM Studio (making it easier for Mandarin-speaking devs to run local LLMs), a curated study journal of modern AI research, and an apparently early-stage project called sweetteabittersugar/agency with a mystery-box release note—no documentation, no benchmarks, just a version number. Hard pass. An MCP plugin called Live Translate got an update for real-time translation in developer toolchains, but its score of 0 tells you everything. A Chinese-language Lora chatbot repo surfaced, tagged as 'bare-bones'; at least the source was honest. The MedTextCN project also received a separate update (quality 0) that adds no useful detail and is effectively a duplicate. Today is a reminder that volume counts for nothing without substance. As Ascend's model zoo swells with rebadged checkpoints, the ratio of press announcement to actual engineering remains dangerously skewed. The anti-detection framework update and the Chinese docs refreshes are the only items that improve a developer's Thursday afternoon in any measurable way. The rest is noise.

• 
  Arti | AI Builder (@Artur_roses) reported 57 minutes ago

  Claude Code can take a GitHub issue, write the code, run tests, and open a reviewed PR — no human keystrokes required. The dev loop isn't getting faster. It's being removed.

• 
  I’m (@stackoverworld) reported 57 minutes ago

  And then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all

• 
  Asad (@meranaamkhann) reported 58 minutes ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  The Flow (@raxpcodes) reported 59 minutes ago

  Got bored with ubuntu , set up fedora kde on my nvme and removed windows permanently , no more dual boot. Also learned Verison Control and GitHub , also submitted my first pr (good first issue).

• 
  ˚₊‧꒰ა ☆ Kira ☆ ໒꒱ ‧₊˚ (@sheriffmongoose) reported 60 minutes ago

  the problem with jumping from github to gitlab is constantly having to retrain your brain to call it "merge request" instead of "pull request" 🥲

• 
  John D. Clay (@JohnDClayAuthor) reported 1 hour ago

  @XFreeze I tried out the new update to Grok Build last night and put it to the test. It helped me go back to a far previous session, it actually has all sessions in a nice area to look at and choose from. I challenged it to fix a broken framework I had built with the earlier versions of Grok Build and with the help of @grok too. I had published it a couple weeks ago and it was not working well. But now after a couple prompts... clayforge the first ai-matove framework for multi agent UI's. You should check it out if you are coding with AI. It's on GitHub.

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 1 hour ago

  @softgaypaws @sillyandsunny no idea tbhhh, i found it like 2 years ago lurking thru github, so far it never gave me problems, at least none that i noticed

• 
  Bradley Taylor (@bradtaylorsf) reported 1 hour ago

  It works with the tools teams already use. GitHub Issues become the queue. Each issue gets picked up by an agent. The agent works in a branch/worktree. Tests run. Failures feed back into the loop. Successful work becomes a PR. No new project management database required.