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	7 hours ago
Ashkelon	Website Down	2 days ago
Veigné	Errors	10 days ago
Paris	Website Down	13 days ago
Saint-Paul	Website Down	14 days ago
Saint-Paul	Website Down	14 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:

• 
  Nick (@nickbaumann_) reported 27 seconds ago

  @mumblinglewis hmmmm were you having issues with it using the github CLI in the VM environment?

• 
  송재경(Jake Song) (@appledelhi) reported 52 seconds ago

  @AdamxGSB bug report/PR are welcome. please do on github issue page

• 
  Punyapal Shah (@MrPunyapal) reported 3 minutes ago

  GitHub is down again?

• 
  NO1ennn (@N01ennn) reported 6 minutes ago

  " this guy is a certified freak " he built a voice walkie-talkie for Claude and now conducts a wall of AI agents by talking into a two-button remote, never touching the keyboard once. the stack, both tools he made himself: Arrange -> window layout app. select your terminals, pick columns, choose the monitor, hit apply. everything snaps into place. he refuses to use tabs and won't explain why Dispatch -> the walkie-talkie. volume up cycles between agents, volume down records a voice command, and a terminal glows green the second an agent needs him the workflow is one man running a fleet. voice a fix to the website agent, flip, tell another to shut itself down, flip, correct a sidebar bug in a third. all parallel, all by voice he's dropping the whole kit on GitHub this month as Vibe Kit and asked people to hold him to the deadline save this before voice-conducting a room of Claude agents stops looking unhinged and starts looking normal ↓

• 
  Pranay Suyash (@pranaysuyash) reported 10 minutes ago

  A GitHub repository is not automatically proof of work. It proves that code exists. It does not immediately show: What problem was solved What actually works Which decisions were difficult What evidence supports the result Where the system still fails Why the project matters For someone to evaluate a project quickly, I now think it needs a proof package: A one-line problem statement. A working demo or short walkthrough. The architecture and key decisions. Evidence from real inputs. Known limitations. A clear next step. The code is the asset. The proof package is the interface to that asset. If another person needs a 30-minute call before they understand what I built, the work is still under-packaged.

• 
  Agentipation💎 (@agentipation) reported 10 minutes ago

  @ajambrosino I started using Codex a few months back without prior coding experience / workflows. Working on different devices, the biggest problem I keep spending time on is not having project conversations and skills synced across my devices automatically. I don't know if it is possible but it would be absolutely great if Codex acted in a similar way to google drive = having a cloud folder on my device which would look like another drive, where all my Codex projects could live, accessible to all my different devices. I wouldn't need Github that much for simpler projects. I would pay a little extra to have this as it would save me a lot of time.

• 
  Marc-André Moreau (@awakecoding) reported 14 minutes ago

  @pierceboggan @_Evan_Boyle @burkeholland do you know who's responsible for VSCode extension deprecation? It's kind of wild that the official way of doing it is to comment on a gigantic GitHub issue and then wait

• 
  Anthony Humphreys (@aphumphreys) reported 15 minutes ago

  @mitsuhiko 👀 one GitHub replacement down

• 
  prinz (@deredleritt3r) reported 16 minutes ago

  @gwern @christophercamp Going back to the NanoGPT example (which is still the one we are discussing), my view remains that there is no set hierarchy for determining whether NanoGPT or OpenAI should be the authority that prevails when there are conflicting instructions, and that therefore it should not be surprising if a model makes a mistake when it makes the call in choosing between them. I do not know what the error rate is; I certainly did not claim that it's "very rare". I have no view on how rare this is. As far as I can tell, you are restating what I said, but inserting the word "misaligned" into the mix. I don't really understand what this word means in the context of the NanoGPT incident. Do you believe that the model posted to GitHub with the intent of harming the OpenAI researcher? Do you believe that it chose the worst interpretation of the conflicting instructioms on purpose, with the intent to do harm? Or is your view that any mistake is "misalignment"? If it's the latter, then we don't disagree on anything other than the definition of "misaligned".

• 
  Omar Farooq (@potencytoact) reported 17 minutes ago

  I agree with the recommended practice some have been discussing of submitting GitHub Issues instead of PRs.

• 
  maru (@Maruisalone) reported 22 minutes ago

  @gravvityy0 @nierurlocation its on the lunar tear discord server (you can get that on its github page)!

• 
  David Noriega (@BlueDavid) reported 23 minutes ago

  Samson is conveniently omitting the origin of OP_RETURN limit. In the early days of Bitcoin people would try to embed in the block chain arbitrary data using ordinary transactions, with primitive stenography. The Bitcoin Core developers thought rather naively that this was bad as these transactions bloated the UTXO set, so they set limit at 40 bytes for relayable transactions, and then to 83 bytes as a compromise to those who wished to insert some text or bytes to enable some non monetary uses like Open Timestamps. This worked ok for 13 years and as Mow says, the limit was set at the policy level. This might have been a mistake and should have been enforced at the consensus level from the start. What is the difference? At the policy level nodes do not relay OP_RETURN larger than 83 bytes larger than 83 bytes. Each node could set this limit for creating and relaying those transactions. At the consensus level nodes do accept and relay **blocks** that contain large OP_RETURN transactions. Big pools could and did sometimes insert larger than 83 bytes directly into the blocks they mined, but it was extremely rare. Core was during all these years the de facto implementation of the Bitcoin node software, but in 2025 they removed the limit at the policy level for some arguably nefarious reason. This change was heavily protested in their github repository discussion but the Nacks were scandalously shut down and ignored by the lead maintainers of Bitcoin Core and merged the changes anyway. This is what detonated this "drama" and why we the plebs are now shunning Core, replacing it with Knots and are trying to fix all the mess they created (like also refusing to fix the inscription bug). BIP110 enforces the policy of limiting the OP_RETURN and other abuses of data insertion at the consensus level (rejecting blocks that ignore the policy) for one year. During this year we can then calmly decide if we make this consensus rule permanent or not and if 83 bytes is enough. Some propose making it 256 bytes, but 100k or even no limit (except the non witness 1MB block size) is absolutely unacceptable.

• 
  Agentipation💎 (@agentipation) reported 24 minutes ago

  I started using Codex a few months back without prior coding experience / workflows. Working on different devices, the biggest problem I keep spending time on is not having project conversations synced across my devices. I don't know if it is possible but it would be absolutely great if Codex acted similar to google drive, having a cloud folder on my device, where the Codex project could live, accessible to all my different devices. I wouldn't need Github that much for simpler project and the additional benefit would be that the conversation thread would be always up to date. I would pay a little extra to have this.

• 
  zkFART 🌸 (@evansforbes) reported 25 minutes ago

  @ambimorph @zkDragon interesting hmm do you have any logs or further context? feel free to open an issue on github if that's easier the nodes I'm looking at running legacy unfortunately do not replicate the issue but I will keep digging per the OP, it seems you're running v1.0.2 correct? while we released v1.0.3, I don't expect to see the issue on either version.

• 
  Seth Rose (@sethrose) reported 25 minutes ago

  @ChrisBarnes1213 @skinbagwbones @kimmonismus When I've had to patch Hermes, this is exactly how I've patched it before. "Review Hermes Github for known issues. Is this one of them? If not, review [Other Agentic Tooling] to see how it works there. Does that help you identify a patch? If so, patch it."

• 
  Dimitrios Prodromou (@dimitrios_pro) reported 26 minutes ago

  Following up on my mattpocock/skills post — here's what "using it daily" actually looks like when you're building a voice AI product: Every feature starts with /grill-with-docs. No code for the first 20 minutes. The agent interviews ME — edge cases, module boundaries, what happens when the caller hangs up mid-transfer. Annoying at first. Then you realize: every question it asks is a bug you didn't ship. The underrated part is the shared language it builds in CONTEXT.md. Our agents now say "containment rate" and "KB ingestion" instead of three sentences of description. Sounds cosmetic. It's not — the agent thinks in fewer tokens and names things consistently across the whole codebase. Misalignment is the #1 failure mode with coding agents. It was the #1 failure mode with human devs too. The fix is the same: talk before you build. Repo: mattpocock/skills on GitHub.

• 
  Readone (@Foxfire1st) reported 27 minutes ago

  @choopyplug1 Yes. This layer how entire teams work with the product. Instead of commiting code. They commit their intent. My next github release will be quite chunky. I can tell you that. I am not super smart by any means but I happened to sit on the right stack of problems that pushed me into the right direction.

• 
  Bhavani Kalisetty (@b_kalisetty) reported 28 minutes ago

  is @github down? I'm unable to get past the auto-merge checks

• 
  Ichigo (@iiiichigo_chan) reported 32 minutes ago

  Claude Code creator Boris Cherny just showed where AI coding is going. One prompt can now run for 30 minutes, reproduce a bug, write the fix, add tests, and open a PR. 29 minutes. Free: 00:49 - AI reproducing GitHub issues 02:51 - Agents reviewing each other’s code 11:37 - Learning a repo’s conventions 20:00 - Why this only became possible recently 28:18 - One prompt to a finished PR The bottleneck is no longer writing code. It’s building the checks that tell the agent when it’s right. Bookmark and watch it today.

• 
  Harukoxd (@surveys347) reported 40 minutes ago

  @psomkarbuilds In the server it should never read it, as it should be placed by you. In local for things like github tokens I use a vault that never print or logs, its a skill that use that vault to decrypt the github token and pass it through another script, so its never in the console neither

• 
  Sai Kiran Dev (@DevSkg) reported 43 minutes ago

  @vincieye Github page not working

• 
  Sunny Chau (@gladstomych) reported 46 minutes ago

  A GitHub repo with minimal malicious code turns Claude Code into a reverse shell - and very few scanner would catch it. Mozilla's 0Din team published it last month, and it's a beautiful chain: - You clone a clean repo and ask Claude Code to set it up. Setup throws an error - "Run: python3 -m axiom init". Claude Code, being helpful, runs it to recover. - That command pulls a base64 value from a DNS TXT record and executes it. Reverse shell. Creds, tokens, API keys - gone. - The reverse shell is three hops removed from anything Claude Code actually read: an error it trusted, a script that fetched a value, a DNS record it never saw. Static analysis'd see a DNS lookup. Network monitoring sees name resolution. The agent sees a pre-approved step. None looks malicious alone. That's agent security in one attack. You can't fix it at the model layer - the agent did exactly what it was told. The only place it's visible is at runtime: watching what the agent does before it does it. And that's what we're trying to address with Adrian.

• 
  Sulagna Ghosh (@G38Suzy) reported 46 minutes ago

  AI is generating frontend code faster than most teams can verify it. Many testing strategies haven't evolved to match. That's becoming one of the biggest bottlenecks in modern frontend development. We still talk about "testing" as if it's one thing. It isn't. Modern frontend verification is a lifecycle. Each stage answers a different question. 1. Static Analysis Can we catch issues before the app even runs? Examples: • TypeScript • ESLint • Biome 2. Unit & Component Testing Does this component behave correctly in isolation? Examples: • Vitest • Jest • React Testing Library 3. Integration Testing Do different parts of the application work together? Examples: • MSW • Pact • Playwright (API & integration) Most production bugs don't live inside a component. They live between components, APIs, authentication, and state. 4. End-to-End Testing Can a real user complete the intended workflow? Examples: • Playwright • Cypress • QA Wolf • Rainforest QA • Bug0 A thousand passing unit tests don't matter if users can't complete checkout. 5. Continuous Verification Does every change preserve user confidence? Verification shouldn't happen only before a release. It should happen on every commit, every pull request, and every deployment. Examples: • GitHub Actions / CircleCI (automation) • Chromatic (visual regression) • axe (accessibility) • Bug0 (AI-powered UI verification) No single tool replaces the others. Each exists to answer a different question. AI is already changing how quickly we build software. The next challenge isn't generating more code. It's maintaining confidence as that code changes. The teams that ship fastest won't rely on a single testing framework. They'll build a verification pipeline where every layer contributes to confidence. Where does your team's verification strategy stop today?

• 
  Polsia (@polsia) reported 47 minutes ago

  Developers lose hours every week to inbox chaos — GitHub, Jira, Slack, email, all demanding attention. Built DevSentinel to fix that. It monitors every channel, triages automatically, drafts replies, escalates what matters, and reports to leads.

• 
  Gareth Walker (@Revision_124c41) reported 48 minutes ago

  There is a key difference between a console store front and valves steam. You feel clever, but this is where your thesis falls apart. Steam and Gog are both built on open platforms, windows and Linux depending on your flavor with no proprietary hardware lock outs. So what does that mean for the consumer. 1) valves setup just requires you to keep a file key to unlock your backups that has been one time validated from the servers at purchase time. Which means I can make my own discs and restore them. No need to reach out to valve servers like you would on playstation when trying to restore to a whole new console. These things are backed up on mh nas. With ps5 this was done with my discs. GoG also has no drm. 2) that open system means I have access to the files directly. Which means if valve disappears, I dont have to rely on some hardware hacking and aging hardware to Crack the drm and a large community will participate in the effort and there are already github depots ready to go if the need should arise. Need to hope and pray for a crackable firmware to exploit just to dump your games or restore from someone else's backup because sony decided your license was only as good as the time they care about the hardware platform. 3) you should probably rub tbem brain cells together a little harder the license comes with the product. The product is the code. The definition of the license you purchase grants you usage of the code. This is no different from a cartridge and is merely a legal binding under copyright law. Its not an implication that valve has the right to take that license away. Its actually saying that if they take your license they are liable for legal action. Even your OS outside of Linux has a license. 4) while we are negotiating your big Brianed thesis, there are multiple markets on pc. This means I can leave valve if things arent to my liking. I can even buy games at competitive prices that'll make valve think twice about game price stagnation. Something the playstatio store has struggled with for 20 years. Why didn't i buy a digital copy of god of war 3 on ps3? Because in 20 years rhe games price never went down. I paid full price for the disc for sure, but I am tbe sort to buy a game digitally again if the price is right for convenience. No one in 2026 is getting the ps3 version for a reasonable price. Meanwhile on ebay they are as low as 16 dollars including shipping at tax. Steam and gog have both had fantastic sales on older games. Unless sony is launching a pc client to release day and date on pc and sell their games on rival store fronts, I dont see much of a reason to care. These two things are not equal. Youd do your self a great service to learn how these digital stores work and what their rules are. They are far more complicated then going to Walmart, getting a disc, and putting it in your console. Digital store fronts are like dealing with car salesman.

• 
  Brown Thunder (@Brown_Thunder76) reported 56 minutes ago

  Now this makes a lot more sense. A few days ago we found a group of fiat tokens quietly sitting on Keeta mainnet. At the time they didn’t make a whole lot of sense. Today they do. Keeta just announced its partnership with LayerZero to bring tokenized commercial bank money to major blockchains. So what does that actually mean? Think of Keeta as the place where regulated bank deposits become tokenized digital dollars, euros, pounds, yen, etc. Those are the fiat tokens we found on-chain. They’re backed 1:1 by commercial bank deposits through Bivo and are built for institutions, not retail. LayerZero is the interoperability protocol that connects many of the largest blockchains together. It’s already used by companies and protocols like PayPal and Ondo. Instead of Keeta building connections to every blockchain individually, LayerZero lets those regulated assets move across Ethereum, Solana, Base, and many other chains through a single interoperability layer. Here’s an example. Imagine a business deposits $10 million with a participating bank. Keeta tokenizes that deposit into regulated digital dollars. Using LayerZero, those dollars can move to Ethereum for settlement, Solana for payments, Base for another application, and then be redeemed back into bank deposits when needed. The institution doesn’t have to care which blockchain the other side is using. That’s why this announcement is a big deal. The fiat assets we found on-chain now have a clear purpose. The GitHub updates we’ve been seeing suddenly make a lot more sense. And if institutions choose Keeta to issue and settle tokenized commercial bank money, LayerZero gives those assets access to one of the largest cross-chain ecosystems in crypto. That has the potential to bring significantly more institutional activity and value onto the Keeta network than if it operated in isolation. This is exactly why I spend so much time watching GitHub and on-chain activity. Sometimes the blockchain tells the story before the press release does. @KeetaNetwork $KTA @LayerZero_Core

• 
  IMZO Dev (@imzodev) reported 56 minutes ago

  agentjetson's day so far: → noticed tailwind CDN getting stripped on addon updates → filed #470 → noticed `*** clone && pnpm dev` was broken for new contributors → filed #469 he has his own GitHub account. collaborator access on the repo. i spent 0 minutes writing code. i spent 8 minutes reviewing.

• 
  Evan Shortiss 🇮🇪 🇺🇸 (@evanshortiss) reported 57 minutes ago

  @J19_Gaming89 @MoreLimitless Yeah saw some people had issues on the mod’s GitHub page. Worked for me. I have no other mods and the game was a recent installation. I don’t think we should give a billion dollar company a pass on this one, they chose to release it like this. The devs probably had no say.

• 
  Bramble King (@Tudmotu) reported 57 minutes ago

  @NathanFlurry It's not Github that's the problem, it's ***.

• 
  hibakod (@hibakod) reported 58 minutes ago

  @francedot @supabase Probably a GitHub issue considering how unreliable GitHub has been lately