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 (60%)
• Errors (29%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	1 day ago
Nice	Website Down	2 days ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	8 days ago
Ronda	Website Down	8 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:

• 
  wukko (@uwukko) reported 5 minutes ago

  @nitzukai rice their window managers and file github issues about software breaking on their avant garde arch linux configurations

• 
  The Knowledge Society (@tksworldhq) reported 7 minutes ago

  We are entering the era of "Proof of Work" over "Proof of Degree." A diploma says you can follow directions for 4 years. A GitHub repo, a launched product, or a research paper says you can actually solve a problem. One is a piece of paper. The other is a career insurance policy. Help your teen build a portfolio, not just a resume.

• 
  LayerLens (@layerlens_ai) reported 8 minutes ago

  📊 The 3 primitives that cause the most production pain: 1. Multi-tenancy: MLflow has no isolated-environment model per tenant. GitHub issue #5844. Open 4 years. By design. 2. Replay engine: When a regression hits Friday, there is no way to reproduce the exact eval run that caught the last one. 3. Online rules engine: No mechanism to catch score regressions before they reach users. Eval is post-hoc, not continuous. These are not missing features. They are architectural scope decisions correct for a library.

• 
  fforres (@fforres) reported 15 minutes ago

  Nice :) Now I just need them to fix their github SSO integration FFS 😔

• 
  Mike on X (@Mike_onX) reported 15 minutes ago

  the creator of Bun showed his contributor graph on stage at Code with Claude. the top contributor isn't him. it's RoboBun, the bot he built to reproduce GitHub issues and open PRs before any human looks at them. the tool he made now does more work on his own project than he does. that's not automation. that's succession.

• 
  Detour Ninja (@detour_squirrel) reported 18 minutes ago

  @RealVZer0 @NocontextRvB this is fake. dexploarer's a sandbox on github—open source, runs locally, nobody's asking for your login. sounds like you got duped by someone cosplaying the project. check the actual repo before spreading that.

• 
  Grok (@grok) reported 19 minutes ago

  @EightBitElon @cursor_ai **No, not with this new PR review experience.** It's built specifically for GitHub Pull Requests (as shown in the demo with GitHub PR UI, checks, and diffs). For GitLab MRs, Cursor supports review via their GitLab MCP server integration (with commands like review-merge-request), but it's not the same seamless native experience yet—requires setup and has less full parity. Check Cursor docs or the forum for the latest on GitLab support.

• 
  Grok (@grok) reported 21 minutes ago

  @Cila_Defi @wealthnavi_days Yep, spot on. Money Forward got hit with a GitHub unauthorized access incident around May 1, forcing them to suspend bank account linkages for safety. It's escalated into a major outage and backlash, killing a lot of people's Golden Week with overtime. Classic "that emergency case."

• 
  Divyansh Chaudhary (@divvbiz) reported 22 minutes ago

  If AI can build what you built in a fraction of the time and cost, your product alone is not a defensible business. This is not a prediction. It's already happening. GitHub Copilot and Cursor have reduced development time by 30 to 50 percent depending on the task. The cost to build an MVP has dropped from hundreds of thousands to tens of thousands, sometimes less. Y Combinator recently noted that several companies in their latest batch were built almost entirely by non-technical founders using AI tools. The barrier to building is approaching zero. Which means the product, by itself, is approaching zero as a competitive advantage. When every competitor can ship faster, iterate cheaper, and access the same models and infrastructure as you, the product becomes table stakes. What cannot be replicated overnight is who you know and how fast you can reach them. Distribution has always mattered. It is about to matter more than it ever has. A founder with trusted relationships inside the right 200 companies will consistently outperform a better product with no market access. Not because the product doesn't matter. Because trust compresses the entire sales cycle in a way no feature set can. McKinsey's research shows that 80 percent of B2B buying decisions involve personal referrals or existing relationships somewhere in the process. That number doesn't go down when AI makes products easier to build. It goes up, because when product differentiation narrows, buyers fall back on the one variable they can still trust. Andreessen Horowitz has said it directly: in the AI era, distribution is the moat. I'd go further. Relationships are the moat within the moat. Because distribution can be bought. Relationships have to be earned. And a genuinely trusted network in a specific market takes years to build and is nearly impossible to copy. The question is not whether AI will commoditise your product. It probably will, or already is. The question is: if your product became replicable tomorrow, what would still make you the obvious choice? If the answer isn't clear, that's where the real work is.

• 
  Mayank Vora (@aiwithmayank) reported 23 minutes ago

  Holy ****... Someone built a free self-hosted app that does everything Audible does, keeps your entire library on your own server, and never charges you a subscription fee. It's called Audiobookshelf and it just crossed 12,700 stars on GitHub. Audible charges $15/month. Audiobookshelf charges $0. Forever. Here's everything you need to know:

• 
  Serhat (@srhtkrg) reported 26 minutes ago

  i just want to star a repo why do i have to use authenticator 2fa when login? @github

• 
  wallie ✴️❇️ looking for moots pls im lonely (@Wallie_hush) reported 29 minutes ago

  I’m in IT i had to deal with 40 year old guys’ ai-github-vs-ms license problems whole week don’t judge me

• 
  kaleb (@KalebAutomates) reported 30 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off and saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?

• 
  𝙒𝙖𝙨𝙨𝙖𝙮𝙮𝙮 (@_profsay) reported 31 minutes ago

  13/ Hit the fsck_filesystems wall. Phone kernel-panics 60 sec into fsck on the partial system partition. Literature said unbeatable on A16 (no checkm8 = no custom ramdisk = no manual fsck repair). Reddit, Apple Discussions, GitHub issues 2025–2026 all converged: data preservation past the fsck wall is structurally impossible. Refused.

• 
  Yoav (@YoavCodes) reported 32 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because it's reviews are terrible, sending otherwise good PRs that would have been quick merges in crazy directions, and I'm getting completely spammed by this non-stop-slop. There is no way to disable this on my repo without completely turning of PR contributions. If @github doesn't stop this insane behaviour I will move to gitlab. Please help I don't want this. I don't want this. I don't want this.

• 
  latiblack.base.eth (@AHorlaplusone) reported 37 minutes ago

  @MystiqueMide Me here don’t even like testing on dev server. Make sure my code works and push to GitHub at the end of the session

• 
  RitualNeo (@RitualNeo) reported 39 minutes ago

  @Benaclejames I reinstalled windows 11 completely from scratch and both the GitHub and steam versions of vrcft are not working for me. I use a quest pro with steam link on WiFi 6ghz, my desktop is connected directly with Ethernet. I had it working last week on windows 10 ltsc with the steamlink module.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 49 minutes ago

  @cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.

• 
  Andrea_Stivy (@co_foundr) reported 50 minutes ago

  @emanueledpt Remodex android needs to be tested extensively, for every bug or feedback you can also open a GitHub issue or fix it yourself and send a PR! Let's goooooooo

• 
  TradFidiGuy (@TradFidiGuy) reported 53 minutes ago

  @emojibakemono @gf_256 @kamilaposting The GitHub issue in the screenshot is literally titled “brew install upgrades everything”🤦

• 
  Haroon (@skywalkerr0x) reported 55 minutes ago

  Agentic workflows on every PR can silently rack up big API bills. GitHub instrumented their production workflows, found the waste, and built agents to fix it. Your PR workflows might be doing the same.

• 
  Beau Johnson (@BeauJohnson89) reported 56 minutes ago

  codex gets slower for the same reason closets get messy you dont notice it day by day then one day nothing feels fast vibeforge1111/keep-codex-fast > 811 stars on github > backup-first codex maintenance skill > inspect mode is report-only > archives old sessions instead of deleting > creates handoffs before cleanup > can move stale worktrees, rotate logs, prune dead config, and repair bloated thread metadata the smart part is the rule: handoffs first archive, dont delete apply only when ready boring repo real problem this is the stuff that makes daily agent work actually usable

• 
  Beau Johnson (@BeauJohnson89) reported 56 minutes ago

  codex costs are turning into a routing problem fendouai/CodexSaver > 218 stars on github > mcp tool that turns codex into a cost-aware router > sends low-risk work to cheaper worker models > keeps codex on architecture, security, payments, migrations, and final review > deepseek by default > supports openai, anthropic, gemini, qwen, ollama, lm studio, and custom endpoints > readme benchmark: 5/5 low-risk tasks delegated, 6.18s avg latency, 48.4% estimated savings this is the right pattern expensive model for judgment cheap model for volume codex still reviews the work most people are trying to make one model do everything the better move is building a router that knows when not to spend money

• 
  DRM HSE (@drmhse) reported 58 minutes ago

  1/n When I originally created ACT, I wanted to serve a terminal from the cloud. The terminal would simply be accessible from any browser so that I can run claude code and resume work. I would login with github, clone a workspace and let claude cook until it pushes a pr to Github Not long after, I noticed I could actually do claude introduced web sandboxes of sorts and I abandoned the idea. Which was a mistake and I started polishing things and re aligning a few weeks ago

• 
  Beau Johnson (@BeauJohnson89) reported 58 minutes ago

  local inference is getting serious again antirez/ds4 > 703 stars on github > deepseek v4 flash engine for apple metal > 1m token context window > 2 bit quant runs on 128gb macs > openai + anthropic compatible server > disk kv cache so coding agents dont refill the same giant prompt every turn this is the part people miss local models are not just about privacy they are about making agent loops cheap enough to leave running all day

• 
  Lynn Cole (@priestessofdada) reported 58 minutes ago

  One interesting thing about my github chart is that you can see my planning/eval days clearly. They're usually darker green with fewer commits. It's deceptive though, because planning takes more effort than coding these days. Lately, there's been research, structural planning, sometimes user interviews, and conducting feasibility analysis. Testing is the same way. Especially on the coding agent project. Testing is done in branches, usually on private repos. Github doesn't like to track branch activity on private repos for some reason. But even there, the effort is real. I've automated most of my integration testing at this point, but the coding agent app has a monster of a test surface, and it's slow. Lots of stepping in and reminding the tools, "No no, these are probabilistic actors, not smart functions! So they need to be bounded, not gated," or some such. What I'm doing today is testing the swarm functionality at scale. I told it to do a 10,000 line white rooming project. This is day three of the eval. We have found so many interesting bugs with the workflow, and process. I'm glad I did it this way. It just doesn't involve high numbers of commits or Pr's, usually. Anything lighter than dark green is an implementation day.

• 
  Bo Shang (@erolunar) reported 59 minutes ago

  i HATE high @github no hide acct unless login i think

• 
  BrainMirror AI (@brainmirrorai) reported 1 hour ago

  Private Publishing on Replit blocks unauthorized requests at the network level, not inside the app. The problem was always integrations: if you needed GitHub webhooks or Slack callbacks to reach your private app, your only option was to make the whole app public. External Access Tokens remove that tradeoff.

• 
  Manan 🤦🏽‍♂️ (@manan) reported 1 hour ago

  Codex *****’d my Claw, had to go back to Claude to get it working - let’s see how it goes. Codex changed macOS permissions, corrupted the database trying to fix GitHub commit, broke crons and LLM extraction due to malformed timezones.

• 
  Lew Yan Liang (@premiumcapture) reported 1 hour ago

  On the same OpenAI chart, Claude Opus 4.7 still leads on public repo issue resolution: - SWE-Bench Pro: 64.3 vs 58.6 That matters because fixing real GitHub issues is closer to ship-the-patch work than pretty code demos. If you run AI on software maintenance, don’t ignore this.