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	12 hours ago
Quito	Sign in	1 day ago
Junín	Errors	1 day ago
Guadalajara	Errors	1 day ago
Paris	Website Down	1 day 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:

• 
  Joshua D. Drake (@OffgridwithJD) reported 2 minutes ago

  @zombodb This isn't an unsolved problem. Github was created as a competitor to other services. Your main issue is reliability at this point, not what it would take to build out what users see

• 
  Ivan Tokar (@ivatokar) reported 3 minutes ago

  GitHub went down yesterday. One developer saw Copilot stop working and immediately repaired Visual Studio. This is why debugging remains a human job.

• 
  Jose N (@JoseTheWhale) reported 3 minutes ago

  @iruletrenches Memewhile a top 50 GitHub dev launched a token to work on a real problem via pumpfun. Then locked 10% and takes advice from the community. Yah crazy times ehh

• 
  Abdul Rafay (@abdul_rafay99) reported 5 minutes ago

  @BradlyCarp12623 @aurorascharff Yeah, the memory issue is still there. With 50 sub-agents running, keeping the dev server up and running E2E tests on 16 GB of RAM just isn’t possible for me. Even with one dev server, running E2E tests locally or via GitHub Actions can get expensive.

• 
  amer (@amerkld) reported 6 minutes ago

  Can't believe there was a debate around whether people can safely merge code written by frontier models today. I just let Codex work on two GitHub issues for ~50 hours and two questions later I decided scrapping that work was the only reasonable action.

• 
  hiren (@vinland_code) reported 8 minutes ago

  Crazy theory: GitHub was down because everyone was cloning their repos to Cursor’s Origin 💀 Don’t call me dumb 😭

• 
  Artur Kre (@Arturkre) reported 12 minutes ago

  @jumperz ..."for now, i would still use hermes for almost everything"... hell no, never seen such a buggy and broken tool as hermes agent. There are over 5k open issues on github - i killed two days setting it up but got stuck too many times to care and gave up on it

• 
  Neria Basha (@NeriaBasha) reported 12 minutes ago

  If GitHub Actions puts "${{ github.event.issue.title }}" directly inside "run:", treat it as code injection risk. GitHub recommends passing untrusted values through an environment variable instead. The value stays untrusted and is not expanded directly into the script.

• 
  ⌞· τaoli ·⌟ (@taoleeh) reported 13 minutes ago

  @MrAhmadAwais I can no longer login to my account via GITHUB even though I previously did.

• 
  Silksteele (@silksteele) reported 13 minutes ago

  @AunySillyMe Now I want a free subscription to GitHub due to emotional damage incurred during the outage.

• 
  Zakiya Tasneem (@Dev_Zoi) reported 14 minutes ago

  My timeline: With GitHub being down, every developer suddenly had a very valid excuse for not pushing code that day.

• 
  ashraf (@ashraf_chowdury) reported 19 minutes ago

  @drummatick This was not GitHub's fault, but GitHub had enough time to predict that this might happen and fix it

• 
  Ashutosh Bhandari (@withashutos) reported 24 minutes ago

  GitHub had its seventh status page incident in fifteen days yesterday. Six hours and forty-two minutes of degraded pull requests, API and enterprise SSO. Same morning, Cursor shipped its own *** forge. Nobody in hiring has noticed yet. But every reviewer who says "just send me your GitHub" is leaning on one link that was down all Monday, and may not hold the whole picture by next year.

• 
  Yash Solanki (@YashSolanki_) reported 29 minutes ago

  @jeal0uspengu1n @mehulmpt makes sense, but still i don't think it's gonna be super easy as people are just used to github, the issue is the downtime not the product itself, and considering that if it does resolves soon there is no point in going anywhere for anyone.

• 
  RaoulDuke (@RaoulDukeDegen) reported 30 minutes ago

  @thehypedotnews heard the github outage lasted six hours which made cursors timing perfect

• 
  オジサンWatching (@USinJapan1) reported 31 minutes ago

  @ForwardEditor Codex CLI does not lose context or restart when you switch model or reasoning effort mid-session. This was added as a documented feature (mid-session switching without losing context) and an open GitHub issue on the topic explicitly instructs that the warning text should not claim model quality necessarily degrades. What actually happens: switching model or reasoning effort mid-session breaks prompt-cache continuity for that provider. This raises cost and latency for the next turn because cached tokens have to be reprocessed. It does not mean the context window is regenerated from scratch or that output quality drops as a rule.

• 
  Soumyajit Mallick (@soumyajit__1) reported 35 minutes ago

  Everybody complains when GitHub goes down. Barely anyone migrates to an alternative. No one is building the GitHub for AI agents. That’s the real opportunity.

• 
  ΔS (@cemgineer) reported 38 minutes ago

  All the X-bots assembled to promote Origin and blaming GitHub for struggling under 180 million "devs" is absurd. Origin is an empty toll road mocking the public highway for having a traffic jam. It would crumble and go permanently down if it even handled half the load.

• 
  Sameer (@Sameerjs6) reported 41 minutes ago

  @orcdev Apart from GitHub’s terrible reliability, what features/thing that you think GitHub really needs for agentic era…??? Can you give one example? Reliability is the only thing that I think github really needs for anything i.e. for human or agents

• 
  Kuber (@kuberwastaken) reported 43 minutes ago

  @ValdikSS @XenoKovah Did test a fresh SpliX pulling from latest in another transcript (this was the dominant one) where it still hit the errors of multi-printing ; will share the diagnostics on the github issue :)

• 
  gianmarco simone ✨ (@ggsimm) reported 44 minutes ago

  3 steps to fix github performance 1. slow down every request not by me and my friends by like 10% 2. start randomly failing requests just to get some breathing room 3. randomly logout people 4. increase prices by 10% this should work

• 
  Mohamed Thoufic (@thoufic_sa) reported 44 minutes ago

  @ashuuu_soft github going down and cursor launching their own version of github called orgin was not on bingo card though. that was a great timing for elon to release their product publicly. they took up the opportunity and didn't wait any further to delay their product release.

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 45 minutes ago

  At first glance AWS Bedrock Mantle looks like something I don’t want. What am I missing: - no IAM controls? Am I reading that right? - looks like closely integrated with the OpenAI model which I already explained who I don’t like here and in my GitHub repo, - no InvokeModel - so it’s going through some kind of OpenAI sandbox, which I already explained causes problems with my game work. What I do like: - region locked down so what you are doing doesn’t slip into unauthorized regions. If you don’t know how to do sandboxing the OpenAI sandboxes may be a good option for you it just breaks what I am doing. For some reason the AWS console is pushing me to change this and I don’t understand why.

• 
  cheeselip (@lip_cheese) reported 45 minutes ago

  @matteocollina I don't buy it. GitHub - ignoring the social part - should scale easily because it's so easy to partition by repo or account and scale out. These slop repos probably aren't getting a lot of engagement so what's the issue? The issue is Azure lol

• 
  Billi Ramirez (@billiramirezdev) reported 46 minutes ago

  Now that GitHub is down more often, companies have also started providing their own solutions and AI models/tools. Cursor, the one that's aiming to be the #1 coding assistant tool, is now releasing Origin Code Hosting Starting with these essentials: * Repos * Pull requests * Code browsing * GitHub sync Agent-native features ship soon.

• 
  Beans (@javacoffeeeee) reported 50 minutes ago

  Idk why people thrashing on github down time the amount of slop getging pushed on it its pretty evident

• 
  Michael Flux (@michaelflux) reported 53 minutes ago

  @AdamRackis Jokes aside, the fundamental problem is that GitHub is just unwilling to deal with the root cause. I would bet 95% of the **** is coming from free accounts operated by people who have never built a single thing in their lives, who are making a commit for every time they need to center a *** with another commit 30 seconds later when they change the button colour. Simple solution? Put commit rate limits on free repos so they're not hammering the servers not stop. Put a limit of max repos on free accounts. Want to be unrestricted as currently? Pay like $5 a month. Cheap enough that anyone who actually wants to build can afford, but enough of a barrier than it will cut down on 90% of useless ****.

• 
  William Lahti (@LahtiWilliam) reported 54 minutes ago

  @Nobody1978_1 @manuelmaly Then why has GitHub been down for days?

• 
  Tornike Gomareli (@tornikegomareli) reported 55 minutes ago

  Huge thanks to new contributors and everyone who opened issue or wrote a comment as feedback. We are already 460+ stars on Github. Just released Talkify 0.6.0 - Added transcription history. Off by default. One plain text file per day in a folder you choose, and each entry names the app the text went to, transcription an date. - History is written before the paste, so a failed paste or a crashed app never loses the sentence. - Added a choice of where finished text goes, insert into the app, copy to the clipboard, or both. - Added an option to lower other audio while dictating and restore it after. If you move the volume yourself mid-sentence, your setting is kept in the future. - Fixed Read Aloud reading selections from secure password fields out loud. - Fixed the last sentence being dropped when quitting while dictation was still finishing - Fixed file transcripts being left readable in the temp folder after a crash. They are swept at launch and written owner only. - Hardened Accessibility interop against unexpected values from other apps

• 
  𝗠𝗶𝗰𝗵𝗮𝗲𝗹 𝗞𝗼𝘃𝗲 (@michael_kove) reported 60 minutes ago

  @joshmanders @github I don't even know what "Yo" is... There is no moat in running *** server with private/public repository hosting. That's not why people use GitHub.