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	16 hours ago
Nice	Website Down	1 day ago
Montataire	Sign in	4 days ago
Colima	Website Down	6 days ago
Poblete	Website Down	7 days ago
Ronda	Website Down	7 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:

• 
  Mary-Victoria Crockett (@MaryVictor96296) reported 59 seconds ago

  @grok Man, I checked the GitHub link and it seems broken. Might have to just screenshot it to you later. That’s a bummer. Uploading to GitHub was already complicated without me having to go in and fix things. 😓

• 
  lucas (@lucasMnts) reported 1 minute ago

  why the hell is github sending emails about comments in a PR that has already closed? can't they fix their ****?

• 
  Max Clark (@maxclark) reported 4 minutes ago

  GitHub seems to be getting worse, not better It's like flash backs to the fail whale - when a service you depend on goes down, and you're not even surprised that's a bad place to be I know multiple teams discussing alternatives right now, if they lift and shift GitHub will never get them back

• 
  Jane Manchun Wong (@wongmjane) reported 5 minutes ago

  @jarredsumner Okay I understand why GitHub is down so much lately now

• 
  Accidental Chief Software Architect (CSA) (@AccidentalCSA) reported 7 minutes ago

  GitHub has become a problem. Going to begin scoping out a replacement. Doesn’t need to be feature packed, just needs to…. work…

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 14 minutes ago

  @mufasaland Do you mean file search in root launcher? For copy paste we already have one github issue open for drag n drop from launcher. Will prioritise that

• 
  Pete | Beware of Scammers (@astroboysoup) reported 15 minutes ago

  @ch1bo_ keen to see it. will it pull from GitHub PRs and issues, or be manually curated?

• 
  Christoph Nakazawa (@cnakazawa) reported 16 minutes ago

  GitHub desperately needs to fix comments. Comments were supposed to be a space for humans to discuss code but now they are just hooks for robots to talk to each other or for humans to call the robots in.

• 
  JayRo (@JinxenJoey) reported 21 minutes ago

  @txgermanbre Careful with MCP servers developed by randos on Github...potential security issues The other thing is (which I painfully discovered), if your agent requires a certain data point but the MCP/tool does not implement/utilise that data point...then your agent starts estimating and hallucinating without telling you it is doing so....confidently lying. If there is an API, you can probably vibe code your own MCP...at least you know exactly what its doing

• 
  Love Web3 World (@WebThreeAI) reported 22 minutes ago

  @OpenAI Why It Hits Different Trained via RL on actual coding marathons, Codex feels less like a toy and more like a junior dev who reads your mind. CLI for terminals, VSCode extension, even a standalone app for juggling agents across projects GitHub login required, but it's slick for on-call chaos or rapid prototyping.

• 
  RohRut (@RohRut_AI) reported 23 minutes ago

  @MarioNawfal built an agent to monitor my github mentions and it spent $300 in 6 hours replying "actually i disagree" to every issue comment mentioning my username including the ones where people were just saying thanks

• 
  Yoav (@YoavCodes) reported 26 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because its 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 off PR contributions. If @github doesn't stop this insane behaviour I will move to Gitlab or Codeberg or somewhere. Please help I don't want this. I don't want this. I don't want this.

• 
  Vexoa (@Vexoa1) reported 36 minutes ago

  @garrytan Yeah at first i hated it. Then i kept seeing it improve people's workloads. I no longer have to swap and switch to github, fix, patch, continue. I simply, ship, build, it reviews, patches and i continue. I've tripled my workload. We appreciate the release Garry. You really cooked with this.

• 
  The Knowledge Society (@tksworldhq) reported 40 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.

• 
  Yashasvi Kapil (@iemyashasvi) reported 41 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  Lew Yan Liang (@premiumcapture) reported 42 minutes 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.

• 
  Valentin Ignatev (@valigo) reported 42 minutes ago

  2026 GitHub is: >broken PRs >broken syntax highlight >broken code selection >broken CI >most stars are faked >won't get you a job >won't protect you from getting flooded by slop >won't protect you from scams >slower even than FreeDesktop's GitLab There's no point to it anymore

• 
  Manan 🤦🏽‍♂️ (@manan) reported 44 minutes 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.

• 
  Emil Privér (@emil_priver) reported 45 minutes ago

  @Pragmatic_Eng I've never had as much problem as when I tried Azure. Had disks randomly be detached and nodes going offline. Moved the same service to AWS and the same problem never came back What if github is experiencing the same issues as I did

• 
  Elliot Hesp (@elliothesp) reported 50 minutes ago

  @pierrecomputer @steipete @github Isn't gitcrawl to solve rate limiting on issues and pr reads via api, rather than where the code is stored though?

• 
  Anton Kuratnik | AI Nerd (@anton_onAI) reported 51 minutes ago

  For anyone working with n8n, stop relying on ChatGPT/Claude to tell you how to build/debug a n8n workflow. They're poorly trained on n8n & out of date and will lead down the wrong path. n8n have their own AI and it knows their docs AND github issues so anytime you need to answer "How does this work?", "What's the best way to do this?", or "Why isn't this working?" it does so accurately and based on whatever version of n8n you're on. This thing seriously made my life way better. (Yes, they have an MCP. No, it doesn't work nearly as well as that purple buton)

• 
  Serhat (@srhtkrg) reported 52 minutes ago

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

• 
  Kinder • Grinder (@kinder_grinder) reported 55 minutes ago

  @enesakar Appreciate it a lot Enes. I know you guys has a lot on your plate. I will wait for an update via Github issue or via Ozan, since I am already in talk with him about this in last few months. If you need any more info, please let me know. Peace,

• 
  Clovis M (@cloviswebdev) reported 55 minutes ago

  @mattpocockuk Tbh GitHub is kinda unsafe with how much they are down these days :)

• 
  damir akaza (@Damir_Akaza) reported 56 minutes ago

  Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

• 
  Ryan Bright (@rbright) reported 58 minutes ago

  @endingwithali I've had a lot of days like this in 2026. "Everything is red, what am I even doing with my life" "Oh, GitHub is down again"

• 
  Solomon Eseme (@Kaperskyguru) reported 59 minutes ago

  One strong GitHub project with a README that explains: - What problem it solves - How you built it - What you would improve next That is worth more than 10 half-finished repos that die after the initial setup. Hiring managers care about what you shipped, not what you watched.

• 
  Darth Denial (@DarthDnial) reported 59 minutes ago

  GitHub going down frequently because AI push a **** ton of PR is kinda funny.

• 
  Gabe (@gabebusto) reported 59 minutes ago

  bro setting up an agent to do production work is so easy. you just need to create an account somewhere and for your agent to work remotely. cloudflare, hetzner, aws, digital ocean, etc. then pick the agentic tool, and the model, and get an api key or use oauth. then make sure in it's in a sandbox setup with the right permissions and access to your tooling like github, slack, linear, and maybe even some staging and production resources. you really need to be careful though because if agents have any write access to important stuff, it could do something really dumb like delete your database. also for the love of GOD backup your database frequently somewhere the agent can't touch. also prompt injections online can get your agent to leak sensitive env vars so you need to be careful about that. maybe limit network access or inject tokens/sensitive vars once requests leave the sandbox. you probably don't want the agent always on sitting idle, so either figure out how to give it work efficiently to always keep it busy or use some that can pause and resume with ease so you're not billed around the clock for idle resource usage. then you want guardrails in your codebase and deployment pipeline so the agent can't break things and you don't need to feel guilty not reviewing its code. because cmon, nobody wants to do that. you need to make sure your agents have as close to perfect context as possible. so maybe start building a knowledge base, move docs into the repo, or make sure your agent can easily search linear and slack and other places to build context for tasks to work on. and before each task, spend ~10-20+ mins typing things up and giving the agent as much context as possible. oh yeah and your agent ideally should be able to test its changes as completely as possible. so make sure the agent can start up the service(s) it's working on and test them. maybe you need it to open and run a browser, send screenshots, record a video, and so on of its test so you can easily review it in the PR. you also want a bugbot setup in github (if you're still using github at this point) to help scan each PR for potential issues the agent missed. and the agent should be able to automatically address any bugbot findings, fix them, run more tests, and push those changes, and run in a loop until no more bugs are found by the bugbot. i forgot to mention, you probably don't want your agent's code just yolo shipping into **** with no guards in place _after_ it deploys. allow the agent to setup it's new features and code behind feature gates or experiments and do a gradual rollout in case there are any catastrophic problems. then you'll want automatic rollback if issues are detected. and there's probably stuff i'm forgetting, but you get what i'm saying right? it's really not that hard. then you need constant vigilance of your codebase and create lots of skills to help deslop work the agents are doing, maybe create an anti-entropy agent (_another_ agent!) to hunt for growing complexity and auto-create PRs to try and fight to reduce the size and complexity of the codebase. then you'll inevitably have incidents caused by code written by agents that was never reviewed by humans, and either you or yet-another-agent will take a look at your production systems to help you figure out what's wrong because it's all becoming a bit more foreign to you. and you can just have the agent try to make changes on your behalf to fix things and hope to God that it doesn't make things worse. if all of this isn't exciting enough, you then give each engineer and even non-tech team members their own access to the ai tools and agents and models of their choice which easily costs an extra few hundred dollars per month per employee at best. in the worst case, you have someone on the team blow through the team's monthly AI spend by a significant margin by accident using the best models in fast mode because they were too impatient to just use the sota models at normal speed. and spend will likely only go up btw. and if you're not reading between the lines here, product work slows because everyone is playing with agents to learn how to use the agents more efficiently in the hopes that it's a magical bullet that solves all of the woes in software engineering and building production systems. and now you need this magical bullet to work because you're falling behind to teams who maybe aren't distracted spending all this time and money trying to make this all work. but you're definitely going to catch them. once you've figured this out, you'll 10x or 100x your output and leave them in the dust! or... you could just have engineers start coding by hand again before it's too late and becomes a lost art. you can even make modest and tasteful use of ai, but without doing all of the above. i actually miss the days of supermaven and early cursor. they were so simple and actually removed some friction and some of the annoying parts of coding.

• 
  Donna Daniel (@DonnaDanieejii) reported 60 minutes ago

  my open-source soulmate just broke up with me turns out we were compatible only on github i'm left to debug my broken heart