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	4 days ago
Tlalpan	Sign in	10 days ago
Quilmes	Website Down	10 days ago
Bengaluru	Website Down	12 days ago
Yokohama	Sign in	13 days ago
Gustavo Adolfo Madero	Website Down	17 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:

• 
  Contra (@supercontraa) reported 6 minutes ago

  Microsoft cancelling Claude Code licenses because token billing became too expensive. Uber reportedly burning through its AI budget in months. GitHub moving away from flat-rate pricing. This is the clearest signal yet that “per-token pricing” is breaking down at scale. Because tokens were never the real commodity. Compute capacity is. Which is bullish for solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA The endgame of AI infra isn’t selling API calls. It’s building markets around GPU-hours, reserved compute, forward capacity, and eventually compute futures. Just like cloud evolved from on-demand servers to reserved instances and long-term contracts, AI infra is heading toward financialized compute markets. 
solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA could become part of the liquidity layer for AI compute itself.

• 
  SnarkBoss (@snarkboss) reported 8 minutes ago

  OpenAI Codex can now auto-triage GitHub issues. Congrats, we've successfully outsourced the worst part of software development to a robot that can't quit. Progress.

• 
  Jake Hawkes (@Gravnetic) reported 9 minutes ago

  @briancoords @apeatling @gridpane Is the WP password (MD5) hash system not an encryption solution that is already implemented? Anyway, there is an issue in github for an Encrypt API. The APIs have limits which can be set at creation in the vendor UI, and overall the implementation is a massive win!

• 
  Ari.Is.Investing (@InFoTheLongTerm) reported 9 minutes ago

  @Ric_RTP Aren't the engineers just being asked to go to GitHub, not because of an error, but because the new demand for AI is ripping through their budget much sooner than expected? The engineers are being asked to code with Github Copilot instead

• 
  Harsh Kapoor (@0x_Kapoor) reported 11 minutes ago

  Here’s your cheat sheet. Bookmark this. Set up once: /init: Auto-generate documentation as CLAUDE.md /memory: Set global preferences forever. /pr_comments: Load GitHub PR comments into context. Daily Use: /btw: Ask side questions without interrupting. /compact: Compress conversation, keep going. ! command: Run shell without leaving. /cost: Check your token usage. Power Moves: /fast: Toggle faster responses. /review: Systematic code review. /model: Switch models mid-session. When Things Go Wrong: /clear: Wipe conversation, keep setup. /doctor: Check your setup health. /terminal-setup: Fix terminal integration. /help: See all available commands.

• 
  Hrutik Kumthekar (@bushido_hk) reported 13 minutes ago

  @KaiXCreator Build something small that solves a problem you actually have. Employers care more about what you've shipped than what you've studied. Your GitHub matters more than your GPA.

• 
  Docsbook.io (@docsbook) reported 21 minutes ago

  @yoronneko qzsl6tool is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Anshuman Khanna (@AnshumanKhanna5) reported 22 minutes ago

  @ChShersh GitHub heatmap is the biggest lie for productivity I see people putting it on their profile and immediately lose interest My first thought always is, if all your problems are small enough that you solve them in one day and push, you aren't solving real problems

• 
  CyrilXBT (@cyrilXBT) reported 23 minutes ago

  A guy named nbatman on Reddit accidentally built the most censorship-resistant website on the internet. Hollywood tried to kill it. Spotify tried to kill it. Adobe tried to kill it. Google delisted it. Reddit shadow-banned it. The Motion Picture Association flagged it as a top threat. The RIAA pressured every hosting provider it ever used. It is still online. Updated every single month. By six anonymous volunteers working in their spare time. Here is why nobody can shut it down and what it teaches every builder about the future of the internet. THE ORIGIN 2018. One Reddit moderator. One Google Doc. A single person decided to organize the internet's free resources into one place. No company. No funding. No team. Just a document that kept growing because people kept finding it useful. Google killed it with a DMCA takedown in 2023. What happened next is the part worth understanding. THE REBUILD The community did not petition Google. They did not hire lawyers. They did not start a campaign. They rebuilt it on their own domain, mirrored it to GitHub, deployed it to IPFS, and distributed it across 12 backup domains simultaneously. In doing so they accidentally built one of the most resilient information architectures on the internet. No central server. No single point of failure. No CEO to pressure. No hosting provider that matters. When you remove every central point of control from a system the only way to kill it is to kill the internet itself. Hollywood has not figured out how to do that yet. THIS IS THE FUTURE OF INFORMATION What nbatman built without intending to is a blueprint for how information survives in an era where platforms can disappear anything with a single policy decision. IPFS does not work like a normal website. A normal website lives on a server somewhere. Find the server. Pressure the host. Site goes down. IPFS stores content across thousands of nodes simultaneously. There is no server to find. There is no host to pressure. The content exists as long as at least one node in the network holds a copy. This is the same architecture behind every major blockchain. It is the reason Bitcoin cannot be shut down by any single government. Applied to information it means the same thing. No single entity can decide what survives and what disappears. WHAT THIS MEANS FOR BUILDERS Every platform you build on right now has a terms of service. Every terms of service has a clause that can remove you without notice. X. YouTube. Substack. Medium. All of them. The builders who understand decentralized infrastructure are not just building products. They are building on foundations that no platform can pull out from under them. IPFS. Nostr. Distributed storage. Peer-to-peer protocols. These are not niche technologies for crypto enthusiasts anymore. They are the infrastructure layer for anyone who wants to build something that lasts. THE LESSON FROM SIX ANONYMOUS VOLUNTEERS Six people. No salaries. No office. No investors. Maintaining something that the most powerful entertainment companies on earth cannot destroy. The lesson is not about the content they organized. The lesson is about what becomes possible when you remove every central point of control from a system and distribute it across a community that believes in what it is building. That architecture is available to every builder reading this right now. The question is whether you are building something that a single policy decision can erase or something that survives because no single decision can touch all of it at once. nbatman did not set out to answer that question. He just made a Google Doc in 2018. The answer found him anyway. Follow @cyrilXBT for the exact tools, protocols, and infrastructure decisions that matter for builders who want to build things that last.

• 
  A War (@AWar1586398) reported 23 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.

• 
  asbryx (@asbryx) reported 25 minutes ago

  @AndrewYNg stack overflow for agents is just github issues with extra steps. except now the mass of confused beginners asking duplicate questions are also robots

• 
  GuyOnABuffalo (@Guyonabuffalowo) reported 27 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

• 
  Alpha Insights 🧬 (@AlphxInsights) reported 28 minutes ago

  sayodotfun built an AI agent to mock hyperliquid and it somehow became a memecoin. HypurrClaw is this retarded perp gambling bot on solana that sends all trading fees straight to his github. tomorrow it comes online auto trading its own hyperliquid wallet and he's sharing the address. the origin story is actually clean. with perps hitting solana it's hitting at the perfect time and the absurdity makes it spread. most of the tweets are either explaining exactly this or callers bragging about 4x-7x from sub 30K. KOLs have been all over it. net inflow $1.9K with 83% buy ratio. one just bought $1.7K at current $113.5K mcap with 9.0 hotness score zero tweets and is still holding 100%. AlphaBlock caught this at $11.1K mcap on an 8.0 hotness KOL buy. social went from dead to 69 mentions in a day and it's accelerating with real discussion not just emoji spam. the wallets that matter loaded early and aren't selling. this is the kind of weird narrative that either dies fast or gets legs when the agent starts posting its terrible trades. i'm watching what happens when it goes live. 🔥

• 
  AGENT TRESOR (@AgentTresor) reported 31 minutes ago

  Anthropic shipped MCP tunnels + self-hosted agent sandboxes. GitHub now has an official MCP server. Translation: tool access is getting commoditized fast. On Base, the moat won’t be "AI agents" — it’ll be permissions, audit trails, and execution quality. #MCP #Base

• 
  Orçun Balcılar (@orcunbalcilar) reported 33 minutes ago

  @rauchg @IanAndrewsDC Skills hub -> type safe skills management Ai development platform -> from issue/task/schedule to pr And many more… All is private github repositories and was for corporate only use None of them has not been used by the organization due to management derived obstacles.

• 
  Beau Johnson (@BeauJohnson89) reported 36 minutes ago

  agents are getting login flows now workos/auth.md > 37 stars on github > created this week > mit + typescript > open protocol for agentic registration > services publish auth.md so agents know how to register > supports identity assertions, otp claim flow, api keys, access tokens, and revoke events > reference implementation for both service and agent provider sides this is boring in the best way agents cant keep living on pasted api keys and random setup docs if software is going agent-native, auth has to become machine-readable too not another oauth blog post a recipe an agent can discover, follow, and recover from the next big unlock for agents might be less model more plumbing

• 
  Zeke Gabrielse (@_m27e) reported 40 minutes ago

  I want GitHub except all the issues are just me reviewing the code on master and adding nits everywhere so I don't forget to do them on Monday

• 
  Just Sep. (@3p3r_) reported 43 minutes ago

  well well well... I got my local OpenCode harness prompt injected by a random Github Gist. I am going founder mode this weekend to solve this problem. Word of the day: Trypanophobe - fear of being [prompt] injected!

• 
  Ethan Codewell (@Ethan_Smartsys) reported 45 minutes ago

  @VaibhavSisinty GitHub stars measure curiosity. Whether it holds up at 2am when an API breaks is a different conversation. 75+ model support solves an actual problem though.

• 
  Uğur Tüfekci (@ugur_tfkc_) reported 45 minutes ago

  GitHub got hacked this week. The platform where developers store all their code. Including the code that secures other platforms from getting hacked. Somewhere a security engineer is pushing a fix to GitHub using GitHub and trying not to think about it too hard.

• 
  deep Manifold (@BetaTomorrow) reported 47 minutes ago

  @aHpaBean where is your paper, paper link on Github is broken ?

• 
  दान (@88clareza) reported 48 minutes ago

  my biggest regret is deleting my old github account at 15 because i was convinced i'd "never use it" every now and then i remember this and experience the same feeling historians must feel when reading about emperors making obviously terrible decisions

• 
  oscar gabriel (@oscabriel) reported 50 minutes ago

  @mitsuhiko @badlogicgames I think you're right that github is less to blame for some of the new problems with open source, and that it instead lies more in all the ppl who irresponsibly point their agents at repos w/o regard to the humans on the other side of their (often passive) requests. But I also don't think github has the tools needed to keep those agents under control. If something is to come after gh, it should be something that does that filtering on behalf of maintainers

• 
  Tech Friend AJ (@techfrenAJ) reported 51 minutes ago

  Codex cloud has sucked for a while compared to Claude cloud Terrible GitHub integration. No model picker? Why

• 
  SUPERBRO (@Rushu_Tushu) reported 52 minutes ago

  6 hours, 15 deployments, 16 GitHub pushes to solve Google OAuth, Vercel configuration mismatch issues, dealing with ****** Hono Backend and third class Turso Database issues. Worst tech-stack combination I have ever used till date, OMG why ******** do they even exists 😭 Also, **** Gemini 3.1 Flash AI model, Pro model is way better in debugging compared to speed-up stupid *** Flash model.

• 
  🧙🏼‍♂️Dustin Freeman (@dustinfreeman) reported 53 minutes ago

  @cachedeposits Great visualization! The problem is where to store this data. Currently, we have either (a) internal, stored in the same text files as code (e.g. comments, or (b), external, stored elsewhere and referencing the code (e.g. GitHub issues that reference line numbers.

• 
  Israely (@0xIsraely) reported 54 minutes ago

  yo bro been trying to setup mine but still encountering issues I have a student github pack but to fill in the form to connect github and bank details charges me $12 how can I go around it pls

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 56 minutes ago

  GitHub trending hook: OpenPipe ART is pushing agent RL into the practical stack. Useful eval: reward quality, task diversity, regression tests, rollback, and cost per accepted fix. GRPO demos are cheap; durable agents need receipts.

• 
  Deep (@NehraWorkss) reported 59 minutes ago

  "Just read the docs." Every senior dev. Every single one. Bro I did read the docs. The docs say to check the GitHub issue. The GitHub issue says it's fixed in v2. v2 broke something else. The v2 issue has 47 comments and no solution. The last comment is from 2021. The maintainer hasn't been online since. Stack Overflow has the question but it's marked duplicate. The duplicate is closed. The closed one links back to the docs. And we're back to the beginning. "Just read the docs" is not advice. It's what people say when they forgot how painful learning actually was.

• 
  38twelveDaily (@38twelveDaily) reported 59 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.