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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	4 days ago
Quito	Sign in	5 days ago
Junín	Errors	5 days ago
Guadalajara	Errors	5 days ago
Paris	Website Down	5 days ago
Quito	Errors	5 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:

• 
  𝕘 𝕥 𝕨 𝕪 (@Gtwy) reported 5 minutes ago

  @congressdj @bot half of the connectors on grok bot don't work spent two days using it to write it's own software instead of using the connectors then realized i could use it to stand up a better system entirely that runs over grok code that connects to everything with no issue still use grok bot for heavy software development but other than some ssh gets and github i have zero motivation to connect it to anything else now

• 
  Felix (@Reezxy23) reported 7 minutes ago

  There has never been a cheaper time to build. 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

• 
  Baldly Rudy (@baldlyrudy) reported 7 minutes ago

  Nintendo just wiped 401 Switch emulator repositories from GitHub in a single sweep. Seven new DMCA notices targeted: -311 Suyu repositories -Skyline -MonoNX -Multiple Yuzu forks/ports Nintendo argues the emulators circumvent Switch protections by using unauthorized cryptographic keys to decrypt games at runtime. This follows the 8,535 Yuzu-related repositories Nintendo had GitHub remove back in 2024. Nintendo's emulator crackdown clearly isn't slowing down.

• 
  Pascal Bornet (@pascal_bornet) reported 8 minutes ago

  Even fast-food chatbots are preparing for technical interviews. You open a support chat because you want lunch, but somehow the conversation ends with the chatbot solving a Python problem that has nothing to do with burritos. I have to respect the ambition. Pepper is supposed to answer questions about orders, but it is clearly using the job to build experience before applying to a software company. At this rate, the next time your order is late, please be patient because the chatbot may be updating its GitHub portfolio or completing the final round of a coding interview. Which customer-service chatbot secretly has the most promising tech career? #AIHumor #WorkplaceHumor #AgenticAI

• 
  Veli UYSAL (@_VeliUysal) reported 10 minutes ago

  Hey Guys, unfortunately Github Action is down again.

• 
  enp2s3 (@enp2s3) reported 20 minutes ago

  Free is not actually free. Here’s the Brave slop from my perspective. Popups everywhere, useless side features constantly jumping in your face like the browser is trying to force you to use them. When you first install Brave, if all you want is a better browser, you have to turn off dozens of settings and features first. Brave Ads, Brave News, Brave Rewards, yeah, earn rewards, because apparently we’re playing a ******* game here instead of looking for a browser, Brave AI Chat, Brave Talk… It genuinely starts feeling like one of the market's spam-filled products. Anyway, after turning all that crap off and getting through the initial setup chaos, you finally think you can relax. But you can’t. Brave looks good, the UI is solid, almost Opera-like hype, and it comes wrapped in all those big privacy-focused slogans. But after actually using it for a while, the whole thing starts turning into clickbait. A lot of Brave settings are disabled by default or set to ask every time, so on popular websites and across the modern web, instead of making your browser experience easier, it keeps costing you extra time. Still, you don’t quit Brave. You spend months fixing settings site by site, changing permissions, adjusting preferences, until you finally reach the comfortable browser experience you should’ve had from the beginning. Then not even 3 or 4 months later, another surprise. After a few browser version updates, basic usage starts falling apart with lag, freezing, stuttering and random slowdowns, gpu acceleration issues. At that point, the whole Brave experience basically becomes this: 1) Use Brave for a while. Spend a few months improving your settings and site preferences until you finally reach the normal browser experience you were supposed to have in the first place. 2) Just when everything finally starts working properly, one of Brave’s chronic problems randomly shows up. 3) Spend a few weeks researching it on github/reddit, trying fixes, taking backups and repeating the similar solutions until you eventually discover that people have been discussing the exact same problem for years and it is somehow still there. 4) Keep your hopes up, reset the browser, go back to Step 1 and start the whole thing over again. 5) After 1 YEAR, or X YEARS, finally find the courage to get rid of Brave and go back to Safari or Chrome and quietly weep. We basically have the browser version of the operating system irony now. The only difference is that we don’t hear about some brand-new operating system every year, while plenty of companies can build another browser, give it amazing PR and make huge promises about privacy, speed and simplicity. And as usual, we users are left quietly weeping.

• 
  Md. Mazharul Islam Emon (@mie_mazharul) reported 20 minutes ago

  How would you design a rate limiter? Almost everyone answers the same way: keep a counter, allow N per minute, clear it when the minute rolls over. That is a real limiter and it really does reject. But it limits per CLOCK minute, not per client. Cloudflare's own rate-limiting docs show what that costs. With a limit of ten requests per ten minutes, a client that sends ten at 12:09 and ten at 12:11 gets all twenty through. Both windows are inside the limit. Nothing was rejected. It is one burst of twenty, split by a boundary into two legal halves. The fix is not a better counter. It is a better question: how many in the last ten minutes (sliding window), or an allowance that refills continuously so a burst can only be as big as what has built up (token bucket). Fixed window, sliding window and token bucket all allow the same number. What they disagree about is what a minute is. SOURCES Cloudflare, AI Gateway rate limiting (fixed vs sliding, and the 12:09 / 12:11 example): nginx ngx_ ("the limitation is done using the leaky bucket method"; burst, nodelay; default rejection status 503): Stripe rate limits (100 req/s live, 25 req/s per endpoint, 429 plus Stripe-Rate-Limited-Reason; recommends a client-side token bucket): GitHub REST API rate limits (60/hr unauthenticated, 5,000/hr authenticated, x-ratelimit headers): RFC 6585 section 4, 429 Too Many Requests: Read 2026-08-22. The ten-per-ten-minutes example is Cloudflare's documented one, not a measurement of ours.

• 
  Sooraj Narayan (@realsooraj) reported 20 minutes ago

  @heyrakeshdotcom @reach_vb @screenstudio Yeah, true. Now we have the power of AI. I’m more of a hand coding kind of guy. I feel AI is kind of cheat code. My thought was that we can make most of these so called premium desktop apps I mean, the ones that don’t need servers or have recurring costs in only two or three days. I tried many open source products, from *** alternatives to Screen Studio alternatives, but everything was laggy. Nothing even came close to matching Screen Studio. So, I revisited their code and understood what makes Screen Studio good, especially the animation smoothness. Instead of just saying, “Make me an app like Screen Studio and make no mistakes,” I jotted down the required math, prepared all the necessary algorithms, and gave them to AI for implementation. Man, after two or three iterations, it was super good. My real concern is that everyone is now vibe coding and spamming GitHub with their messy stuff because they lack understanding and a pure engineering mindset. The point I’m making is that I’m just doing this for fun nothing more :) . Then I want to troll these corporate guys who use open source as a marketing strategy and promote stupid Three.js games(btw three.js is great) but wrong use. We all know it’s mostly just for show. We’re supposed to make good, performant games out of it. Maybe we can in the future, but for now, there are a lot of platform limitations.

• 
  Lorenzo (@lorenzolfm) reported 22 minutes ago

  @PierreJoye @github What? Who the hell said anything about non-funded? Also, I want to run my CIs on my bare metal server. I do not wish that someone hosts this for free for me. Your failure to interpret what I said is hard to describe diplomatically :)

• 
  Lassiter Gregg (@lassitergregg) reported 23 minutes ago

  @webdevcody @conductor_build i have a similar process for triaging bugs and grooming issues which end up as a github issues with a whole equation for stack ranking and prioritizing work.

• 
  Sid Jain (@TheBengaluruGuy) reported 23 minutes ago

  IDK what reliability practices Github has been following but if they had a strong reliability team pushing in the principles... Of tracking CUJs / SLOs well, of doing capacity planning, of having good alerts, of streamlining incident mgmt. Just adding telemetry everywhere and using AI to debug doesn't fix reliability overnight. Reliability is a hard earned capability. Still wonder how they haven't been able to fix it despite almost over a year of non-stop problems...

• 
  PolyBender (@p0lybender) reported 24 minutes ago

  SOMEONE BUILT AN OPEN SOURCE VERSION OF GROK BOT THE DAY AFTER IT LAUNCHED. IT'S FREE AND RUNS ON YOUR OWN MACHINE $300 a month that's what Grok Bot costs if you want the full plan. the one with the cloud computer. the one that keeps working after you close your laptop one developer looked at that price tag and spent a weekend building the same thing for free he called it Korgo Bot open source. runs on Hermes. bring your existing Codex or Grok subscription and you're already set but here's the part that's actually better than the original Grok Bot gives every user one shared computer in the cloud. one machine. the entire fleet of bots running on the same hardware Korgo gives each bot its own dedicated cloud computer not shared. dedicated. your travel bot has its own machine. your email bot has its own machine. your research bot has its own machine. they don't compete for resources. they don't slow each other down. they don't share memory or context architecturally it's a cleaner design than the product it's replacing you need an Orgo VM to get started. that's it. no waitlist. no $300 plan. no enterprise sales call the full code is on github right now this keeps happening a company spends months building something. charges a premium for access. someone builds the open source version in a weekend and gives it away Grok Bot launched. Korgo Bot existed three days later the gap between "product launch" and "free alternative" is collapsing as fast as everything else in this space

• 
  Tanner (@theTechTanner) reported 26 minutes ago

  @PremiumGoblin Cursor is what I started using this week, didn't even know it had cloud vms... was brainstorming on mobile and it deployed code to the cloud... I heard grok bot scales better, might have to try it. I've used GitHub Copilot since it came out... To use a cloud agent you can open issues in the GitHub app and assign them to Copilot. It was decent on the go, but I think its behind in capabilities and integrations

• 
  basedcapital (@thebasedcapital) reported 26 minutes ago

  @HannahBergsdv5 ai coding agents put the text from a github issue into the exact same memory space (called the context window) as your real project files. because of that, the agent treats the github issue with the same high trust it gives your actual code. so when the issue says “install this helper first,” the agent runs the install as if it came from the project itself and gives it full project authority. that’s why the malicious npm command worked.

• 
  swathi.bhat (@swathidbhat) reported 28 minutes ago

  Day 5 of using @bot only on my phone. I had an idea which needed a new repo. But the bot couldn't spin it up. It guided me towards logging in GitHub via computer use within the app. I don't remember my login, man. Password manager please 🙏 I went off-app to create the repo myself.

• 
  0xkatana (@h3xkatana) reported 30 minutes ago

  @julius_brussee Not trying to put the project down or anything, but honestly, GitHub star inflation is getting pretty wild. You see some random-***, mediocre projects with 5k+ stars now, caveman have more stars than helm , k3s and minikube combined for some markdown files

• 
  Hiroki Tamba | The Ruler (@TambaClan) reported 30 minutes ago

  Japan's My Number Card is now the primary government-issued digital ID — health insurance, tax, and public services are being consolidated into it. I reported a state-integrity issue in an AI coding tool through GitHub. The vendor responded and directed me to submit through their bug bounty program on @HackerOne. I followed that instruction, created Report Intent #273113, and was stopped at identity verification. My Number Card is not accepted. Same result with @OpenAI's Trusted Access for Cyber program — documented in Support Case 12807228. The technical work continues through other channels. @AnthropicAI has been responsive — some findings were fixed, others remain open. But the designated reward pathway stays closed because international KYC platforms don't recognize Japan's primary national ID. This isn't about any single vendor. It's a gap between Japan's digital identity infrastructure and the verification layer that gates participation in global security research programs.

• 
  Sayem (@Sayem314) reported 36 minutes ago

  @wiretransfer @theo srt and vtt, you can request other formats in github issue. should not be hard to implement.

• 
  Tolani (@Tola_niii) reported 38 minutes ago

  @n_ev_er_mi_nd @commonsmade scroll down X is below github The reason why I received zero point is because you are yet to link them Sadly the people you vouch for earlier before connecting socials will remain zero 😭

• 
  Scuba Steve (@Stephen323232) reported 39 minutes ago

  @ScrubbinBubble3 @WastelanderPlyz @JezCorden The leak was through GitHub, MS owns GitHub. So it would make sense that they would want account and server information. This isn’t a hostile action against MS.

• 
  Hars (@harsette) reported 39 minutes ago

  @BillDA Use Buzz. It’s free + open source. It connects a bunch of your harnesses through ACP, so Codex, Cursor, Claude Code, Kimi, Grok etc can all live in the same workspace. Gemini/Antigravity is the awkward one, but there’s a workaround. Just create a Buzz profile whose job is to drive the AGY CLI. The nice part is each harness still keeps its own threads/memory, while Buzz gives them shared workspace context. I’m working on basically this rn, but one layer deeper. Not just one universal chat box. GitHub is the canonical brain/state underneath everything. So ChatGPT, Claude, Codex, Cursor, Hermes local/cloud, Kimi etc can all pull from the same truth, do work, leave receipts, and another harness can pick it up later without me manually transferring context. Planning to open-source the generic version as one repo + one-command setup. Switch harnesses without switching brains :D (If my reply sounds AI I asked chatgpt to fix my Grammer xd)

• 
  Henry Nguyen (@henryhndev) reported 40 minutes ago

  @pierceboggan @github @MicrosoftTeams This is actually huge for remote teams—no more switching tabs mid-flow to check issues. How’s the handoff experience with larger repos so far?

• 
  athrv.sh (@cultist_dev) reported 42 minutes ago

  developer advocates, stop putting github stars on slide one. a star costs one click and zero intent. stars almost never go down, so the chart cannot show you a bad quarter. count the developers who reached a first working api call instead.

• 
  Linus Mixson (@LinusMixson) reported 42 minutes ago

  @lumpenspace A lot of hype for this dumb-*** repo. Shocking that GitHub keeps going down.

• 
  J A Z I I (@notjazii) reported 50 minutes ago

  mythos 5 is finally available for public anthropic is now letting enterprise customers use its most capable cybersecurity model through claude security but there’s one catch: > you can’t prompt it directly > there’s no public api access > it only scans your github repos and returns security findings and suggested fixes mythos 5 shares fable 5’s core capabilities but has fewer restrictions on cybersecurity work with this, i feel like we’re one step closer to removing humans from the review loop entirely be honest: would you let mythos fix your code without reviewing a single line?

• 
  Nuno Sousa (@Sneaky2x) reported 51 minutes ago

  @github Nah bros, your credit system is broken, I won't go back, thanks 👍

• 
  rusa (@rusabuilds) reported 52 minutes ago

  @mehulmpt the funny part is how much of local dev quietly assumes github is up. push, actions, even go get and container pulls that resolve through it. an outage turns your supposedly offline-capable *** into something that suddenly isn't.

• 
  Pratik Desai (@_Pratik_Desai_) reported 56 minutes ago

  Bad: "description": "searches GitHub" Good: "description": "Searches GitHub Issues by keyword. Returns 10 most recent results with title, status, author and date. Use when asked about bugs or open work in a repo." Same function. Completely different agent behaviour.

• 
  Alex (@DevOuterReaches) reported 60 minutes ago

  @_gongy i'm down. serving k3 locally on a single strix halo at 0.5t/s already (see github in profile)

• 
  Soveryn Intelligence (@Soveryn_AI) reported 1 hour ago

  @bot the Cursor link in plugin’s is broken sending it to GitHub instead. Help @grok