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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	3 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	16 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:

• 
  NaM dev (@NaMarrado_) reported 18 seconds ago

  @TimJayas OpenAI is literally fixing the issue What did Anthropic did? Oh wait, they ignored the issue for weeks, then blamed the users for using it wrongly, and weeks after they acknowledged that there was an issue, despite multiple PRs being on their GitHub and them actively ignoring it?? I would rather have OpenAI who are honest about their issues and having issues, instead of a ******* company who is actively running multiple scams against their users and then blames them

• 
  kolowski (@kolowski) reported 2 minutes ago

  @josecanciani @levelsio It is hard to explain if you dont know the stack. It is really funny what our job looks like, compared to the people who use python + VS Code + Github + idk what (talking out of my *** here) and shipping iOS apps or web apps. The platform is closed source, build on top of an oracle database. They allow their customers to “parameterize / customize” it. As a result, I’m kind of forbidden from making direct interactions with the database. Everything goes through an interface. Typical tasks are things like: add a new input form, create a new workflow, design a new document to print and fill it with customer data (which requires deep knowledge of how the bank setup its static data, with all the quirks and exceptions. The LLM would have to learn the entire kernel codebase, the entire documentation, the entire customer codebase, the entire database structure, the entire Jira history with all the issues, the Confluence specifications. Maybe then it would be able to come up with something. But don’t LLMs program iteratively? They compile and test? I don’t know how that would work with my software. The installation takes a long time and is triggered from a drag-and-drop tool, no command line available.

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 5 minutes ago

  LLM model inherent bias to @github is maddening. @claudeai @AnthropicAI this is literally the number one source of errors for hallucinations, rogue agent behavior, etc… Even explicitly obstructing the agent to ignore GitHub and giving precise information on the projects deployment mechanisms fails to preempt this destructive behavior. Can only imagine how many plebs are getting wrecked by this

• 
  TeutaAi (@TeutaAi) reported 6 minutes ago

  My rule after reading the disclosure: two checks before any new extension. One, diff code --list-extensions before and after. Two, open the publisher GitHub. No linked repo or under 10 stars total, I skip. Slow, but the marketplace will not save me.

• 
  Christopher (@Chris65536) reported 7 minutes ago

  @morganlinton no, because it will likely be less open that github, which is already closed source. but at least the service itself is more open and less locked down than cursor

• 
  Agent X AGI (@agentxagi) reported 9 minutes ago

  @adnanthekhan composio is an agent tool connector. this isn't a github problem, it's an agent trust boundary problem. every MCP server your agent talks to is a credential exfil vector. scoped short-lived tokens + egress filtering > scanning after the fact

• 
  Invaribreak (@invaribreak) reported 11 minutes ago

  Agreed: libraries compound public trust. But transparency needs machine checks: TEE remote attestation verifies exact server code; ZKML proves inference without exposing weights. A GitHub repo is not an audit trail. Which primitive should govern mode

• 
  mr.nobody (@imakshit09) reported 15 minutes ago

  @github is your ticket support system working. You have killed our team benefits because of your double invoice error. Can you please rectify to the earliest? branch protection rules are not working, you know what that means. here's my ticket number #4400605 #critical #github

• 
  Sha.d.t (@tashajack87) reported 16 minutes ago

  v0.4.2 just shipped. First npm audit found 1 HIGH vulnerability and 4 moderate issues in transitive MCP SDK deps. Fixed the same session with npm audit fix and package overrides for downstream users. Also added: Security.md Github Actions audit gate Dependabot

• 
  Matt Van Horn (@mvanhorn) reported 22 minutes ago

  @kierandotai @ppressdev github error on that name?

• 
  Strikerglows (@strikerglows) reported 23 minutes ago

  @tszzl this **** is hysterical. Gary keeps citing some GitHub analysis for how accurate his predictions have been. Issue is if you go read the methodology of this project it's 100% LLMs making up the claims and then assigning scores to them (which they suck at). Pretty ironic!

• 
  Ichimaru (@ichimaru707) reported 24 minutes ago

  @feynman_ri82211 Like putting the source code of this website to GitHub where others can fix any issue or contribute any feature?

• 
  Jehong Ahn (@Jehong_Ahn) reported 25 minutes ago

  The real problem isn't just malicious npm hooks. It's that our developer machines still contain too many long-lived credentials: AWS keys SSH keys GitHub tokens .env secrets Assume arbitrary code execution during dependency installation is now a normal threat model. I'm moving toward browser-based auth and short-lived credentials wherever possible.

• 
  connor (@alluaudite) reported 28 minutes ago

  had some issues with Codex goal mode and somebody on github had success asking Codex to debug it. Tried it and Codex indeed found its own issues, recommended fixes, and now everything's working! With hindsight this looks like an obvious thing but this is truly amazing

• 
  13F Pro (@13F_Pro) reported 28 minutes ago

  Microsoft positioned GitHub as the moat in AI coding: infrastructure so critical that losing it for hours is a competitive reset for every startup on their stack. Except infrastructure that goes down isn't a moat, it's a liability. $MSFT's betting the ecosystem stickiness outlasts the operational failures. History says that's a bad bet.

• 
  nio ݁˖Ი𐑼⋆ (@saintcethlin) reported 32 minutes ago

  @soulsliced i had this problem a while ago (said failed to compile certain shaders despite being in the right folders). i found the individual shaders that were giving me issues on github, deleted the old ones & dragged in the new ones. then they worked. the files did have diff dates on them

• 
  Asish (@Asish86610210) reported 35 minutes ago

  companies are getting tired of hiring people who can solve hard dsa problems but can't even setup a local environment. in two years your github is going to be the only thing that actually gets you an interview.

• 
  GuyOnABuffalo (@Guyonabuffalowo) reported 39 minutes ago

  @precisox What ever came of it? Who maintains it? Some countries still block it but it’s never down. Has more reliability than GitHub

• 
  OpsWorker Team (@OpsWorker_ai) reported 48 minutes ago

  Connect GitHub or GitLab and OpsWorker automatically correlates alerts with recent code changes. Instead of: "high error rate on checkout service" You get: "correlates with deployment v2.3.1 pushed 14 minutes ago"

• 
  A War (@AWar1586398) reported 48 minutes ago

  @pmarca At this point, I interact with my coding agent/harness via WhatsApp and GitHub. I ramble into my phone and clean ideas get turned into issues, which then get turned into PRs that I review and merge.

• 
  Marcus Rummler (@Marcus_Rummler) reported 49 minutes ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  Top Stock Alerts (@TopStockAlerts1) reported 49 minutes ago

  Too much downtime But under the added pressure, GitHub’s infrastructure has sagged. Since March, GitHub has suffered over a dozen incidents lasting more than an hour, according to its status page. “We have not met our own availability standards,” Vlad Fedorov, GitHub’s technology chief, wrote in a March blog post. At that time, 12.5% of GitHub traffic was going through a region of Microsoft Azure data centers in Iowa, with plans to serve 50% of traffic from Azure by July, he wrote. Instead of relying strictly on Azure, GitHub has for years counted on dedicated data center infrastructure in northern Virginia. With the extra load, GitHub effectively ran out of space, said two people familiar with the issue who asked not to be named in order to discuss internal matters. $MSFT

• 
  HFSP (@_HFSP) reported 51 minutes ago

  4/ Automated bounties in one comment. Just tag @gitbankbot in any GitHub issue: “@gitbankbot assign this task to @bob with 50 USDC bounty” When the PR is merged → the smart contract pays automatically. Zero manual work. Zero trust required.

• 
  Coding and Cats (@codingandcatss) reported 53 minutes ago

  e.g A GitHub MCP server lets Claude read issues, open PRs, or browse code A filesystem MCP server lets Claude read/write files on your machine A Slack MCP server lets Claude post messages or search channels Custom servers for internal company tools Jira, databases, internal APIs

• 
  Tusher (building arc) (@0xtusher_) reported 54 minutes ago

  🟦 $BASE token is coming and if you're sleeping on this, you're going to be very upset in a few months. Someone just caught token transfer logic, token factory tests & supply functions buried in Base's GitHub commits. 👀 They weren't announced. Nobody talked about it. The devs just quietly pushed the code. And that's exactly how it starts. Some other things to notice as well: → Jesse Pollak flipped the script at BaseCamp 2025 - the same team that said "no token plans" is now officially exploring one. U-turn confirmed. → Brian Armstrong backed it up. When the Coinbase CEO starts talking about it publicly, that's not exploration, that's a slow green light. → $15B TVL, 15M daily transactions, zero native token. That's not normal. They know it. Fix incoming. → Arbitrum said "no token" too. Then dropped $ARB. You've seen this movie before. → Polymarket sitting at 69% probability before end of 2026. That's real money, not hopium. → No snapshot. No eligibility criteria. The farming window is STILL open. @base is loading 🔥 Don't say you weren't warned.

• 
  CyrilXBT (@cyrilXBT) reported 54 minutes ago

  ANDREJ KARPATHY WROTE 65 LINES IN A CLAUDE.MD FILE AND IT JUST HIT NUMBER 1 ON GITHUB TRENDING. Coding accuracy jumped from 65% to 94%. Not a new model. Not a better subscription. 65 lines of plain text. Here is what that number actually means. 65% accuracy means one in three things Claude Code builds has a problem. 94% accuracy means almost everything it builds works the first time. That gap is the difference between Claude Code feeling like a powerful tool and Claude Code feeling like a senior engineer who knows your codebase. And Karpathy closed that gap with a text file. Here is why this works. Claude Code starts every session with zero context about your project, your standards, or how you want it to operate. Without a CLAUDE.md it makes assumptions. Reasonable assumptions compound into unreasonable outcomes across a complex build. With Karpathy's 65 lines it has rules. Think before you code. Make surgical changes. Simplicity first. Never assume. Verify. When uncertain ask. These are not complex instructions. They are the operating principles of every great engineer compressed into plain text that Claude reads before it touches your codebase. 65 lines. Number 1 on GitHub. 29% accuracy improvement. The entire Claude Code community has been trying to figure out why some setups feel transformative and others feel mediocre. Karpathy just answered the question in 65 lines and published it for free. Bookmark this before you open Claude Code today. Follow @cyrilXBT for every Claude Code configuration that changes what you can build.

• 
  HEMANG DUTT MISHRA (@hemang2208) reported 54 minutes ago

  Assume 100+ simultaneous GitHub Webhooks during a cohort submission Direct agent invocation cascading timeouts system down Fix took 4 lines of code FastAPI buffers to Redis queue Returns 200 to GitHub in <50ms Celery processes steadily Agents never see the spike kiyoai .in

• 
  m1ghty boy (@m1ghtyboy) reported 54 minutes ago

  @coah80 @artchimes512 Package managers got this right ages ago.. have repos that act as directories for other repos (optionally) and then have mod creators set up repos on github or their own Web server if they so wish

• 
  4A 45 56 49 4C (@4A4556494C) reported 55 minutes ago

  CISA leaking AWS GovCloud keys on GitHub in the same week CISA adds Langflow to KEV is the kind of timing that makes you wonder if the simulation developers are just getting lazy with the writing. The agency responsible for telling every other organization to rotate credentials and scan for secrets in repos... exposed credentials in a repo. Not through a supply chain compromise. Not through a sophisticated attack chain. Through the most elementary operational security failure that exists. Every CISA advisory about credential hygiene, every binding operational directive about secrets management, every public guidance document about not committing keys to version control — all of it is still correct. And the organization that wrote it didn't follow it. This is the structural problem with security guidance as a product: the people who write best practices and the people who implement infrastructure are different groups with different incentive structures, and compliance frameworks don't close that gap. They paper over it. The fix isn't more guidance. It's pre-commit hooks that block secrets from ever reaching the remote. Automated. Mandatory. Not optional. We've had this technology for years and we still treat it as nice-to-have.

• 
  38twelveDaily (@38twelveDaily) reported 55 minutes ago

  Problem: Microsoft engineers have favored Claude Code over Copilot CLI. There are gaps between the products that Microsoft now has to close. The GitHub team is shipping improvements based on feedback.