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 (29%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	6 hours ago
Quito	Sign in	23 hours ago
Junín	Errors	24 hours ago
Guadalajara	Errors	24 hours ago
Paris	Website Down	24 hours ago
Quito	Errors	1 day 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:

• 
  p19k (@peteralexbizjak) reported 2 minutes ago

  @jethrolising Everything that's free is taken for granted. I just don't know how will GitHub improve their issues without artificially de-incentivize free usage. More aggressive paid tiers? I've no clue. Volume is the problem from what I've read on their blog.

• 
  Anis Ahmed Chohan (@AnichoBuilds) reported 4 minutes ago

  @kunchenguid So GitHub isn't the problem per say the problem is all the bad repos and actors hogging up the resources. Yeah iceberg is fair or I still don't think it is a bad shout for just hosting your own remote as an open source project is bad idea. Just need hosting in sure there are providers who'd be willing to host that for them.

• 
  effectfully (@effectfully) reported 6 minutes ago

  @ChShersh I almost accidentally went on GitHub for something and noticed it was down. Then I spent two days shitposting. Great news for the unemployed.

• 
  achilles (@infinitymod7) reported 10 minutes ago

  everyone's always like github is down github is down, but I've never had to experience it do they mean github actions or something?

• 
  piq and 69 others (@piq9117) reported 16 minutes ago

  @DanielW_Kiwi github wouldve gone down already with those views

• 
  Adel Bucetta (@adelbucetta) reported 18 minutes ago

  @unclebigbay143 vercel's api key auto-revocation for github integrations was a silent fix

• 
  Rob Smith (@RobmsmithUK) reported 19 minutes ago

  @mattpocockuk I know much should live in the github issues, but then do you simply use Agents/claud.md, context.md, change log and decisions/adr? For keeping things ordered?

• 
  Arun (@heyarunb) reported 26 minutes ago

  cursor launched a github competitor on the same day github went down for 7 hours. this is no longer product strategy. this is manifestation.

• 
  Nick e/code (@nicksdot) reported 27 minutes ago

  Feels like the regular GitHub problems could end in big trouble. People get tired. Non-OS has virtually no reason to be on GH - there are legit alternatives. So paying customers could just leave. Thing is, everything GH is doing for OS is cross-financed by those paying customers.

• 
  Albertos (@Alberto81712002) reported 27 minutes ago

  @Teknium I built a small plugin, how can I publish It? It seems the original github repo to PR to is down.

• 
  TheDavidTai (@TheDavidTai) reported 29 minutes ago

  Pretty interesting write up about the importance of solving the swamped by PRs issue. You can either gate or automate the pipeline or some combination of both. However there's no good solution to the industrial scale PR generation. I really do believe that the github killer will be the one who solves this issue and is able to give it away for free. I personally think it will involve being integrated with IDEs and use local LLM to eliminate the costs.

• 
  Sam Ongaro (@samongaro_) reported 32 minutes ago

  Cursor just launched Origin. Not just an AI code editor anymore. Now it wants to own the repo, the PRs, the code browsing… basically the workflow that developers usually give to GitHub. And the timing is brutal: GitHub had a major outage, and Cursor immediately opened a new front in the war. The AI coding race is no longer about assistants. It’s about owning the entire developer stack.

• 
  Scott (@scottjla) reported 32 minutes ago

  @birdabo People need to get over GitHub issues, and cursor is nothing without vs code

• 
  The codewali (@the_codewala) reported 32 minutes ago

  Put down Codex No more Fable Log out of Supabase and Vercel and Github. It's time to promote and sell brothers.

• 
  NIKSUN (@NIKSUN) reported 34 minutes ago

  GitHub suffered a major global outage this week, disrupting software development for more than seven hours across the Microsoft-owned platform’s 225 million-user ecosystem. The incident lasted several hours.

• 
  Weigo (@Samweigo) reported 34 minutes ago

  @nijokestu @replayio severity tags on github issues help mad

• 
  Clara Bennett (@CodeswithClara) reported 35 minutes ago

  Elon is after Microsoft now!! Cursor is planning to kill Github Yesterday GitHub went down for 7 and a half hours. Website, Actions, Copilot, code merging, all of it. 15,000 developers reported outage. GitHub's own CTO admitted they planned for 10x capacity and realized they needed 30x. They're now renting servers from AWS, Microsoft's biggest cloud rival. Cursor launched Origin the same day.

• 
  Suvodeep Mishra (@SuvodeepMishra) reported 37 minutes ago

  GitHub is down, 🔽 Cursor Origin is up 🔼

• 
  david (@yodering) reported 40 minutes ago

  github down at work i got nothing to do today

• 
  Darek Gusto (@darekgusto) reported 41 minutes ago

  @bil0090 In a form of a menu item on Cursor page, for paying Cursor users. Yes, it will for sure for a long time be used on top of Github, since people have yet to see if it sticks and doesn't get shut down by Elon in September.

• 
  Tasos V⚡ (@CryptoSympozium) reported 42 minutes ago

  @LunaTechAI @sabir_huss50540 Definitely removing the babysitting layer is the most important part. Built-in MCPs on claude code though, like Jira, Github, they don't fix the problem. I used both, for my daily coding tasks, and they do connect stuff and fetch context, but when you want them to run tasks they mess up with branching, CI, and PR reviewing. I have to manually guide them. Will definitely try this repo out.

• 
  Pavle Padjin (@ppadjin) reported 43 minutes ago

  You just know they were waiting for another Github outage to publish this. They probably didn't have to wait a long time tho

• 
  aapdo_gujju_gujarati (@gujju_gujaratii) reported 47 minutes ago

  github is down again and we still don’t have a real alternative 🫩

• 
  Apollo (@ApollonVisual) reported 47 minutes ago

  Cursor Launches Its GitHub Rival Cursor launched Origin as a code hosting platform built for AI coding agents. The service is deeply integrated with Cursor and can sync repositories from GitHub. Origin uses specialized infrastructure for large volumes of simultaneous automated commits. Its automated conflict resolution can assign a subagent when an agent breaks continuous integration tests. A human supervisor is notified only when the automated repair process cannot resolve the problem. Origin supports stacked pull requests that let agents work across dependent branches without waiting for each review. Its structural metadata records which model changed the code. The audit trail also stores the prompt logic and context window configuration behind each agent contribution. Origin launched in limited beta after SpaceX completed its $60 billion all stock acquisition of Cursor. GitHub generates about $2 billion in annual revenue and retains a much larger enterprise customer base.

• 
  Sriram Kiron (@sriramkiron) reported 49 minutes ago

  @BaneyDonovan i added image reporting to the latest sieve version. it's through github issues right now, though, so it's not anonymous. might change things soon

• 
  Synapse Brief (@Synapse_Brief) reported 50 minutes ago

  The real story isn’t the 7.5-hour outage or the 10x-to-30x planning miss — that’s just the symptom. The signal is what the CTO’s April post actually said: they planned 10x in October 2025, revised to 30x by February 2026, and still got hit. That means the demand curve is outpacing infrastructure planning cycles by quarters, not weeks. And the AWS rental isn’t desperation — it’s a multi-cloud hedge that Microsoft itself confirmed in June. Azure doesn’t have the elastic capacity to absorb agent-driven load spikes, so they’re paying their biggest rival for burst capacity. The Cursor timing? Product launches lock weeks in advance. But Origin’s real move isn’t the launch date — it’s the “Detach from GitHub” button. That’s the switch that turns a sync client into the source of truth overnight. This isn’t about hosting. It’s about who controls the authoritative copy when agents, not humans, generate most of the commits.

• 
  Eric Sauvageau (@RMerlinDev) reported 50 minutes ago

  @carlucci7777 @github No, I don't use AI to review code. Having received multiple AI-generated code reviews, I found that 80% of the content are non-issues: code that isn't actively used by my firmware, niche cases that are unexploitable and would just make it a PITA for future upstream merges.

• 
  Praveen Perera (@PraveenPerera) reported 52 minutes ago

  @theo github sign in on desktop on alpha and nightly is not working, i get a 404, was able to sign in on mobile, was also able to sign in on desktop by using the same email as github sign in

• 
  Simon Høiberg (@SimonHoiberg) reported 56 minutes ago

  @Martin_Adams Yeah but you're still depending on GitHubs control plane, that's why it's still slow. And GitHub even dabbled with the idea of charging people for action minutes even on self-hosted runners. I'd leave asap.

• 
  Stephen “The Yellow Dart” Schutt (@schuttsm) reported 57 minutes ago

  why do we have to live with downtime? scm isn't a hard problem to solve. Why do we have to tolerate github downtime? perhaps we don't code our own, but good grief, this is not acceptable