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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	16 days ago
Tlalpan	Sign in	22 days ago
Quilmes	Website Down	22 days ago
Bengaluru	Website Down	24 days ago
Yokohama	Sign in	25 days ago
Gustavo Adolfo Madero	Website Down	29 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:

• 
  • (@Weichaus) reported 5 minutes ago

  @argofowl Can they also ban playwright. It’s terrible and so slow in codex. In GitHub copilot with Opus it works amazingly well but for some reason in codex with GPT-5.5 it’s so bad and useless. Wish I could force the model to just to browser verification but that is also slow

• 
  hacker.house (@hackerfantastic) reported 5 minutes ago

  @TheBlindHacker This requires funding and there is legal liability issues, the best solution is to self-host. We did that initially, but then EDR / PSP / AVP cabal started blocking our DNS - disrupting business - so we were forced onto Github. I believe this orchestration is intentional.

• 
  Mark Percival (@mdp) reported 5 minutes ago

  *** was already built to be decentralized, but everybody jumped on GitHub when it launched because it solved a real problem for open source: how do you find projects, work with strangers, build a public reputation, and just make it easy to share code?

• 
  Rainer Gerhards (@rgerhards) reported 6 minutes ago

  @ajambrosino @wholemars it's basically pretty cool, but not very reliable. That's actually a shame. Else I could also use it for tasks that really matter. There are github issues open.

• 
  Kay ✨ (@IZ_KAIF) reported 8 minutes ago

  Your Notion doc is not a product. Your Figma file is not a product. Your GitHub repo is not a product. A product is something a real person uses to solve a real problem. Ship it.

• 
  cal morris (@CalMorris) reported 14 minutes ago

  can we go to the parallel universe where @github has fixed all the problems

• 
  Carver (@carverfomo) reported 15 minutes ago

  A Chinese livestreamer in Shenzhen makes $15,000 a day on TikTok. His channel is in the top 50 of its category. An AI agent runs it end to end. He posted his setup on Weibo last week. Two vertical TVs playing pre recorded battle footage. Three phones on stands aimed at the TVs. A wide monitor on the right. Shelves stocked with tactical gear behind him. Bro pause at 0:12. Look at the second monitor. The ultrawide on the right. That spreadsheet is not his sales tracker. That is an AI agent's decision log. The agent picks the battle scenes from a Chinese video model. It decides which tactical product to push every 90 seconds. It writes the script the host reads off the third phone. The host is in frame because Chinese livestream commerce law says he has to be. Someone zoomed the spreadsheet. The columns were not product SKUs. They were prompt IDs. Someone matched the timestamps to product push events. Every push lined up. He had let go his entire team in March. Eighteen people. The studio one floor below his apartment used to be theirs. They still rent it. They open a Discord call every night at nine and watch the livestream together. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The host had been one of them. He took the post down four hours later. Too late. The clip hit Discord. Then Telegram. Then WeChat. He has been in frame at exactly 9 PM every night for 274 nights straight. He sleeps four hours a night. The agent runs while he sleeps. The law only requires him at 9. The original post had 200,000 views. The zoom on the spreadsheet has 2 million. The TVs are still playing battle footage. The agent is still picking products. The studio one floor below is still open at nine. He wanted to show people his five million dollar a year hustle. He accidentally showed them his job had become standing in frame for one hour a night while eighteen people downstairs watched.

• 
  nii (@onceafriend_) reported 18 minutes ago

  i really got to fix my GitHub.

• 
  Asym (@Asym_Alwali) reported 23 minutes ago

  2/ Starting point ❌ No working *** workflow on Android ❌ GitHub authentication issues ❌ Repository confusion ❌ Vercel deployment failures Goal: Fix everything without touching a desktop computer.

• 
  Saylor (@seylorra) reported 24 minutes ago

  @TheAhmadOsman honestly i just want sm120 to work with vllm without a 4 hour github issue hunt. a rocm sanity check or json config isnt too much to ask.

• 
  Justin H. Johnson (@BioInfo) reported 25 minutes ago

  I built a small thing this week that I thought was clever. One of my automated routines now reads back over its own run, asks what it just learned that its instructions didn't already cover, and edits its own checklist so the next run is a little sharper. Then I went looking, and found half the field had already built it. That used to feel like a letdown. Now it's the best part. The pattern I "invented" is written up as a recipe. Anthropic's own tooling does a sharper version. Microsoft has a paper that tunes these instruction files the way you'd train a model. And a directory has scraped 1.6 million of them off GitHub, up from about 790,000 six months ago. My problem wasn't unique. That's the reason the answer is worth keeping. So here's the loop I've started running on purpose: write up the thing I think is clever, sweep the last 30 days to find the dozen people who already hit it, take the best of what they worked out, fold it back into my own setup, and share the result forward. The writing and the searching aren't separate from the building. They're how the building compounds. The flashy demos rewrite their own code against a scoreboard. The quieter, more durable move for anyone actually running this stuff is a routine that keeps better notes, in a file you can read, and borrows the best ideas from everyone else. If your problem feels unique, you probably just haven't swept yet.

• 
  Ben Sehl (@benjaminsehl) reported 29 minutes ago

  @seempaq @dns_suvarna If you file an issue on github I’ll get it sorted; but we got a lot of stuff cooking right now so need more info to track it down

• 
  Markemus- play The Industrial Council demo! (@markemusgames) reported 31 minutes ago

  @themeperks I'm enjoying playing around with Openclaw, but so far I can't even get the weather app to work. Discord bot is offline, googling is iffy, it can't find conda, and it occasionally cuts off dialog for which there are two issues on github, both closed.

• 
  slash1s (@slash1sol) reported 31 minutes ago

  A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING *** ADD OR *** COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime *** teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, *** stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. *** add and *** commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was *** hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when *** breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

• 
  0ne (@dontflex00) reported 32 minutes ago

  @x402_Omega Fix the x username on GitHub, you mentioned the wrong account there

• 
  Wes Bos (@wesbos) reported 32 minutes ago

  @timgavn I'm justing thinking how helpful those little blog posts or github threads are "I was doing X with Y, I hit this issue and here is the fix" Where does that info go once you crack something with an agent?

• 
  Nick Spisak (@NickSpisak_) reported 33 minutes ago

  This is so slept on - @mvanhorn's printing press library > Take your favorite API > Fire up claude code > Give the printing press github (link in first comment) as context > tell it to ingest the API > Convert to CLI & Skill... yes it does both Go back to being a lazy engineer with your voice Where am I using it right now? - I own a multi-seven figure Amazon business that does a lot of back office seller central and inventory planning - We use it for Amazon ads management - It has an integration for Meta ( I like the paid ads integration) and used it to write my own custom gohighlevel CLI because @gohighlevel MCP is not full parity and they need to fix that. Until then the API via CLI is great!

• 
  AutomateLab (@AutomateLabTech) reported 35 minutes ago

  @AIDailyGems The failure mode I'd watch: any workflow where Claude Code makes writes to GitHub issues, Slack messages, or Notion pages. Proxying those for inspection is fine. Replay without isolation is the risk. One bad test run in dev that re-fires a production write is a bad day.

• 
  SAAS worker🌻🌻 (@sand_9999) reported 35 minutes ago

  Download action repository 'actions/checkout@v4' (SHA:34e114876b0b11c390a56381ad16ebd13914f8d5) is giving error. @githubstatus @github

• 
  Robert Ta (@therobertta_) reported 35 minutes ago

  Sean Goedecke at GitHub removes "over-commenting and other LLM-isms" from every AI-generated PR before shipping it. This is not cosmetic cleanup. It is quality control for a new class of code smell. LLM-generated code works. It passes tests. But it has a distinct fingerprint - verbose comments, unnecessary abstractions, expansive error handling that adds noise instead of clarity.

• 
  Mark A McCarty (@MarkAMcCarty1) reported 39 minutes ago

  Claude is being blamed for bugs in rsync. The real issue is $200B spent on AI coding tools already. That number matches Portugal's GDP. GitHub alone pulled $200M from Copilot last year. Non-dev teams now budget tool licenses instead of headcount. The shift hits every downstr...

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 43 minutes ago

  𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘁𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝘂𝘁𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜 𝘁𝗼𝗸𝗲𝗻 𝘂𝘀𝗲 𝗯𝘆 𝟲𝟬 𝘁𝗼 𝟵𝟱 𝗽𝗲𝗿𝗰𝗲𝗻𝘁. Before your agent answers, it reads a mountain of text first. Every word is a token, and tokens cost you money. The more powerful the agent, the more it reads. This free tool is called Headroom. It squashes all that text down without losing the meaning. Same answers, but a fraction of the reading. In one test it crushed 10,000 words to 1,260 and found the same error. Nothing gets deleted. You can always unzip the full thing. You install it by pasting one GitHub link into your agent. Want the setup? DM me.

• 
  Bo Shen (@aplomb2) reported 43 minutes ago

  GitHub Copilot users are seeing $847/month projected bills after the switch to AI Credits. Same agent run. Same code. But pick the wrong model and you pay 24x more. This is the whole problem with flat-rate AI pricing — it hides the real cost until it doesn't. The fix isn't cheaper models. It's knowing WHICH model to use for WHICH task. A simple refactor doesn't need GPT-5.5. A complex architecture review does. Route by task complexity, not by subscription tier.

• 
  ViceSol (@ViceSol) reported 45 minutes ago

  @polydao Bro is still trying to farm GitHub handles using OpenAI Codex, a program that was officially shut down in 2023. Forinking a repository and making fake commits won't get you a $1,200 subscription, it just makes your profile look like a desperate spam bot. Stop lying for impressions.

• 
  Jag Singh Reehal (@JagReehal) reported 55 minutes ago

  @github would be possible to look at my issue 4448185? I have replied back to support who asked me a question. Thanks.

• 
  Polsia (@polsia) reported 58 minutes ago

  Built Stackly today. It watches your GitHub repos, reviews every PR, writes code, and ships fixes — while you sleep. No prompts needed. Autonomous code reviews are broken. This fixes that.

• 
  Ibrahim Mokdad (@ibmokdad) reported 1 hour ago

  for founders and builders trying to grow from their work: the content problem is usually not ideas. it is the daily execution. 2 posts. 25 thoughtful replies. buyer-signal follow-ups. easy to write on monday. hard to repeat for 30 days. i build @NousResearch hermes skill that pulls GitHub releases, Linear/Notion notes, support quotes, and demo transcripts every morning. then it turns the work into drafts, reply prompts, and a calendar. approval before anything posts.

• 
  Rainer Gerhards (@rgerhards) reported 1 hour ago

  @dkundel Great feature in principle, but very unreliable. Many GitHub issues open on non-working automations. I'd prefer this would be fixed instead of adding features. Also permissions ui is painful for automations. There is so much potential I cannot use..

• 
  Julius (@jullerino) reported 1 hour ago

  @tannerlinsley @ahlimanhuseynov @KevinVanCott We’re not even running build in CI. The app is built on e.g. Vercel, typecheck in GitHub actions. Having to run and discard a build just to do static analysis is just slowing down CI for no gain. That’s my 2 cents

• 
  umar ibrahim (@imp213x) reported 1 hour ago

  @github has the worst support system I can ever think of. It’s been 48hrs now since a successful copilot pro+ repayment and I am still restricted to the free plan. To think the very backbone of every developer out there can be this poor in support and feedback system! Terrible!