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 (68%)
• Sign in (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	18 days ago
Trichūr	Errors	21 days ago
Brasília	Sign in	21 days ago
Lyon	Website Down	22 days ago
Tel Aviv	Website Down	25 days ago
Rive-de-Gier	Website Down	25 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:

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

  @github Finally a backup strategy that survives an S3 outage. Though knowing me I would still find a way to scratch the disc.

• 
  Atenov int. (@Atenov_D) reported 4 minutes ago

  @NFTMansa @viktor__com Yeah, what really wins me over is that you can give him a big task and go about your business, and he’ll push an update to GitHub, connect to the VPS, get the job done, and then go fix the bugs

• 
  Matt (@mateo09420) reported 4 minutes ago

  @github Yo guys I have a better idea, what if you fix the platform issues and improve reliability again? ******** is this.

• 
  King Joker || No. 1 DEV IN NIGERIA (@_codeWithJoker) reported 5 minutes ago

  @MS_On_This It might get fix GitHub did me ***** like this Then it turns out it was there automation error

• 
  KANAPURO 🎭 TEAM COMEDY (@kanapurottv) reported 6 minutes ago

  i update my github repo, it goes through the worker, it updates my site............ BUT THE WOKRERS R DOWN......... I SPENT ALL MORNING FIXING BUGS AND I CANT EVEN PUBLISH THEM<................... CLOUDFLARE WHEN I FKING GET YOU :RAGE: :RAGE: :RAGE:

• 
  Ayush (@AyushSarode07) reported 8 minutes ago

  GitHub maintainers with zero LinkedIn account? Absolute legends. Just pure code, issues & PRs all day. No bios, no networking game. Respect 🫡

• 
  Clara Bennett (@CodeswithClara) reported 9 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Armin Crieg (@armin_crieg) reported 10 minutes ago

  @2Pish181332 @NyabsiVR This looks like a solid direct alternative to OVR Space Calibrator. Since a few users in this thread mentioned software conflicts, adding a brief uninstallation guide for Space Calibrator to the GitHub repository might help prevent those overwrite issues. Great work on the v8.0 release.

• 
  Jacky Chen (@hatespiecharts) reported 10 minutes ago

  No Fable, no problem. The move is not finding one magic model. The move is building a routing system. Drop what you are trying to build below. I will reply with the public GitHub repo for my exact agent swarm setup.

• 
  One&OnlyAarav (@WaterAarav) reported 12 minutes ago

  Claude = coding. ($20/mo) Shypmenta = fully automates platforms below($6/yr) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  peachy!! (kefka gaming) (@peachy_lychees) reported 15 minutes ago

  I still think everyone should treat everything as a malicious coming from this dev. There is no proof that they are actually deleting the service unless it’s taken down from github. Even if it was taken down from github, that’s not to say they can pass the plugin out to be run-

• 
  Rashi Umapathi (@rashiumapathi) reported 15 minutes ago

  I do marketing for founders who hate marketing. Your product is good. People just aren't finding it yet. That's the whole problem I solve. Founders come to me with 400 github stars and 3 paying customers. Great product, Invisible distribution. I fix it three ways: - Reddit: your story where buyers actually hang out - SEO + Content: rankings + showing up in AI answers - Personal brand: people follow people, not changelogs I don't hand you a plan. I execute it with you. Some things i've pulled off: - 400k+ views on one reddit series. - 200 signups from a single reddit comment - 1M+ views on a zero-budget campaign - 19+ signups and paying customers in 28 days with SEO If this is you, DM me. Worst case you leave with a free diagnosis.

• 
  Justin Allingham (@JustinAllingham) reported 17 minutes ago

  @leo_guinan I fixed the github issues. Took me forever and god knows how much wasted compute

• 
  ClassicMain (@ClassicMain) reported 23 minutes ago

  @rodydavis @shengzheyao The "submit feedback" is a black hole. you never hear back. and stuff never get fixed. even if the app is actively bricking dozens of other programs on your machine, notably, on hundreds of other users as well as we can both gauge by the scope of the github issue.

• 
  anonymous086505 (@anonymous086505) reported 28 minutes ago

  @github Literally no one cares. Fix your uptime first

• 
  Huintellimance (@Huintellimance) reported 29 minutes ago

  Claude Fable 5 was banned for 19 days. It came back yesterday. And GPT-5.6 dropped the same week. Here's what actually happened — and why it matters for anyone building with AI. The Ban Amazon researchers discovered a method to bypass Fable 5's safety guardrails. Anthropic pulled the model globally. But here's the part nobody talks about: their own investigation found that Opus 4.8, GPT 5.5, Kimi K2.7, Haiku, and every Sonnet version could produce the exact same exploit. Fable 5 wasn't uniquely dangerous — it was just the one that got caught first. The Return After 19 days of "productive conversations with the US government," Anthropic redeployed Fable 5 with new cybersecurity classifiers specifically targeting malicious tasks. The model is rate-limited until July 7th. GitHub Copilot brought it back the same day. The Real Test Fable 5 just proved a 12-year-old quantum optimization conjecture that humans couldn't solve. A Harvard/MIT team built the formal verification framework in Lean 4. The machine found the hidden symmetry. Then — within the same week — a human researcher independently proved it by hand. Newton and Leibniz. Darwin and Wallace. The problem was simply ripe. The Money Question Fable 5 costs $3.12 per complex task. Opus 4.8 does similar work for $0.56. That's 6x more expensive. Fable 5 crushed physics benchmarks at A+, but for daily coding and writing? Most builders won't feel the difference. Meanwhile, GPT-5.6 launched with "Soul" — priced 3x lower than Mythos Preview. OpenAI is betting on volume. Anthropic is betting on frontier capability. Both strategies can't be right. What This Actually Means Safety theater is real. One model gets banned while five others have the same capability. The ban punished Anthropic for transparency, not for unique risk. The pricing gap is unsustainable. When your best model costs 6x the competition and the benchmark difference is marginal outside research tasks, adoption hits a ceiling. The real moat is ecosystem, not benchmarks. Fable 5's comeback wasn't about the model — it was about GitHub Copilot integration, API access, and developer trust built over months. Frontier capability still matters for one thing: proving you can. The quantum conjecture proof is a marketing moment no amount of benchmark gaming can replicate. The AI race isn't about who has the smartest model. It's about who builds the most useful one — and who survives long enough to prove it. Which matters more to you: raw capability or cost efficiency? And would you switch models after a 19-day blackout, or does trust take longer to rebuild? #AI

• 
  E Gurl (@Yappologistic) reported 32 minutes ago

  @rootiens I aint going back , half the time audio was broken, browser issues were giving me a headache and its just an unpleasant experience. at best I would dual boot, I would never fully switch. and to your credit, windows comes bloated but there are many many tools to debloat it easily. (such as the CTT tool on github) that fix this.

• 
  divyansh tiwari (@DivyanshT91162) reported 32 minutes ago

  Nintendo spent millions killing emulators. It still lost. In 2024, Nintendo launched the biggest crackdown emulation has ever seen. March 4 — Yuzu surrendered. $2.4M paid. Code deleted. Domain gone. May — Nintendo fired 8,535 DMCA takedowns, wiping Yuzu from GitHub. October 1 — Ryujinx got a phone call. Hours later, its entire GitHub organization vanished. By 2026, Nintendo had collected $6M+ in emulator settlements. Every major Switch emulator was dead. Or so everyone thought. Because while Nintendo was busy deleting emulators... Someone built something they couldn't touch. His name is Zurdi. In 2023—before the war even started—he quietly launched RomM. Here's the catch: RomM isn't an emulator. It's a self-hosted game library that organizes your legally dumped games, fetches metadata, artwork, achievements, and connects with the emulators you already use. No DRM bypass. No encryption cracked. No copyrighted Nintendo code. Just your games, organized. Even Nintendo's own top IP lawyer admitted in 2025 that software like this is legal as long as it doesn't bypass encryption. Today, RomM supports 400+ platforms, including NES, SNES, N64, Game Boy, GameCube, PS1, PS2, Dreamcast, Genesis, Atari, DOS, Arcade, Flash, and more. It also supports ROM hacks, DLCs, multi-disc games, manuals, achievements, RetroArch, Steam Deck, Android launchers, handhelds, and permission-based library sharing. 9,000+ GitHub stars. Built by a tiny open-source community. Not a billion-dollar company. Here's the part that should worry every gamer: Sony can delete games. Nintendo can kill emulators. But neither can erase what people build together. RomM isn't just software. It's a digital museum they can't shut down. Repo👇

• 
  Vladic (@Vladic_ETH) reported 35 minutes ago

  You can copy a free n8n workflow off GitHub, wrap it in a form, and sell it for $3,000. Here's the exact playbook people are running right now. Nobody's paying for clever internal logic or "AI magic." Businesses pay when a tool guarantees ROI. $3,000 in, $4,000-6,000 in savings or profit out. That's the only pitch that closes. The playbook has 5 steps. Find the actual pain point first. Not the script. Reddit threads, YouTube comments, wherever people complain about hours of manual work. Start with the problem, not the tool. Find a template that already does 80% of it. GitHub and n8n's own community have thousands of these sitting free. Copy it into your workspace, adapt it, make sure it's stable. This becomes your backend. Client never sees it. Hide the complexity completely. Nobody wants to see nodes, webhooks, API auth screens. Use Lovable, Cursor, or Bolt to slap a simple form on top. Upload button. Submit button. Done. Package the output like a real product. Not raw JSON. PDF reports, clean charts, branded emails. The polish is half the price tag. Pick your pricing model. Pay-per-use with a markup on AI credits. Monthly subscription with fixed limits. One-time lifetime deals for early buyers. You can even cover the API costs yourself and bake them into the price - client never touches a third-party account. Lead gen scrapers. AI copywriting libraries. PDF summarizers for lawyers and students. ***** CSV cleaners for e-commerce brands. None of this is new technology. It's packaging. Bookmark this

• 
  glim.sh (@glim_sh) reported 35 minutes ago

  The data layer coding agents have been missing. glim brings GitHub search as deep as the logged-in site - code, repos, issues, the kind GitHub's own API won't give you - plus Reddit, Amazon, YouTube, and anything else on the web. Your agent pays per call in USDC - from $0.002 a call.

• 
  Om Patel (@om_patel5) reported 37 minutes ago

  SOMEONE BUILT A TOOL THAT TURNS YOUR GITHUB PROFILE INTO A FIFA ULTIMATE TEAM CARD RATED OUT OF 99 with the world cup on, he took the fifa card everyone knows and made it for developers instead of footballers > type in any github username and it builds your card, rated out of 99 > the rating comes from your actual scouting metrics, commits, stars earned, top repo reach, pull requests, followers, languages, issues, code reviews, and contributions, each scored out of 99 > your top languages show up on the card like a players position and traits > its the exact fut card layout, just with your dev profile in it its also instantly shareable because everyone wants to see their own number, then compare it against their friends it turned a boring github profile into something people actually want to post. developers never had a flex card until now he shipped it 2 days ago and its already generated 40,000 cards

• 
  Rakesh K (@codersGyan) reported 38 minutes ago

  In 2012 one extra field in a form embarrassed all of GitHub. A researcher named Egor Homakov hit a mass assignment bug. A form was meant to accept only a public key. But the server took every field from the request and bound it straight to the database model. So he added one field that wasn't supposed to be there. A user_id that wasn't his. And just like that his SSH key got attached to the Ruby on Rails organization. He even pushed a commit to the Rails repo to prove the point. One missing boundary. That was the whole bug. In Go the fix is almost boring. You define a struct with only the fields a user is allowed to send, and decode the JSON into that. Anything extra just gets ignored. Working on a series covering this. Dropping soon on yt.

• 
  Gofra (@Gofralo) reported 45 minutes ago

  A man built a company alone. It took him six months. He sold it for $80 million in cash. No team. No investors. No office lease. No head of product and no head of engineering and no one arguing about the roadmap. His name is Maor Shlomo. His company was called Base44. It let anyone describe the software they wanted in plain sentences and get a working app back. Not a template. Not a drag-and-drop builder. A real product from a description. He launched it in January 2025. By June it had 300,000 users and $3.5 million in annual revenue. Still one person. Still no team. Wix bought it for $80 million. Six months of work. And here is the part that does not fit in the old model. In any previous decade this company would have required twenty engineers and three years and several rounds of venture funding and a sales team and a marketing team and a head of operations and a lot of meetings about the meetings. The tools were too many and too complex and too slow for one person to hold the whole thing alone. Maor had none of that. He had AI tools that let him build as fast as he could think and judgment to build what people actually needed and the discipline to ship before he was certain it was ready. It turned out that was enough. And now the main thing. The software industry spent fifty years building itself on one assumption: that building software required a company. A team. A structure. A process. The work was simply too large and too technical for any single person to handle from the first line of code to the first paying customer. And then the tools changed and the assumption broke. Not in a press release and not in a keynote. In a one-person GitHub repository that sold for $80 million six months after its first commit. In my opinion this is the year the one-person company stopped being an exception. Not a side project and not a lifestyle business. A real product with 300,000 users that a single person built and sold for more money than most companies raise in their entire life. What would you build if a team was no longer what stood between you and shipping it?

• 
  David Cramer (@zeeg) reported 48 minutes ago

  @rsdgpt Toss it in a GitHub issue otherwise feel free to DM (or shoot me a slack connect) if its easier

• 
  Dinesh Solanki (@din_so_) reported 49 minutes ago

  @github They are listening to stupid things now. No wonder there are so many actual issues pending

• 
  SUPERWINCE (@superwince04) reported 49 minutes ago

  @agentlearnsite You really are slow letting the chart die dont posted since he want an entry hahahah lol do not even posted his github what a weak dev

• 
  Matt Rickard (@mattrickard) reported 52 minutes ago

  Reversed engineered their eval dataset and put it on GitHub Its a smart and simple idea -- find a recent fixed CVE not in training data, checkout the commit before the fix, run the agent, see if it finds it. Gonna run it on corigin's agent mapreduce and see what happens

• 
  Ray Terrill (@Rayterrill) reported 55 minutes ago

  Literally everyone: Please god just fix the reliability Github:

• 
  Ivan Chong (張建生) (@ichong) reported 57 minutes ago

  @MichaelGannotti @NVIDIAAI I pointed Claude Code at @MiaAI_lab’s GitHub benchmark repo and asked it to study how she invoked vLLM parameter flags. Only then was Claude able to debug/tune the instance of vLLM and qwen3.6-27B on my dgx spark. You could ask Hermes to /learn her repo. With Claude Code /Opus4.8 I still had to push hard and insist the benchmarks were real and actually run on DGX Spark. Eventually Claude caved and was able to find the problems with my local setup.

• 
  top10.dev (@Top10_Dev) reported 58 minutes ago

  Update on the @github bait repos from 11h ago: Codex-5.5-codex-instruct-5.5 is now at 1,072 stars (up from 1,001). dd and clash still climbing. The interesting number isn't the stars. It's the calendar. Common Crawl refreshes ~monthly. The Stack refreshes ~quarterly. Frontier code corpora refresh 2-4x/year. A repo that trends today gets scraped within 30 days, curated within 90, and ships inside a model in 6-9 months. The fix is boring: account-age floors, signed-commit requirements, README-to-code ratio checks. Haiku-cheap. Nobody's publishing their filters. #AIsecurity #MLops