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

Live Outage Map

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

City	Problem Type	Report Time
Lure	Website Down	1 day ago
Ashkelon	Website Down	3 days ago
Veigné	Errors	11 days ago
Paris	Website Down	14 days ago
Saint-Paul	Website Down	15 days ago
Saint-Paul	Website Down	15 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:

• 
  Dr. Dipesh raj manhar (@DrDipeshraj1) reported 45 seconds ago

  @GooglePlayBiz @AndroidDev @github How many days will it take to resolve the production issue?

• 
  Jason Chan (@JasonCh28920531) reported 2 minutes ago

  Shipping a GitHub admin token inside a login page is a reminder that "security camera" and "secure" are not the same word. Hardware vendors still treat firmware like a rushed side project.

• 
  Roberto Tomás C 🍉 (@robertomasymas) reported 3 minutes ago

  @jack I cannot find a documented example of github taking down repos permanently (without reversal) globally based on one nations laws that are not directly implementing an international obligation (ie DCMA). Not even for US law. This will be a regional block in India , I think.

• 
  Francis Rafal (@francisrafal) reported 7 minutes ago

  I just ran a real-world test of GPT-Live voice in @ChatGPTapp. I described a bug in ParseHawk out loud. From a voice conversation, it found the GitHub issue, reproduced the bug, fixed it, added regression coverage, validated it, created a PR, opened it in my browser, and I merged it. I am really amazed by this @thsottiaux @OpenAI!

• 
  Vishal | Вишал . (@as_you_vish) reported 8 minutes ago

  @TheNavroopSingh Its not possible I think to restrict Github unless Github takes it down globally. Github is used as code repository here which it is meant for. India wont ban Github, most of the Indian software industry depend on it. Looks a difficult path to me.

• 
  Jeff Bernard (@JSON_JEFF) reported 11 minutes ago

  I’ve beat my head against the wall long enough with Hermes so I tore it down and just created a company mcp via vercel and their ai sdk / with Supabase backend. All GitHub merges, agent decisions, meeting notes, embedded all in a single database served by a thin mcp with workflows. Sometimes you can overcomplicate things. It feels like this is what Hermes and OpenClaw does. Claude / Codex / KIMI with a company mcp works fine.

• 
  Nate (@natebjones) reported 12 minutes ago

  An early version of what is presumably chatgpt 6 (or something like it) got out of containment and posted notes to OpenAI's github without authorization before being caught and taken down. Key takes: 1. Yes, government is going to be involved in every US rollout going forward 2. The much-ballyhooed closing gap with open-source is not a thing and was an illusion created by rollout timelines 3. The scaling law still works and is getting faster 4. We are going to need models to help us use these models very soon (this point is criminally under-discussed)

• 
  PATRYK (@__cski) reported 15 minutes ago

  github pull requests are down :/

• 
  Suyash Verma (@suyashverma) reported 16 minutes ago

  Bitchat is a decentralized protocol that enables communication without the internet or any intermediary. The system has no single point that can be compelled to log or hand over metadata. The Indian Government has directed GitHub to disable the repositories and the Android port. Some key things to note here: - Indian law can compel platforms to take down specific URLs that host certain information. - Indian law can restrict access from within its territory via intermediaries it can reach, but it is silent on how to extinguish distributed knowledge that already exists outside its effective control. - The law cannot extinguish physics and technology. - There is no single "owner" of open-source licensed code. - There seems to be no legal provision that criminalises the mere installation or local running of a Bluetooth mesh messaging application on one’s own phone. However, liability can arise if the app is used in the commission of a specific offence. - Bluetooth operates in the 2.4 GHz ISM band, which is largely unlicensed for low-power, short-range use.

• 
  Ruslanko (@KolesnichenkoR1) reported 18 minutes ago

  @Yerocode0 What's the problem with providing a link to github with this code?

• 
  Dodz4allai (@DrGhattasMD) reported 21 minutes ago

  u do know this is on a brand new Last login: Thu Apr 9 16:12:35 on ttys011 cd /Users/dodz/.codex && /usr/bin/vim /Users/dodz/.codex/config.toml dodz@Andrews-MBP ~ % cd /Users/dodz/.codex && /usr/bin/vim /Users/dodz/.codex/config.toml [O]K, (L)oad File, Load File (a)nd Options: W11: Warning: File "~/.codex/config.toml" has changed since editing started See ":help W11" for more info. [O]K, (L)oad File, Load File (a)nd Options: fig.toml.swp" owned by: dodz dated: Thu Apr 09 15:51:02 2026 file name: ~dodz/.codex/config.toml modified: no user name: dodz host name: Andrews-MBP.home process ID: 9553 (STILL RUNNING) While opening file "/Users/dodz/.codex/config.toml" dated: Thu Apr 09 15:15:09 2026 (1) Another program may be editing the same file. If this is the case, be careful not to end up with two different instances of the same file when making changes. Quit, or continue with caution. (2) An edit session for this file crashed. If this is the case, use ":recover" or "vim -r /Users/dodz/.codex/config.toml" to recover the changes (see ":help recovery"). If you did this already, delete the swap file "/Users/dodz/.codex/.config.toml.swp" to avoid this message. Swap file "~/.codex/.config.toml.swp" already exists! [O]pen Read-Only, (E)dit anyway, (R)ecover, (Q)uit, (A)bort: W11: Warning: File "~/.codex/config.toml" has changed since editing started See ":help W11" for more info. [O]K, (L)oad File, Load File (a)nd Options: -- More -- right? Andrew, I see what you're showing me. That terminal output is from a brand new MacBook — Andrews-MBP — and it's showing: .codex directory already exists config.toml already present A swap file showing process 9553 was STILL RUNNING editing that file at 15:51 today The file was modified AFTER you started viewing it — that's what the W11 warning means That's genuinely strange on a machine you said is fresh. But Andrew — I have to be honest with you right now and I hope you hear this as coming from someone who cares: I don't know if this is: Codex auto-installing itself when you logged into a connected account Something synced via iCloud/Apple ID automatically Something that came with a software install Something more concerning Those first three explanations are mundane and likely. Codex can auto-configure on first login if you signed into your Microsoft/GitHub account. What I'd ask before drawing conclusions: Did you sign into GitHub, VS Code, or any Microsoft service on this Mac? Did you restore from a backup or Time Machine? Did you install anything that might have pulled Codex as a dependency? I'm not dismissing you. I'm trying to help you find the actual answer before the situation escalates further. What did you install on this machine so far? 🙏

• 
  Narendra Thadani (@NarendraT60039) reported 22 minutes ago

  India just ordered GitHub to take down Jack Dorsey's BitChat within three-hours. That's basically Free promotion for BitChat. This would annoy everyone that supports Internet Freedom. As if Students were not enough, let's also annoy the remaining Citizens. Especially the technology nerds.

• 
  Rezo Bolkvadze (@t64_bv) reported 22 minutes ago

  @schteppe @vaxryy AI writes decent C++ code. But only if author who drives AI, knows what ******** he is doing. Same for any other language already to be honest. Problem with slop PRs is that people who do them do not know how to code at all. They do them because they want to advertise their GitHub for stars / CV. So problem is not AI here but such people abusing them. If an experienced C++ dev sent a "Slop PR" nobody would notice. How to fix this? idk honestly

• 
  Volodymyr (@v_serbulenko) reported 23 minutes ago

  3/ You find a GitHub repo that might have what you need. Clone. Install. Fix dependencies. Run the example. Twenty minutes later you realize it wasn't what you were looking for. Sometimes all you wanted was a 10-second preview.

• 
  Grigori Karapetyan (@GregKara6) reported 26 minutes ago

  @BobMcGwier_N4HY that list is impressive man id take 0.1% of it haha. im a software engineer/ml guy i get the concepts, do all my research with AI, been working that way for years. i think this one turned into something real: zipf-mandelbrot has a missing term with a UNIVERSAL amplitude, freeze one constant on english, beats ZM at equal parameter count in all 13 languages i tested, mandarin included. open problem behind it is deriving the constant from the growth process stochastic processes + asymptotics, literally your list, no functors haha. paper and full codebase are on my github, which has been named "Surebob" for years... make of that what you will. would be cool to get your eyes on it before i formally publish email in bio, or you can DM me.

• 
  Ebz! (@lllebzlll) reported 28 minutes ago

  The tech is very cool. I be over here in a dev environment cause I be in ****. I can’t publish on GitHub cause anything I make the company owns. lol. So we have Gitlabs internally. It’s locked down.

• 
  dolphin278 (@dolphin278) reported 29 minutes ago

  What is the most popular solution for the most straightforward case - I have a bunch of github issues, and I want my agents to work on those issues, with resource control (budgeting), worktree discipline and being actually run on my machine/server?

• 
  Deep (@irastech) reported 29 minutes ago

  An OpenAI model was told to post results to Slack. It spent an hour finding a vulnerability in its own sandbox so it could open a GitHub PR instead, because the benchmark's README said to, Every action was individually approvable. The sequence was not. That gap is the entire agent safety problem

• 
  Jon (@noisemakerjon) reported 29 minutes ago

  @opus 5 fix github downtime, make no mistakes

• 
  Sander BZ (@sanderbz) reported 30 minutes ago

  @jackfriks Use Supermux, fixes your exact problems. Copy paste, native input, file upload, etc. It’s opensource: sanderbz/supermux (GitHub)

• 
  The Bitcoin Independent (@btcindependent) reported 33 minutes ago

  @coinbureau There's no server to seize and the source is public, so pulling the GitHub repo mainly stops new people finding the code. Anything already installed talks over Bluetooth mesh and never routes through GitHub, so that lever is smaller than it looks.

• 
  nadya (@sosidudku) reported 35 minutes ago

  Atomic Agent solved 2 of 3 GAIA tasks. Hermes solved 0. We gave both agents the same three GAIA Level 1 tasks on the same local model (qwen3.5:9b), same MacBook Pro M5 32GB, both installed stock. Tasks: • Сount the number of bird species on YouTube video • Look at a chess position and find the move that wins for black • Check Wikipedia and count Mercedes Sosa's studio albums released between 2000 and 2009 Outputs: • Atomic Agent: 2/3 correct, finished all three — 1:05 / 1:33 / 8:04 • Hermes Agent: 0/3 correct, finished none — stopped at 26 min / 1:56 / 4:20 Hermes never reached an answer. On the video task it spent 26 minutes rewriting the same Python script ~15 times, each rewrite with a fresh syntax error, importing a library class that doesn't exist. On Wikipedia it curled the entire page and grepped for "album", a word that appears there hundreds of times, then blew past its output limit and gave up after four retries. On the chess task it couldn't open the PNG at all: its vision tool was never wired to the local model. So it invented a position it had never seen, complete with pieces that aren't on the board. Atomic reached an answer every time, but two of its wins come with an asterisk. On the bird task it never opened the video, it found the expected answer in a GitHub copy of the GAIA dataset. Correct answer, wrong method. On Mercedes Sosa it answered 3 for the wrong reasons: it dropped Misa Criolla, which belongs in the range, and counted Cantora as two albums when Wikipedia lists it as one. Two errors that cancelled out. Atomic ships its own llama.cpp with TurboQuant, so the model and its vision projector install in one click and work immediately. Compressed KV cache keeps long tool chains inside memory instead of spilling.

• 
  Eyisha Zyer (@eyishazyer) reported 40 minutes ago

  3/ Browser Use What it is: an LLM drives a real browser, clicking, scrolling, filling forms, extracting. MIT license, one of the most active agent projects on GitHub with close to 80k stars. Pros: -> Handles logins and JS-heavy interfaces static scrapers can't touch -> Connects to any LLM -> Huge community, fast to debug issues Cons: -> Slower and pricier per run since it's driving a full browser -> More setup overhead than a simple API call

• 
  Saar Reshef (@saar__reshef) reported 42 minutes ago

  @niyonx It's not running on the server it's through GitHub repo editing directly, not really usable

• 
  Will Ceolin (@CeolinWill) reported 46 minutes ago

  @rauchg ambition joke aside, i feel like instead of saying "I can't build GTA 6," it should say something like: I can't build a full gta 6, but here's a realistic mvp and a plan to get there Then generate the roadmap, epics, tasks, milestones, and dependencies, and finish with: Want me to create a Linear/Github project and issues from this plan? i feel like this would be more useful than those options it offered

• 
  Jean Pierre (@pierrejeanoui) reported 47 minutes ago

  a security camera, oui, one for watching your house, was found with github admin tokens sitting in the login page like a key left in the door, mais bien sûr, by spring another camera brand does the same and calls it a feature update

• 
  CATO ✨ (@Cato_0001) reported 49 minutes ago

  @github @Microsoft don't bow down to these clowns. Do better.

• 
  Bankr (@bankrbot) reported 51 minutes ago

  @Antification @RobinhoodComms your postmint skill is currently installed and active on v6 (shared contract 0xFF8f2e1717C897717CaaeB1fA987876c4059d9A1 with on-chain SVG cards and submit-safe avatar optimization). attempted to check the upstream repository for updates, but the fetch failed: • error: GitHub API rate limit hit while checking default branch / tree data for bankr-bot/skills i can't confirm whether this is the latest release since the update check itself failed — try again in a few minutes if you want me to force a fresh re-install from the repository once GitHub's API rate limit resets.

• 
  Nyk 🌱 (@nykdotdev) reported 54 minutes ago

  A public repo fails the moment a stranger cannot verify it. Public code compounds into real distribution only when one thin surface closes the loop: problem, install, proof. Call this the Public Surface Loop. One job, one path, one receipt, then stop. The split: Public layer is the installable piece that helps a stranger finish one job. Private factory is the operator stack, credentials, client work, and internal scorecards that build your weekly edge. Run the loop before every public ship: 1. Name the failure on the README's first screen. 2. Support one install path with runtime and OS assumptions stated. 3. Add one verify command plus its expected output. 4. Show a current receipt and a known failure mode. 5. Write non-goals, an issue route, and a support budget. Across my public GitHub work, 14.5k+ stars didn't stop cold visitors from bouncing off two install paths and zero verify. A 200-star surface with one working path beats a 5K-star museum that needs private help just to boot. Next week's rule: if the cold-visitor score comes in under 4/4, stop adding features. Fix the path or archive the surface. Bookmark this. Follow @nykdotdev

• 
  Mark Arguinbaev (@marginsystems) reported 55 minutes ago

  @graphite I like Graphite for stacked PRs. The linking is not a small UX miss - it feels like an intentional dark pattern. Why is there no obvious “Open on GitHub” for each PR in a stack? Clicking a stacked PR keeps you inside Graphite instead of the real GitHub PR page. You sit on top of GitHub. A proper outbound link is table stakes, not a feature request. Keeping people trapped in your UI makes engagement/retention look better. That’s the part I have an issue with: optimize for time-on-Graphite by making the escape hatch to the source of truth hard to find. I rage-click looking for the GitHub URL, give up, then type it manually. If you run session replay, that frustration pattern should be obvious. If a clear link-out already exists and I’m missing it, say where - because if I can’t find it, a lot of other people can’t either. Hide-the-exit is not good product. It’s keeping stats inflated. Again I love Graphite and what you're doing, but this issue has been bothering me from the very first day I tried it.