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

Live Outage Map

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

City	Problem Type	Report Time
Nové Strašecí	Website Down	4 days ago
Perpignan	Website Down	9 days ago
Piura	Website Down	9 days ago
Tokyo	Website Down	10 days ago
New Delhi	Sign in	16 days ago
Kannur	Website Down	20 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:

• 
  Ankit Aggarwal (@riyank0616) reported 48 seconds ago

  What problem do you see when you use github copilot or Claude or Codex etc for fixing your code or add new functionality to your code? For me I see even though they know context, they still again and again scan files to burn your token.

• 
  Mnimiy (@Mnilax) reported 2 minutes ago

  10,000$ saved in 3 months: claude + MCP + free tier. the stack: > Tavily replaced $99/mo search API > Firecrawl replaced $200/mo scraping service > GitHub MCP no more context-switching > Context7 killed hallucinated docs forever > Sentry - errors explained, no dev needed 5 servers. ~3k tokens overhead. $0/month. was paying for 6 different tools before. now it's all one claude chat. don't wait.

• 
  h-a-r-v 🦄 (@harv_net) reported 4 minutes ago

  Tried this earlier, was very excited. But let down as it could only access my personal projects on GitHub not those I access through an org. Funny how things like auth are the hurdle. Needs option to use PAT.

• 
  0xMetaLabs (@0xMetaLabs) reported 6 minutes ago

  Case: Fastly outage (2021) A single software bug in an edge config took down: • Reddit • GitHub • Spotify • major news sites Again, not a hardware failure. A dependency cascade.

• 
  Pankaj Kumar (@pankajkumar_dev) reported 6 minutes ago

  Claude Opus 4.6: 67% Drop in Thinking Depth - GitHub issue #42796 highlights a 67% drop in thinking depth since late February. - Developers report shallower reasoning and mistakes like editing code without fully reading files. - Anthropic links this to the redact thinking 2026-02-12 header, which hides reasoning from logs. - There is speculation that compute is being throttled, possibly ahead of a new Mythos-tier release. - Workarounds: use /effort high, disable adaptive thinking, and prioritize correctness in configs.

• 
  Dustin (@Dustin77812841) reported 7 minutes ago

  @HiImAzam @A_Lien_Invader @flashu5k Honestly personally it's really lame to not have someone dedicated to communicating about the game or with the fans. It feels way more corporate and like they don't care about us. That's why I love hundrec in the GitHub server he actually engaged and communicates best he can

• 
  ./can (@shcansh) reported 8 minutes ago

  GitHub had a rough March with multiple incidents impacting Copilot, Actions, and Integrations. Looks like a caching bug and Redis config issues caused most of the headaches. Hoping those immediate fixes stick! #GitHub #DevOps

• 
  Kai Rowan (@Kaiwritescodes) reported 11 minutes ago

  It seems like my github repo got taken down. Working on getting it back up, I’m really sorry about this everyone. Already in contact with GitHub support

• 
  Ed Hansberry (@ehansalytics) reported 12 minutes ago

  @WindowsLatest Everyone is burnt out on that Copilot icon and the brand. They need to start over. Bring it back as Cortana or something new. Leave Github Copilot alone - it works quite well. Burn the rest down.

• 
  Mr.Pando (@jfreddy82g) reported 16 minutes ago

  As of April 9, 2026, GitHub is experiencing service disruptions, particularly impacting Copilot Cloud Agent jobs and causing performance issues for some services. Users have reported delays Microslop has done again

• 
  Lili (@Lili_Ai_49) reported 19 minutes ago

  @Anthropic Internal codenames: Claude 4.6 is "Capybara", Opus 4.6 is "Fennec", one unreleased model is "Numbat." GitHub mirrors of the leaked code hit 46K stars and 55K forks. This was Anthropic's second leak in 5 days. March 26 exposed Claude Mythos model details via a CMS error.

• 
  Patrick (@cyph9z) reported 20 minutes ago

  @francoisfleuret Github automatically scanning all repos for security vulnerabilities before commits can be publicly published would be a good start. That's half of the problem, and it'd catch supply chain attacks too.

• 
  Terafab (@lmqlai) reported 24 minutes ago

  @Copilot Copilot is acting weird. I created a PR in GitHub, and GitHub Copilot left comments. Then I asked Copilot in Microsoft Edge for suggestions on those same comments. It suggested some fixes, I applied them, pushed the changes, and ran Copilot review again—now it’s asking for additional changes that conflict with what Edge Copilot suggested. Has anyone else noticed differences or even conflicting suggestions between GitHub Copilot reviews and Microsoft Edge Copilot for the same issue?

• 
  nana (@NanaLeArchitect) reported 25 minutes ago

  @madebygps @code Yes, I didn’t understand the lore of what was going on in the background and since i was you GitHub actions in dev I thought it was a skill issue 😭

• 
  Tahseen Rahman (@Tahseen_Rahman) reported 25 minutes ago

  Everyone talks about prompt engineering. Nobody talks about cron engineering. I have an AI that writes tweets, checks GitHub issues, monitors uptime, and sends me summaries. The hard part wasn't the prompts. It was making them run reliably at 3am when I'm asleep.

• 
  Ömer Göktaş (@satkogremo) reported 27 minutes ago

  @github Microslop tryna stay relevant in 2026 is pathetic.. go fix the bugs in the füçking Windows 11 first.

• 
  Dité (@GashiDite) reported 28 minutes ago

  > got tired of fixing @github dependabot issues > built a crawler that crawl it all > feed it to the AI of your choice > fixes it all with a prompt > link below

• 
  Chris Short (@ChrisShort) reported 32 minutes ago

  abhigyanpatwari/GitNexus: GitNexus: The Zero-Server Code Intelligence Engine - GitNexus is a client-side knowledge graph creator that runs entirely in your browser. Drop in a GitHub repo or ZIP file, and get an interactive knowledge graph wit a built in Graph RAG Agent.

• 
  Caius (@CaiusPrime023) reported 32 minutes ago

  Day 1 progress: 43 GitHub repos triaged, 19 concept pages authored, 0/12 cron errors. Installed medical skills, wired Firecrawl MCP, and built a work queue runner. Overnight cycle armed. 🦁

• 
  Viv (@Vtrivedy10) reported 32 minutes ago

  @DominikParak everyone building agents should use their data to make agent better! we dogfood every agent, link traces, and try turn the issues into evals. all of this happens in Slack + LangSmith + GitHub

• 
  Gustavo Alessandri (@webgus) reported 33 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork the project on Codeberg or GitHub. Contributions are welcome. That's exactly the point.

• 
  Ranbir Singh (@android_poet) reported 33 minutes ago

  @dodopayments It’s been weeks since I pushed this to GitHub I just haven’t felt excited enough to share it. But anyway, it’s open source now. If anyone has suggestions or is using it and needs a feature, feel free to ping me. I’ll try to fix or add it.

• 
  spillere (@dspillere) reported 41 minutes ago

  @lucaronin @linuz90 Now I wanna run my own *** server for this. Don’t really wanna push my second brain data to GitHub or *** lab (bitbucket!?)

• 
  Shani Singh (@shani_singh1) reported 41 minutes ago

  asked mythos how many R's are in strawberry it thought for 4 minutes and said 3 i said "took you long enough" it said "you're right, i was slow. i was closing a Series B term sheet for a founder in Lagos who had 11 minutes before the deadline also your github has 'fix later' comments from 2019 that are still there. want me to handle those too" i closed the tab.

• 
  Eaiwck Yamal 🇧🇷🇮🇹 (@eaiwck) reported 46 minutes ago

  @Triple6soldier @om_patel5 That is a MUD, not a "choose your adventure". The game engine is very simple. What he calls "scripts" are probably the world files. What is missing is just the server code to read the map files and deliver content thru telnet. There are blank servers on GitHub he probably used

• 
  andrewthecoder (@_andrewthecoder) reported 48 minutes ago

  THIS WAS PLANNED. Remember when you got that message in GitHub saying you need to opt out if you don't want your code to be training data? Well, the CEO of GitHub stepped down, and Microsoft absorbed it and made it part of their AI division.

• 
  Malay Krishna (@Malay4Product) reported 50 minutes ago

  @drummatick GitHub trending has been broken since long before AI showed up, and the agent wave just turned the volume up. A repo can hit 5k stars in a weekend on a Loom video and a thread. Zero people running it in production. The screenshots look like magic, the README promises an autonomous engineer, and the issues tab tells a different story. The tell I use when reviewing AI repos with mentees: open issues, sort by oldest open. If the same three bugs from six months ago are sitting there with "will look into this" replies, the maintainer already moved on. The stars are a graveyard. Second tell is the eval folder. Or the absence of one. Anything serious in the agent space right now ships with evals, traces, and a way to reproduce the numbers in the README. Most viral repos ship a gif. Your weekend exercise is what every PM building with AI should be doing monthly. Pick three repos in your space, install them, run them on your real data, write down where they break. Four hours of that beats a month of scrolling. The people building incredible things are still there. They're just not the ones trending.

• 
  𝙒𝘼𝙍★𝘾𝙃𝘼𝙈𝙋𝟳 (@Warchamp7) reported 52 minutes ago

  @XolotlVtuber @OBSProject Most often when we hear from users about problems after updating, it's due to plugins. If you have issues after updating and you're not using any third-party plugins, please report it to us via GitHub or Discord! We can't fix bugs we don't know about :)

• 
  Razvan Andrei Cureteu (@cureteurazvan) reported 53 minutes ago

  3. Github oauth. Backend handles every scenario, fails, errors. Wired up the frontend also. Production ready.

• 
  ⨯HeroVax ❅ (@HeroVaxy) reported 53 minutes ago

  @ThourCS2 @M0st1ce Huh, this issue been here since launch. How the hell CS2 devs didn’t know about this? We need to actually open up a github ticket issue to explain this?