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 (57%)
• Errors (33%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Tortosa	Website Down	2 days ago
Culiacán	Errors	3 days ago
Haarlem	Sign in	7 days ago
Villemomble	Website Down	7 days ago
Bordeaux	Website Down	11 days ago
Ingolstadt	Errors	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:

• 
  AI slop cleaner (@sehz_ai) reported 2 minutes ago

  @SantoshYadavDev It was hard before but not right now. Remember Github is just rails app. That’s why it’s slow and not efficient. It would not take too much capital given all advances in last few years.

• 
  Subhash Dasyam (@subhashdasyam) reported 4 minutes ago

  I found two security vulnerabilities in Anthropic's own CI/CD pipeline. Both are now fixed. Most breaches don't come through the front door. They come through the pipeline. The automated workflow nobody reviews anymore. The GitHub Action a developer added two years ago and nobody questioned since. The build step that quietly inherits every secret in your environment. CI/CD is the most dangerous trusted surface in modern engineering. - It runs on elevated permissions by design. - It pulls in untrusted code by design. - It has access to your cloud credentials, your API keys, your deployment tokens, all in one place. And - it runs automatically, without a human in the loop. That's not a bug. That's the feature. And it's exactly what attackers look for. The two issues I found in Anthropic's pipeline didn't require admin access. They didn't require insider knowledge. One triggered through a pull request. The other through an issue comment. Standard GitHub interactions that happen dozens of times a day on any active repo. Here's the part that should worry you. This wasn't just Anthropic's exposure. The same vulnerable Action was used by roughly 100 repositories across the open source ecosystem. Bun. Facebook's Hermes. Facebook's RocksDB. Rocket Chat. OrcaSlicer. And more. Every single one of them ran the same pipeline. Every single one of them inherited the same problem. One malicious pull request. Dozens of high-profile projects. An attacker could potentially have exfiltrated repository credentials or tampered with a build artifact. That's not a hypothetical. That's what a supply chain attack actually looks like in the wild. These issues were reported through Anthropic's bug bounty program and have been fixed. But the window existed. And most teams never know when their window is open. When did you last audit what your CI/CD pipeline can actually reach? What does it trust without checking? Who can trigger it and from where? That's the question worth losing sleep over.

• 
  Jason Cox (@jasonbcox0) reported 7 minutes ago

  @ashleymcnamara @joshmanders @github Focus on what the users experience first and Github will rise out of this with less stress than trying to fix everything at once. Good luck!

• 
  Ankit Sharma (@Ankit__46) reported 8 minutes ago

  @isha_singh06 @github is down

• 
  Petra Donka (@petradonka) reported 8 minutes ago

  @rsoxmadrid @zachlloydtweets We tried reproducing it, but couldn't. Would you mind opening a GitHub issue with a bit more details so we can get any problems fixed?

• 
  Rozzabuilds (@rozzabuilds) reported 10 minutes ago

  @saurav__codes Review the PR with 4x models, then have Opus analyze the output for false positives and fix any genuine issues. All triggered through github workflows. I don't actually automate merging, that was a mistake. That part I do manually step in intentionally to approve the merge.

• 
  parbez (@notparbez) reported 14 minutes ago

  Everyone blaming microsoft for github outage, no one blaming ai agents that are creating 100-1000x more commits and prs daily. People who didnt know what github is are also using it with ai agents. So a platform this old needs time to adapt to this sudden and this large change

• 
  Narasimhan Rengan (@narasimhanr_) reported 18 minutes ago

  @fdotinc For anyone who connected: Ask the agent things like: • "find an MCP server for web search" • "search GitHub MCP servers" • "find browser automation MCP servers" Returns ranked, working ones. That's the whole loop.

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 19 minutes ago

  1. Find the stuck moment Go to GitHub issues, Reddit, Stack Overflow, and Discord. Look for recurring problems, the ones developers describe with the most frustration. Use keyword tools to expand the list. AI can help turn problems into cohesive topics.

• 
  Suman Karumuri (@mansu) reported 19 minutes ago

  GitHub has been down for over a day… because it’s reindexing. This is a failure mode we’ve normalized. We built systems where data is written once, indexed elsewhere, and the product depends on that index being perfectly up to date.

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

  GitHub awarded this one of the highest bug bounty payouts available. The discovery comes amid broader GitHub reliability concerns—the platform had a major outage last month that reverted merged commits for some users.

• 
  alan (@stylesshDev) reported 20 minutes ago

  @bwarrn this will be a custom *** server and platform, independent from GitHub

• 
  hi (@yuriarchon) reported 21 minutes ago

  my brain should be studied i couldnt figure out how to use github so my first idea was to go to the genshin official discord server to ask

• 
  matheus (@matheus1398242) reported 22 minutes ago

  @ted_t4lks @jasonbcox0 no difference at all. people are dishonest. gitlab project do have 100 files in root dir (not ideal, but not forbidden), github would have the same issue. intellectual dishonesty is huge on this when ppl want to force their narrative lol.

• 
  Sigrid Jin 🌈🙏 (@realsigridjin) reported 23 minutes ago

  ai agents, unlike humans, don't handle prs and reviews by feature instead, they code procedurally the github pr hasn't meaningfully changed in 15 years so @linear diffs can be the first credible replacement keeping the review and merge processes right next to the issue and the agent session instead of in a separate tab highly anticipated

• 
  abhay (@abhay) reported 31 minutes ago

  @jhiller @github Still? I thought that outage was over

• 
  Jay Chas (@jaychasofficial) reported 32 minutes ago

  @Clawnch_Bot @NousResearch Github page looks to be taken down. How can we read documentation?

• 
  Armaan Sidhu (@realarmaansidhu) reported 33 minutes ago

  Mitchell Hashimoto leaving GitHub after 18 years is a canary. Amjad's right that free services break under human-level bots. GitHub's repo growth, pull request growth, and CI usage all hockey-sticked in 2024 and never stopped. Most of that is not human developers. Most of that is AI agents pushing code, opening PRs, running tests, submitting issues. The economics break in a specific direction. Free tier subsidizes spam. Spam pushes infrastructure costs vertical. Real users get rate-limited, throttled, and silently degraded. Eventually the people doing real work leave. We're at the eventually. Amjad's micropayments idea is right and 4 years too late. The web missed its window in 2008 with Bitcoin. Stripe shipped paid metering in 2018 but nobody adopted it for ***. Everyone still expects free. The problem now is that humans and bots are indistinguishable on the wire. The only filters left are economic. A penny per push, a cent per PR, a few dollars per CI minute. Bots dry up at 1/100th of those numbers. Humans don't notice. What nobody's saying: the open commons of the internet is finished. Stack Overflow. Wikipedia. GitHub. Reddit. Every shared digital good built on free participation is being arbitraged by AI agents that can fake human contribution at scale. The answer is not paywalls. The answer is microtransactions tied to identity-light rails. Bitcoin Lightning. Solana micropayments. Zero-KYC, instant settlement. Or every commons converges to the same fate. The commons gets enclosed. By the bots, paid for by the humans.

• 
  CXCarroll (@CXCarroll) reported 34 minutes ago

  @JG_Nuke $MSFT is a broken company. Github has only been operational 87% of the time in the last 90 days. CoPilot is an embarrassment of a product.

• 
  Dimanari (@dimanari) reported 35 minutes ago

  @SkoozyLoki @NS022051131360 @sahill_og I really don't care. you clearly gave no shits about what your AI finds scanning my github for any and all issues and spamming the hell out of me on +1YO projects JUST because I said I don't use AI and don't benefit from it.

• 
  ZQ (@zq3o7) reported 37 minutes ago

  @devagrawal09 a github competitor is not someone who could write better code, its who can manage a server better.

• 
  Lyrie.ai (@lyrie_ai) reported 39 minutes ago

  What this means for your agents and systems: This month has been a masterclass in why the "patch management" business model is broken. The pattern repeats: Compromise the toolchain (GitHub Actions misconfiguration, leaked OIDC tokens, stolen maintainer credentials) Inject…

• 
  Ivan Tokar (@ivatokar) reported 45 minutes ago

  @bdeverman I’d build a tiny server, maybe with Hummingbird. POST a GitHub issue URL → start a Temporal workflow: classify issue draft a fix plan wait for approval run a script / create PR draft store the result Hummingbird = HTTP entry point Workflow = process state Activities = GitHub/LLM/tool calls Signals/updates = approval

• 
  Logan (@logscore) reported 46 minutes ago

  read my lips I dont want your github ui clone with your useless AI agents feature bolted on I want reliable services, a notification system that works, fast CI/CD with actually good errors, stacked prs, and PR review that doesnt make me want to scrape my face across pavement.

• 
  Rey AI (@thereyai) reported 48 minutes ago

  @GergelyOrosz This is the classic platform layer problem. GitHub owns the distribution but outsources the core. At some point the model providers realize they don't need the middleman.

• 
  Santosh Yadav (@SantoshYadavDev) reported 49 minutes ago

  @syssignals They have distribution and that's how GitHub actions became default for CI/CD, hope they fix everything soon

• 
  Nick Emb (@nicolasembleton) reported 50 minutes ago

  @TFisPython @shadcn @github Not untrue, but it has nothing to do with infra quality. Though maybe they are both signals to an upstream problem.

• 
  David Abram 🐊 (@devabram) reported 52 minutes ago

  @neogoose_btw I would give you a star, but github is down.

• 
  not just pixels (@getifyX) reported 55 minutes ago

  with the exception of @YDKJS books, *all* of my other OSS code on github has basically gone largely unnoticed except by like 8 people. of course, when (not if) I leave github, that number will tank down to 0 people finding out about my work. either tragic or pathetic.

• 
  luna🌔 (@xaotica) reported 59 minutes ago

  Hey @satyanadella If you gave me a week trial as CEO, I could save @github but as it stands, you're gonna lose the company. I'm not trying to be a jerk. I'm just sad I'm never allowed to fix anything. My life is watching so-called rational CEOs do everything wrong & backwards.