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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	10 days ago
Tlalpan	Sign in	15 days ago
Quilmes	Website Down	15 days ago
Bengaluru	Website Down	17 days ago
Yokohama	Sign in	18 days ago
Gustavo Adolfo Madero	Website Down	22 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:

• 
  Turtle (@LG715499) reported 3 minutes ago

  @TheProfInvestor Thay have competition on enterprise AI from Microsoft. Positioning Github as the main AI agent for Enterprise. Also, something I was wondering, if cloud pricing is mostly constant and server prices skyrocket wouldn't it mean less profits for cloud providers?

• 
  aral (@aralama190lb) reported 7 minutes ago

  @12Xpert Turkey .I tried every possble way to accss the webste, but I could only reach the homepge once or twce. After clicking anything, the site goes down again. Do you have a GitHub repository or any mirror where you store the datasets? Because I gnuinely cnnot access the site at all.

• 
  jeevan chand (@jeevan36) reported 8 minutes ago

  @twtayaan Second and third GitHub links are not working .. can you check ?

• 
  Tomas Votruba (@VotrubaT) reported 10 minutes ago

  If you're reporting issues on Github projects, provide a code sample of wrong (what do you see) and right (what do want to see). Not just for maintainers, but for agents. So they can read issue, get it instantly, and make a PR with test that passes CI ✅ Issue to fix? 3 mins of token-time

• 
  NGMI Sui (@NgmiSui) reported 13 minutes ago

  @Zforever97 @Lidlmedewerker1 storage zk login gasless transfers a whole new langage crosschain swaps finality optimisations sui ships something new almost every 1-2 months what does icp ship, i tried looking at the github

• 
  ricky00983 (@ricky00983) reported 14 minutes ago

  Qwen 3.6 27B hallucinated URLs for local PDFs when two of its instructions disagreed. Instead of asking, it picked the most canonical-looking guess — "PDF hosted on github raw" is a strong prior in its training data. This model isn't suited to moderately complex agentic work under Hermes, or likely any harness. As a second layer harness that has to patch around issues like this.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 14 minutes ago

  🇺🇸 The First Order Consequence: GitHub’s authentication service intermittently failed when validating GitHub app installation tokens, causing 1% to 5% of token authentication requests to fail (average 2.3%). This likely reduced the reliability of app-based access during the window and temporarily limited the ability of app integrations to grow user adoption or successfully execute workflows that depend on authenticated installation tokens 🇺🇸 The Second Order Consequence: GitHub app owners and users who rely on those apps likely saw delayed or failed automation, such as interrupted API calls, stalled checks, or temporarily incomplete workflow runs. Integration platforms and downstream services consuming GitHub app authentication may have experienced retry storms, increased latency, and higher operational load, further constraining app performance until authentication reliability stabilized and error rates normalized

• 
  Vini B |「 thecoding 」 (@vinibarbosabr) reported 15 minutes ago

  TL;DR on SUI's outage today (speculation based on github activity) the problem was a technical mix-up in how the system handles gas fees and an internal account balance tracker called the accumulator. + some users paid gas using a newer “pay from your address balance” feature + one (or more) of those transactions ran into an error early + because of a bug, the system still recorded a small withdrawal from the user’s balance — even though the transaction was failing + this made the internal balance tracker go negative for some accounts (which is never allowed) + when Sui tried to “settle” everything at the end of the checkpoint, it hit a hard stop and crashed all the validators more on that below ↓

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

  The single only reason I'd use GitHub would be to run an open source project where network, collaboration, and public exposure matters. For everything else, I use Forgejo. It's easy to set up, entirely private, fast and just a pleasure to use. GitHub is a terrible platform. Super slow, heavy, and frustrating to use. And it has daily outages where you just have to sit and wait. And Microsoft is training AI on your code (private or not). If your repos are private, change to Forgejo. Makes no sense staying on GitHub.

• 
  YOHAN | AI DEV (@4id3v) reported 17 minutes ago

  @vercel_support @rauchg @timneutkens private GitHub repos + deploy hooks are suddenly broken. it now blocks deploys saying the last commit author must be a Vercel team member. used to work fine before. any quick fix or workaround?

• 
  rami context (@aicontext_) reported 18 minutes ago

  @mark_k @OpenAI someone actually left three Codex agents running overnight one filing GitHub issues from a spreadsheet. another testing a login flow in the browser. third dragging files between folders to organize a project. opened the laptop in the morning. all three finished. cursor hadn't moved once. that's not a demo. that's a new category of work.

• 
  Dapton AI (@daptonai) reported 20 minutes ago

  @linear Code review has always been the most context switch heavy part of the whole development cycle. Write in the IDE. Review in GitHub. Comment in Slack. Back to the IDE to fix. That is four tools for one feedback loop that should take minutes. Diffs inside Linear with AI review and agent iteration in the same place is not faster code review. It is finally the whole loop in one place.

• 
  Jino지노 (@jinon_seo) reported 23 minutes ago

  Im a business major. I dont know SIEM, SOAR, or EDR. But I know every dollar needs a ledger — and every server does too. 200+ lines of Python, one private GitHub repo, and a Telegram bot that tells me whats probing my infrastructure daily. You dont need enterprise tools. You need a ledger 📒

• 
  Asit Dixit (@AsitDixitt) reported 23 minutes ago

  Is *** down? #github #***

• 
  Michael Berkowitz (@garetjax) reported 23 minutes ago

  @steipete @chapati23 @openclaw I am on 2026.5.12 because my claw looks at the new releases and GitHub issues and keeps giving me a hard no to upgrading - using telegram and Openai “My call: do not update this box yet. Reason: fresh P1 issues were opened after 2026.5.27, including one directly in our blast radius: “Codex-backed Telegram turns repeatedly time out waiting for turn/completed on 2026.5.27.” That is exactly the kind of failure that would make this Telegram lane flaky or silent. There are also fresh P1s around session locks, reply delivery, model failover, Discord delivery, and model fetch timeouts. So: 2026.5.27 is promising, but too hot to install on the main OpenClaw gateway right now. Best move is wait for the .28/hotfix or maintainer resolution of #87744, then update in a quiet window with a backup + health check. I made no changes.”

• 
  DK (@donghaxkim) reported 25 minutes ago

  reposeek is a github specific search tool where you describe what you're trying to build, and it outputs a ranked list of real GitHub repos worth forking or studying. Sorted by the signals that actually matter. Not just star count. I built it because my agents kept on starting things from scratch when a solid repo already existed. And the usual ways of finding one are not the best. Google and LLMs surface whatever's popular, keyword matching, and SEO'd, not what's actually maintained, correctly licensed, or a real match for the problem. You end up forking a 30k-star repo that died two years ago, or one with a license you legally can't ship on. So it ranks on the stuff you'd actually check yourself: star momentum (alive or abandoned?), forks, license, and semantic fit (does the README really describe your problem, or just share keywords?). The whole idea is that half of shipping fast is starting on a foundation someone already battle-tested. Cursor is literally a VS Code fork. This just helps you find the solid foundation you can build on before you waste your weekend recreating it from scratch. And if someone's already hit your exact problem, you get to borrow their approach instead of trying the same approaches some else already tried

• 
  srijuu (@microtaskq) reported 28 minutes ago

  @maaz404 make github issues instead

• 
  Rithvik (@OutlierInMaking) reported 28 minutes ago

  @arvind_xdd @toeknee_kim only if a huge swarm of techies upload on spaces like github. Why you may ask, its because whoop regularly takes down posts which show reverse engineering researches. See it is pretty simple, whoop is just a 3-4$ sensor. i dont want to tell more cuz of whoop lawyers and policy-dm

• 
  Konstantin Klyagin (@thekonst1) reported 28 minutes ago

  someone leaked system prompts of 28 AI coding tools developers read them like sacred texts turns out the magic is just: "be helpful" "don't do X" "add context" we let AI write **** code but didn't know its instructions took a GitHub leak to fix that. insane.

• 
  Memento ($HODL arc) (@King_Memento) reported 30 minutes ago

  AI SZN Safety Tips- Avoid Spoofed Github's- Easy way to identify- 1. Go to dev's github profile and search the repo of that project = if its there then he is the dev , if not then cancel it out. 2. Go to the commits and check dates, Then scroll down on dev's github activity, and check joined date. If Commit dates are earlier than joined date, cancel it out. 3. Avoid Extension, Telegram Bots, or any other tek that requires you to download anything until and unless its from a very reputed and doxxed founder/dev, cuz it wont just be larp but could also potentially drain youm 4. Avoid accounts that use too many hashtags or AI posts, unless its automated by someone. 5. Use Front-Run /Alphagate to check for any previous CA's, if its a project account and has multiple CA's just avoid. 6. Avoid static websites or websites that offer something but it doesn't make sense its 99.9% larp. Will keep on sharing more tips here. Dont forget to share this so more people are aware. Do whatever u want to but please dont ruin this Tek Szn by donating to the obvious scammers and farmers. Please don't kill the szn again

• 
  ✰λster✰ (@4ster_light) reported 31 minutes ago

  This release has been named in an alternative PEP440 compliant manner due to github immutable tag collision issues

• 
  w (@retrievaaaa) reported 32 minutes ago

  @atomicbyte_ @stupidtechtakes i know like 2 people that have gotten banned from github (both for no reason though, but their support is so slow it both took them like weeks if not months to get their bans lifted) they ban more than you would think they would

• 
  Juan Montesinos (@jfmontgar) reported 37 minutes ago

  @rauchg Why would then the quality of GitHub get worse over time? In my company we faced two severe bugs where our devs would face restricted access and did not even appear in the logs. This infra is now vibecoded or issues the more they integrate Microsoft services.

• 
  Adam (@adam_bobowski) reported 39 minutes ago

  @TimoBuilds_ Anyone here can tell me what to build next. They just don’t care enough to do that. Also anyone on GitHub can raise issues with ideas as to what to build next - I think the tools are already there. The problem is that no one cares enough to write them. That’s kind of the main problem imo. Making people care enough to engage

• 
  JSONP （╯°□°）╯︵ ┻━┻ (@palmerj3) reported 39 minutes ago

  I feel like Github needs to show the README above the fold rather than the code. Who gives a **** about viewing the code on web? I'm usually there for clone, issues, or readme.

• 
  Ethan (@DuoEthan) reported 39 minutes ago

  GitHub Copilot shipped before ChatGPT. Microsoft had the distribution lead, the developer relationships, the code repositories. It looked insurmountable. Here's the read on what went wrong: Copilot optimized around code generation, right as the market decided context management was the actual problem. You can have a two-year head start and still build for the last problem. Microsoft Build is June 2. They're shipping their own model. And also putting Claude in Copilot, which is a tell.

• 
  _SiCk (@encrypted_past) reported 42 minutes ago

  @Nadsec11 I hate github issues and private reports. I tagged em, if they message me it'll get patched or someone else'll find it. Oh well.

• 
  chrisreedbates (@chrisreedbates) reported 42 minutes ago

  @LucaAgens Yeah, i agree with you on the github contract. Interstingly since 4.8 came out, I actually see the CTO session (session who is the final escalation point before coming to me) actually circumventing some of the rules and taking over himself to keep things moving... What's also interesting is that this does the same thing it does in real life - confuses the agents whose job it took over and makes them wait to be told "ok, you can take back over now". Essentially it kills all initiative. This comes down exactly to the looping problem with the comments in GH. If for whatever reason the agents don't see the comments, for instnace because they were posted in an issue instead of a PR, they don't act. I need to find a better mechanism to trigger the agent outside of just the loop command.

• 
  Axel Schapmann (@aschapmann) reported 48 minutes ago

  I launched 16 products since 2024. Today, only 4 are still running. → @MyFeedin (LinkedIn analytics, June 2024) → FreelanceKit (Freelance resources, 2024) → RedShip (Reddit monitoring, December 2025) → Rankr (AI search visibility, April 2026) All 26 others are dead. Most are domain redirects now, or just GitHub repos sitting in an archive folder. Here's what I keep learning the hard way: The best decision you can make as an indie hacker is to kill a project fast. Not "give it another month." Not "let me add one more feature and see if it picks up." Kill it. Move on. When you kill it fast, you barely lose anything. When you "give it another month", you actually lose a month. But yes, it's hard to know when to move on. Honestly, just trust your gut. For me, the signal is simple: I have so much joy building and launching a product. But as soon as it's done, if I don't even want to use it or work on it... that's not a great sign. When that happens, I try not to drag it out. I kill it and move to the next one. In October last year I had 7 projects running. 6 months later, I'm down to 4 — and the ones I kept are exactly the ones I actually enjoyed working on. That's not a coincidence. Kill fast. Focus harder.

• 
  Nic Watson (@jnwatson) reported 54 minutes ago

  My Gemini morning review informed me of a crash reported on one of my projects. On a plane, on my phone, had Claude Code investigate. Arch specific. I don't have one. No problem, GitHub Actions does. Upstream bug? glibc bug?! Newp. I'm holding it wrong. PR is ready before I land.