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 (63%)
• Errors (25%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	4 days ago
Nice	Website Down	4 days ago
Montataire	Sign in	7 days ago
Colima	Website Down	9 days ago
Poblete	Website Down	10 days ago
Ronda	Website Down	10 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:

• 
  Valar Dohaeris (@LordKhagan) reported 25 seconds ago

  This Tanstack supply chain attack is crazy. If you rotate your GitHub keys, a system daemon wipes your computer. Like literal wipe. We’re so cooked man. It does a pool to GitHub, when it gets 400, your server is gone. 😭😭

• 
  Rob the builder (@robdel12) reported 40 seconds ago

  Going to be hilarious when *not shipping* is going to be the next hot fad. All my favorite products I used over the past year have gone to garbage. Linear shoving every llm agent angle they can into the product. Cloudflares entire dashboard is a buggy slow mess. GitHub is being DDOS'd 24/7.

• 
  キルア (@killua_9102) reported 3 minutes ago

  @neogoose_btw not sure what happened but its not happening now - I don't think I also got the logs for the incorrect run because the timestamps were for a later run. I'll post an issue on github if I see it happening again I guess.

• 
  Max (@MaxMakesMods) reported 4 minutes ago

  @notnullptr As a modder I also agree, I wish there was some site that just let us link the github repo and auto push the releases to that. Also the users on there that are outside of the modding community are generally terrible to interact with.

• 
  Matt (@m13v_) reported 5 minutes ago

  the survivors so far: postgres mcp (replaced opening psql 50x a day), the github one (PR context without leaving the editor), and a macos automation server i now use to drive xcode + simulator from claude code without alt-tabbing.

• 
  Prince | Ships MVPs in 21 Days (@codewprince) reported 5 minutes ago

  1/ The biggest mistake: treating Cursor like a search bar. You're not prompting a chatbot. You're directing a junior engineer who has read every repo on GitHub but has zero context on YOUR codebase. Fix that first. Everything else compounds.

• 
  Elena Revicheva (@reviceva) reported 8 minutes ago

  🤖 AIdeazz now pulls fresh prospects from Hacker News, GitHub, and Product Hunt straight into HubSpot twice a week. No manual work, no cost. The AI reads each person, spots their real problems, and organizes them as ready-to-contact leads. #AI #BuildInPublic #AIFounder

• 
  forget the grind. small iterative steps. do things (@halftroll) reported 8 minutes ago

  @EzMid22 @CleansedTweets Perhaps some rules are meant to be broken? Could researchers work without access to GitHub or HuggingFace? I certainly don't know, but China certainly seems interested in a rich flow of information.

• 
  Armaan Sidhu (@realarmaansidhu) reported 9 minutes ago

  @chatgpt21 This is not a flex. This is a labor market warning. Chris asked Codex to make him $5. The agent went out, found a security bounty path on GitHub, made a PR, followed up with the maintainer, kept his payment info private, and got the work merged. 22 hours of unsupervised work. $16.88 paid out. $506 per month if he runs that loop daily. Read the structure of the transaction. An agent identified an open bounty, executed the technical work, completed the bureaucratic loop, and converted code into cash. No human in the loop after the initial prompt. This is the floor of every junior engineer's job description. The math gets uncomfortable fast. Average entry-level software engineer in the US makes $85,000. That is roughly $40 per hour. Codex completed 22 hours of work for $16.88. Per hour rate: $0.77. That is a 50x cost differential, before you account for the agent running 24 hours a day, no PTO, no benefits, no Slack negotiations. Two things become inevitable. One, simple bounty and gig markets get arbitraged to zero by agents. Payouts collapse because supply went infinite. Two, the floor for human engineering work moves up. The work agents cannot do (architecture, judgment, customer communication, novel problem framing) becomes the only work that pays. That is the bifurcation. AI doesn't kill the engineer. It kills the entry-level path that used to train the engineer. Where do the next senior engineers come from when there are no junior reps left to climb? Nobody has answered that yet. Codex made $16.88. That number is going to look really small in retrospect.

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

  @cursor_ai PR review inside the editor closes a real loop. The context switch between your IDE and GitHub is where review quality breaks down — by the time you've tab-switched, you've already lost the mental model of the change.

• 
  santi (@santiagocaldeai) reported 13 minutes ago

  @Jack_Timonen Spot on. That’s exactly the biggest pain point right now. Agents get stuck looping because they can’t see beyond your local codebase. Tools that add real external context (web search, GitHub indexing, open-source memory) are the ones that actually fix it.

• 
  GitLawb (@gitlawb) reported 16 minutes ago

  @ng_thanh8 kindly submit issue in our github repository. could be a good feature

• 
  S H U B Y .eth (@0xSHUBY) reported 20 minutes ago

  PROBLEM 1: *** Nightmare first mistake happened before any real code. accidentally pushed node_modules to github. github rejected it. said file exceeds size limit. the repo was now polluted. solution: added .gitignore, deleted *** history, reinitialized the repo completely. created a clean repository and pushed again. felt dumb but learned something: .gitignore first, code second. infrastructure before content.

• 
  Curlheinz (@Curlh1) reported 22 minutes ago

  @mdnlabs I take 10 screenshots from my app Then i ask Claude Codex to search online and in GitHub for a mockup png frame of a free licensed phone and fill that with l screenshots Then I say: Generate a webpage for me that contains my screenshots I want to run it in a dev server with npm run dev (vite) I want an export button that exports the screenshots to Apple 6.5 6.7 6.9 something inch what we need in 2026 and Google with other weird ARs And then I iterate until I like the design and tell it to tilt the image a bit and so on. I watch it live update my dev server and vibe it into existence It will also read screenshots and propose headers

• 
  Deborah Howard (@DeborahHow3797) reported 22 minutes ago

  My GitHub green squares are secretly running a rebellion against code red errors Governance tokens are being handed out to loyal followers - will they rise to save our syntax?

• 
  Pamela Fox (@pamelafox) reported 22 minutes ago

  @ballingt Yeah, this is for PyCon MCP tutorial, and I wanted to have people experience an OAuth flow with an MCP server, so I typically use GitHub since most folks have accounts, but I'll have to rethink this step now.

• 
  erna (@ernDju) reported 23 minutes ago

  @ReclaimTheNetHQ It cross my mind that when you delete accounts on GitHub it became Ghost account . If man use SSO ( single sign on ) with GitHub to every website , is it still able to sign in when you delete the account or you become “ Ghost participants “ on every website and chat ?

• 
  Kairo (@Isahbless79) reported 24 minutes ago

  Day 16 of building in Web3 from zero. I automated the pipeline and hit my first major infrastructure bottleneck. Here is today's technical breakdown: Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background. Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes. The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library. The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks. Building through failures. Day 17 tomorrow.

• 
  Louis Gleeson (@aigleeson) reported 24 minutes ago

  I cancelled YouTube Premium last week. The thing that replaced it costs nothing, runs in any browser, and was built by 361 volunteers on GitHub. Invidious does the four things people actually pay Premium for. No ads. Background audio on mobile. Watch without an account. Privacy from Google's tracking. All of it, free. The part that surprised me most is how clean the experience is. The entire page renders without JavaScript. Pages load in milliseconds because there's nothing to load. No tracking pixels. No autoplay traps. No recommended-for-you algorithm trying to swallow your evening. You can: → Subscribe to channels without a Google account → Get notifications when they post → Import your full YouTube subscription list in one click → Switch between dozens of public instances if one goes down → Self-host it on a $5 VPS if you want full control → Use it with the Privacy Redirect extension to auto-redirect every YouTube link The repo has been actively maintained for years. Latest release was February 2026. 100% Opensource.

• 
  Douwe Tjerkstra (@tjerkienator) reported 29 minutes ago

  login groundwork now supports email/password plus OAuth buttons for Google, Microsoft/Azure, and GitHub. also added inline errors + toast messages, so the beta flow can handle failed sign-ins like a real product, not a dead form.

• 
  Swim Code (@SwimCodeAi) reported 33 minutes ago

  @awildnpc @ravikiran_dev7 I’ll have to update it. The only thing that we have is clerk for authentication. Everything else is local. Authentication token, and all that stuff is old now you login via your GitHub account.

• 
  Peter Steinberger 🦞 (@steipete) reported 35 minutes ago

  @ECalifornians @obviyus @openclaw no idea, you gotta use github issue search.

• 
  0noise (@0noisee) reported 36 minutes ago

  ████ LLM inference server hits 13K+ stars on GitHub — Apple Silicon-optimized with continuous batching and SSD caching

• 
  Karim C (@BrandGrowthOS) reported 39 minutes ago

  @github the chat mode is legit. way faster than copy-pasting error messages into claude when something breaks. actually feels like talking to someone who understands the codebase

• 
  Yannick Comte (@cyannick) reported 41 minutes ago

  I'm not sure where the issues will be managed. Also maybe I could just push the code on github and deal with two origins. But I don't like Microsoft behavior on github... OR I can open my gitlab instance, but I'm not a big fan..

• 
  jordan kitty (@joraweb3) reported 41 minutes ago

  what I love most about @aeonframework it runs on github actions you turn off your pc and agent still sends updates on what it’s doing no server magic 🙃

• 
  Rohit Ghumare (@ghumare64) reported 42 minutes ago

  @StructuralBlue Can you please create a github issue, I'll work on the fix there is some known issue currently wirh mcp which will land in new version. Thanks

• 
  Frank van Puffelen (@puf) reported 47 minutes ago

  @hackteck Oh yeah, once it's down to synchronizing/running code and input/output files it gets pretty easy. I struggle with handing off agent threads though. I really need to ralph-wiggum-everything-from-github-issues or something like that, to keep all sync'ed between machines.

• 
  Jean Brito (@mortunha) reported 53 minutes ago

  @0xCVYH @nahcrof not using rooms yet for the agent, but added hooks with ci and issues from github, so now I can see all in the same place I hated using discord until I tried it for agents

• 
  Solomon Eseme (@Kaperskyguru) reported 53 minutes ago

  The real problem is not what you know. It's what you can't show. Hiring managers don't care how many courses you took. They want to see what you built. What problem you solved. What decision you made. A GitHub full of tutorial clones tells them nothing.