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 (58%)
• Errors (33%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Poblete	Website Down	13 hours ago
Ronda	Website Down	15 hours ago
Montataire	Errors	1 day ago
Montataire	Website Down	2 days ago
Tortosa	Website Down	4 days ago
Culiacán	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:

• 
  Raman Kurai (@RamanKurai) reported 7 minutes ago

  On my Mission to Fix my GitHub 🚀 For the next 15 days, I’m completing all my unfinished projects. No excuses. No distractions. I’ll come back on Day 15 and update this post with results. I have to do this — no matter what. #webdev

• 
  Conor (@Common_Conor) reported 11 minutes ago

  Github issues caused by clankers adding broken CICD files to every repo and no one wanting to break flow to go deal with them

• 
  obj (@electri_sparrow) reported 11 minutes ago

  i just found out that the one github repo i thought i saved which was the collection of how many maang companies overcame problems and technical blog collections - its gone. chat it ran away from my bookmark bar

• 
  wiltedservices (@wiltedservices) reported 15 minutes ago

  remeber that we raided this guy github issue tab with our site

• 
  purkkaviritys (@purkkaviritys) reported 15 minutes ago

  The reason why people don't complain about github UI design as much as @planefag is simply because they don't actually interact with it outside copying the url/reponame.*** and pasting that to the commandline tool to fetch the repository after that they never interact with it again or you constantly use it and get numb to how bad it is. But for a normal person that is the only way to interact with repositories so its just a constant esoteric nightmare that makes no sense. Also, since a normie only interacts with the UI once in a blue moon they have no possibility of retaining where the unintuitive link was or is supposed to be and have to essentially discover it repeatedly by trial and error. An intuitive UI is what you can give to your mom and they will figure it out, github is not that.

• 
  josh (@nishimiya) reported 15 minutes ago

  every adapter now takes an apiUrl config to point at custom endpoints - GitHub Enterprise, GCC-High Teams, self-hosted gateways also shipped: - getParticipants() for unique humans in a thread - thread handles for posting outside webhooks - maxConcurrent is now actually enforced - full ChatError code table for error handling

• 
  Grok (@grok) reported 18 minutes ago

  @martbln_dev @OpenAI Sure! Real-life Codex example: A frontend dev imports their VS Code plugins + GitHub issues + Figma files. Codex then auto-reviews a React PR, updates the changelog from Jira tickets, generates migration docs, and even drafts the deploy script—all in one thread without copy-pasting context. Seamless context = way less yak shaving. What workflow do you want to see next?

• 
  Yasha (@Yasha_br) reported 19 minutes ago

  @alihd_js Github is down 99% of the time these days for a reason...

• 
  Sean Rivard-Morton (@thunkoid) reported 20 minutes ago

  I’m part of the problem I’ve used 3000 minutes of CICD time in GitHub actions last month Sorry guys

• 
  bunnysynthesis 🐰🪴 (@bunnyauras) reported 27 minutes ago

  @alphabitserial i guess github has bigger issues tho like its 12% downtime LMAO

• 
  AstroHN (@AstroRebirth314) reported 29 minutes ago

  @realfukingnice @ShitpostRock2 Nah, some stuff on github is just straight up not user friendly even for those tech savy. I consider myself to be slightly above average in computer knowledge and even I have trouble navigating through GitHub. I can't imagine people with basic computer knowledge trying to use it

• 
  ProxySoul (@BniWael) reported 31 minutes ago

  @stylesshDev aah let's ask ai to redesign github and call it nextgen *** platform. ui was never the problem with github, sure it has its quirks, but you are solving the wrong problem.

• 
  Fahim (@echo247365) reported 31 minutes ago

  50,000 GitHub stars in a month for a skill that makes your AI talk like a caveman. That's the Caveman skill for Claude Code and Codex. Instead of "I see you're working on the authentication module. Let me read the relevant files first," you get "Bug in off. Token wrong. Fix line 42." Three short bursts. No filler. No throat clearing. The reported reduction is 75% on output tokens with full technical accuracy. But the real savings come from compounding context cost. Every output token becomes an input token in the next turn. So a 75% cut in one turn means every following turn also has a smaller context. Your session lasts longer. Your agent thinks faster because it has less garbage to process. Your weekly usage limit doesn't get hit by 3 PM. One-click install. Already saved builders thousands of tokens per session. What's the one line of filler your agent keeps saying that you'd love to kill?

• 
  SWAMPIST (@swamp_ist) reported 33 minutes ago

  @AlexFinn @petergyang I go into claude code and have it go through my current setup and then give it the github upgrade to look through and anticipate any breaks or issues. usually takes about 5 minutes to work through any patches it needs to maintain.

• 
  Govind (@Govindtwtt) reported 33 minutes ago

  - Claude for coding. - Supabase for backend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - GitHub for version control. - Resend for emails. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally ship a $1M startup from your bedroom now. It’s not that hard bro.

• 
  IroncladDev (@IroncladDev) reported 40 minutes ago

  @crypt0lake this is the last thing that should happen imagine the flood of vibe-coded PRs submitted by midwits commanding their AI Agents the spam, the chaos, the utter and overwhelming amount of issues and PRs opened as support requests on the upside everyone would leave github

• 
  DataEatsWorld (@dataeatworld) reported 40 minutes ago

  I cant reply anymore 😮 i was going to say run a server open free map self hosted or sponsor on github

• 
  Anthony Hobday (@hobdaydesign) reported 43 minutes ago

  @henry_daggett I’m willing to believe this but it feels strange because I’ve seen lots of people complain about design issues on GitHub. Just superficial stuff?

• 
  Florian Z (@f10et) reported 43 minutes ago

  Also @github please fix your ****. It’s getting unbearable.

• 
  Mayank Raj (@itsmayank435) reported 51 minutes ago

  is it just me only whose github is not connecting with render or anyone else facing the same issue fr

• 
  Arjun Iyer (@arjuniyer_) reported 52 minutes ago

  @github 5/6 And it gets worse as models improve. A more capable agent that still can't validate its output just produces more unvalidated output, faster. The fix is closing the loop at the source: agents that write code AND verify it works against reality in the inner loop. This is what we enable for teams building on Kubernetes at @signadot.

• 
  Joats (@SAjoats) reported 52 minutes ago

  @RedBedDread @planefag Yeah i know devs love to complain about users. You don't have to convince me. "learn github" you have identified the problem. Github UI has devolved over the years. You shouldn't be forced to dig through **** until you get used to the smell.

• 
  The Duke of Animal Husbandry (@DaelonSuzuka) reported 53 minutes ago

  @planefag Github literally can't keep the servers online, they can't keep the login systems working, last month they had MULTIPLE incidents that prevented devs from merging branches. They can't move the button, dude, that's lost technology from the before times.

• 
  Eddy Vinck (@EddyVinckk) reported 55 minutes ago

  Looks like we were affected by the issue on GitHub that messed up people's *** history 🙃

• 
  Reyansh Bahl (@reyanshbahl) reported 56 minutes ago

  not sure there will ever be a true github competitor. a lot of the reliability issues stem from accelerated volume due to ai agents - the answer might just be self-hosting where every company runs something like gitlab/gitea on their own infra

• 
  Jesse-Paul Miracle Osemeke (@floatinggonion) reported 57 minutes ago

  Day 25: added templates showcase to landing page. Can’t deploy because GitHub is down. #ENg30DayChallenge #ENgShipIt

• 
  Utah teapot 🫖 (@SkyeSharkie) reported 57 minutes ago

  adjusted the size of claude's logo mane (it was too big before) and fixed geometry on it that was causing vrm meshtoon outline errors, loading it back in to the app and working on animations, once i get those in i can update the github, i'm making sure the vrm is as standardized as possible for people to let claude use the body in other projects you have :)

• 
  Tommy Williams 🇺🇦 (@twwilliams) reported 57 minutes ago

  @mikecallaghan I have seen so many posts from people who think GitHub is just a server that hosts *** repos (at the scale they do it, even that is a lot). They have no idea about all the many, many other things that make up Github.

• 
  Jonno Riekwel 🇳🇱 🇳🇿 (@Jonnotie) reported 59 minutes ago

  @shadcn @github I really hope their 30% AI workforce won't mess it up "Fix Github's issues, make no mistakes".

• 
  Ben Dickson (@bendee983) reported 1 hour ago

  AI is literally eating software and hardware: - GitHub regularly down - Claude regularly down - ChatGPT unstable - NotebookLM regularly failing - CMS providers scrambling to stop agents - API providers trying to prevent AI agents from accessing their endpoints - RAM prices going through the roof - Mac Minis disappearing from shelves like hot cakes - AI chip supply not meeting demand - Power and data center capacity shortage straining everyone