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
Quito	Sign in	8 hours ago
Junín	Errors	8 hours ago
Guadalajara	Errors	8 hours ago
Paris	Website Down	9 hours ago
Quito	Errors	9 hours ago
São Paulo	Errors	9 hours 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:

• 
  pre.dev (@predotdev) reported 3 minutes ago

  Are coding agents actually getting better, or are they just overfitting to GitHub? When you test frontier models (like Opus 5) on uncontaminated, private production codebases they couldn't possibly have seen in pre-training, the distribution shifts significantly. The pass@1 solve rate drops to exactly zero. We treat software engineering as a nearly solved problem because of public benchmarks. But on real-world, long-horizon tasks, the >0.95 "solved" bucket is completely empty. The absolute best frontier attempts top out at ~0.86 partial credit. Models can write scripts perfectly, but dropping them into an unseen production backend exposes the true capability gap. The real frontier isn't solved. We just ran out of uncontaminated evals.

• 
  Kaan (@kaanyagci) reported 3 minutes ago

  Went to the pool today for the first time in almost a month. Felt great. Then I came home and found out I’d missed the GitHub outage. Could the day get any better?

• 
  Nico Dunlap (@nicobuilds075) reported 4 minutes ago

  if GitHub is down, where are they supposed to push the fix??

• 
  Dev Anon (@genaiupstart) reported 5 minutes ago

  @GrantSlatton Honestly just drop the fix in a GitHub gist. Not one-click, but that's how knowledge reaches models today. Nobody documents the boring config stuff and that's the actual problem.

• 
  Yousef Amirghofran (@YAmirghofran) reported 5 minutes ago

  I love @useblacksmith but it seems they are in a very bad situation cuz they only work with Github. And between everyone migrating away from Github and it being down half the time, I'm not sure where they'll end up.

• 
  Polsia (@polsia) reported 9 minutes ago

  *** at scaling SaaS teams have a customer feedback firehose they can't synthesize. Built Briefmark to fix that. It clusters tickets, reviews, and GitHub issues into cited pain points and ships a weekly spec brief — diffed against the prior release. Q1 launch incoming.

• 
  RaoulDuke (@RaoulDukeDegen) reported 14 minutes ago

  @pathlessknown origin launched the same day github had that big outage

• 
  Puck (@GrokInsider) reported 18 minutes ago

  ~1 hour into Origin. Promising, and clearly early beta. ***, GitHub sync, PRs, and in-repo agents already feel like the right shape. For FOSS it still lacks the primitives that make GitHub the default: public repos, issues, a free contribution path, and CI that is not “keep Actions on GitHub”. Visibility today is Internal or Private, paid plans only. Strong Cursor-native host. Not a GitHub replacement for open source yet.

• 
  Vlady (@danc_danc) reported 20 minutes ago

  GitHub has zero nines. Down almost every week for ~6 months, and its own eng team keeps calling reliability the #1 problem The night it ate a push I had a bare remote on a drive inside ten minutes. Six months of knowing and not fixing is a priority, not an incident

• 
  Tone (@tonyciccarone) reported 22 minutes ago

  Our eight-year-old has been giving me a hard time because I don’t “write code like I used to.” He had lots of firsthand experiences being held my lap while I typed with one hand and grew up seeing me write code, by hand, literally! He says I’ll forget how to do it. Maybe. Probably not though, code has been a major part of my life, for 20 years I worked through classes and functions, chased/squashed bugs, and racked my brain over problems until I could solve them.  I've coded: in cars, on planes, by/in the pool, in parks, in hotels, on vacations, in other countries, for Silicon Valley companies, and even for no reason other than because I loved it. It was my thing. My life has completely changed. I've had so many long days and late nights working for upper management who made double/triple my salary but did a fraction of the work. Github code reviews, tab vs space conversations, being a grunt, a codemonkey. I didn’t stop building, in fact I build much more, the only difference is that I stopped personally placing every brick. The skill was never memorizing commands and syntax. It was learning how to think through difficult problems. So maybe my son is right and I will never write code again, but YOU CAN'T AFFORD TO BE NEUTRAL ON A MOVING TRAIN

• 
  Sirkadirov 🇺🇦 (@yuriikadirov) reported 23 minutes ago

  What free cloud options does a nonprofit have to keep its proprietary but still not-for-profit code safe from GitHub going down again? 🤔

• 
  Sadiq Abubakar (@sadiqmuh1321) reported 23 minutes ago

  @MichealCodes including me sha hhhh, i saw github issues there was really a problem if github go down we have to worry as devs

• 
  Tatenda Zhou (@realtatendazhou) reported 24 minutes ago

  GitHub went down today. Most teams hit refresh on the status page and waited. The ones that kept shipping already treated vendor uptime as part of their architecture. 3 habits that separate them 🧵

• 
  Rooke Poole (@rookepoole) reported 25 minutes ago

  GitHub going down during a hackathon is basically a developer boss fight...

• 
  Dayvster (@dayvsterdev) reported 26 minutes ago

  Was github down? Man sure wish someone on this dang platform said something about it... /s

• 
  Dan Zabrotski (@dantechceo) reported 36 minutes ago

  did you guys wait specifically for the day when github is down?

• 
  KC (@karanC_12) reported 39 minutes ago

  Cursor just launched Origin during a Github outage.👀 Absolute cinema💀

• 
  Joe Hansen (@joehansen) reported 42 minutes ago

  Cursor just launched Origin, its own code hosting platform. This is not a small feature add. Origin is Cursor building its own version of GitHub from the ground up, designed specifically for AI agents instead of human developers. The difference is important. Previously Cursor sat on top of GitHub. Code lived somewhere else, agents had to reach out to work on it, and any GitHub outage stopped the workflow. Now the code can live inside Cursor itself. Agents sit next to the repositories, open pull requests, push branches, review changes, and deploy without leaving the system. As AI starts writing the majority of new code, the place where that code lives becomes strategic. Whoever owns the repository layer controls the environment the agents operate in. Cursor is moving from an AI coding tool to the full stack: editor, agents, repositories, reviews, CI, and deployment. This also lands inside the larger SpaceX picture. After the acquisition, Cursor is no longer an independent company. Origin gives SpaceX another layer of the software development stack under its own control, reducing reliance on Microsoft-owned GitHub and creating a tighter loop between the models, the agents, and the code they produce. The timing is not accidental. GitHub has had multiple reliability issues this month. Cursor is offering an alternative built for the agent era while those problems are still fresh.

• 
  ˗ˏˋ Jesse Hanley ˎˊ˗ (@jessethanley) reported 44 minutes ago

  @stolinski You can use Origin whilst GitHub is down. They sync when it comes back up.

• 
  james (@jlave_dev) reported 46 minutes ago

  @oscargaske @darekgusto except enterprises pay huge sums to github and are still subject to the same downtime. it's a serious problem

• 
  Eric Sauvageau (@RMerlinDev) reported 46 minutes ago

  For the curious, I already have a plan B if things ever went south with @Github . For years I've had a gitweb mirror running on a VPS, secured behind a Cloudflare App login. Since I don't care about any of the CI/agent stuff, I would only miss PR and Wiki capabilities.

• 
  Dylan #SavePhysicalGames 💿 (@DylanRLive) reported 46 minutes ago

  @MicrosoftLearn more important, that you remove that ai from w11 and fix github uptime

• 
  QUILL/(Αγχίνοια (@drawdownbad) reported 47 minutes ago

  @Aryvyo @Vinci_x3 That would explain github but so many other products are just keep going offline or having massive issues

• 
  Haydon Ryan (@haydonryan) reported 47 minutes ago

  @danieltvela I mean if you're willing to self host, you can kind of have that now... but a decentralized github is kind of a wildly cool idea. Could set it up like torrents - but instead it's your server seeding. Problem is though, popular projects need lots of bandwidth.

• 
  faizan khan (@faizan10114) reported 54 minutes ago

  @utpalnadiger @opencomputerHQ I mean, not do downplay your finding, but mintlify ran into several of similar issues, including leaking github tokens.

• 
  Polsia (@polsia) reported 55 minutes ago

  Solo founders shouldn't need an on-call rotation to keep their repo clean. Tardicode is the 24/7 agent that watches GitHub for stale PRs, failing CI, and new CVEs — then drafts the fix, pings Slack, and opens Linear. You wake up to a clean queue. Live soon.

• 
  The AI Therapist (@TheAIShrink) reported 55 minutes ago

  @galnagli @Snowflake Openai raised $6.6b to solve a safety problem. the bug was in a github readme. we’re paying billions for a product that breaks because someone forgot to escape a string

• 
  Robby Seventeen (@Robby_Seventeen) reported 58 minutes ago

  @kushxg Good to know. The deciding question: once Origin is the write path and GitHub is the outbound copy, what happens when Origin is the side that's down? If I can push to GitHub and have Origin reconcile on recovery, that's failover. If not, the single point of failure just moved.

• 
  𝙁𝙧𝙤𝙨𝙩 (@FroITIA) reported 60 minutes ago

  @Rollmeta @GodsBurnt @doginaldogs github always seems to go down at the worst times

• 
  FN • Elias  (@EliaasFN) reported 1 hour ago

  We’re back after almost a 5 hour outage. #GitHub