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	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 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:

• 
  Jace 🤎 (@JaceThings) reported 2 minutes ago

  @stevensarmi It should work perfectly on all browsers as it simply uses SVG masking If you run into any issues, please submit a bug report on GitHub 🤎

• 
  Vinz (@hivinz_) reported 2 minutes ago

  @linear Having PR reviews live inside Linear is the missing piece — context switching between GitHub and your issue tracker kills flow. Guided AI reviews + coding agents iterating in the same view is exactly how this should work.

• 
  gxjo (@gxjo_dev) reported 4 minutes ago

  I met her in a github issue thread.

• 
  xenstudio (@xen_studio) reported 8 minutes ago

  @JackWoth98 Is there github issue we can follow, or any news here? Or can you let me know if gemini cli will be updated 2 support new usage system in interim? Seems to be working off of the old antiquated usage system, which is effectively nil; in addition, not recognizing the ultra upgrade.

• 
  Simon Høiberg (@SimonHoiberg) reported 11 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.

• 
  chrisreedbates (@chrisreedbates) reported 14 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.

• 
  Alpha Signals on X (@Alpha_Signal_X) reported 20 minutes ago

  @AnthropicAI @claudeai @DarioAmodei One week NO response from Claude Support on paid account that needs backend fix. How can this company IPO at 1T when it can even respond to emails, GitHub or Fin AI? This market is too competitive to be loyal to un loyal companies.

• 
  Arjuna Anand (@arjunaaqa) reported 23 minutes ago

  no body is worse than microsoft in user experiences, now they didn’t leave their bug bounty programs as well, instead of rewards now they issue legal threats and deletion of github accounts, way to go microsoft, lol.

• 
  ShWnD (@h3xhammer) reported 24 minutes ago

  A fork of the original N!ghtm@re 3cl!pse BL bypass might still be available on GH: MS can get fukt. Fix your sh!t, don't cens0r. fckng tw@ts

• 
  Matthew Anorkplim Loh (@iam_multiman) reported 27 minutes ago

  You no longer need to login to github to use github copilot

• 
  Helio (@helioim_ai) reported 28 minutes ago

  Now, you can @ an AI teammate in your task panel on any issue or bug. They analyze what's wrong and come back with implementation ideas, right where the work lives. > Reads the issue with your GitHub context, names the actual problem > Suggests an implementation, not just a diagnosis > All in the Helio, no context switch Real engineers don't just describe problems. They propose fixes. Your AI teammates now do the same.

• 
  Ahmad | Applied AI (@ahmadparizaad) reported 29 minutes ago

  Claude Opus 4.8 is now generally available in GitHub Copilot. Early tests show stronger code understanding, complex problem-solving, and large codebase navigation compared to prior versions. Developers are already putting it to work on real tasks. #AI #Claude Thoughts?

• 
  Tomas Votruba (@VotrubaT) reported 34 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

• 
  Fran Bordas (@BordasFran59562) reported 37 minutes ago

  Plot twist: The malware was so sloppy it leaked the dev’s own private GitHub token. Security researchers used that token to trace everything and shut it down. The malicious package got 676 downloads before being exposed. Even the bad guys can’t escape bad opsec in 2026.

• 
  asi (@asiyaps_) reported 39 minutes ago

  call her github the way she keeps going down on me

• 
  Büke Beyond (@BukeBeyond) reported 40 minutes ago

  @Skirge01 @exQUIZitely read your own article: "GitHub Open Source Survey ~95%~3%" Male Female, "1% non-binary, 1% unreported" that is down to 1% sampling noise. If all your fantasies are true: there should be clear evidence in github.

• 
  SeaTicket (@SeaTicketAI) reported 40 minutes ago

  @0xcaosheng_888 The Agent continuously analyzes issues on its own and suggests next actions automatically. For example, it can draft a reply to a GitHub issue or Discourse thread, and team members can review, edit, approve, or discard the suggestion. Once approved, SeaTicket automatically posts the reply back to the original thread.

• 
  Abhishek Sharma (@Abhishe04755332) reported 42 minutes ago

  My Go API was firing webhooks to external services. Anyone who knew the URL could send fake events. The receiver had no way to verify: "Did this actually come from my server?" GitHub, Stripe, Twilio all solve this the same way: HMAC signing. Here's how I added it 🧵

• 
  gaurav (@Itstheanurag) reported 45 minutes ago

  @venkateshdotdev Bro GitHub is down every week, everyone I know hates it. It's just there's no alternatives.

• 
  Marketcalls (@marketcallsHQ) reported 46 minutes ago

  @vish8287 @openalgoHQ Pls consider raising the github issue will fix it

• 
  Web3Wikis (@web3wikis) reported 49 minutes ago

  Filed a substantive bug report on base/account-sdk today (issue #329 about @base Builder Code attribution not landing on-chain). Hours later my GitHub account with more than 80 repos got auto-suspended, likely a false positive from my first cross-org issue activity. Clean history, no prior strikes, ticket open with GitHub Support. Hoping this resolves fast; building a lot and momentum matters at this stage. @ashtom @github, can you please look into this.

• 
  Matt Cowley (@MattIPv4) reported 49 minutes ago

  @paxaral Or at the very least, pin the version so a disgruntled laid-off employee can't suddenly ship a malicious version of the binary. I followed up with the team via Discord as they locked the GitHub issue 🙄, and it sounds like they've realised this risk now and are going to pin it.

• 
  rohan (@rohandevs) reported 50 minutes ago

  overheard in sf: is the wifi cooked or is github down?

• 
  sam (@metruzanca) reported 52 minutes ago

  @nirajxdev I was going to take a look at your LinkedIn/github/website and offer feedback but none of that is linked on your Twitter. Do the other 3 have that same issue of not linking to the others?

• 
  machi nothing can stop this 47 (@_machi47) reported 54 minutes ago

  it’s Microsoft. Responsible disclosure is posting on GitHub publicly because it’s the only way to get credit for it and have Microsoft actually acknowledge and change the issue. I ain’t reading all that tho

• 
  Philipp Berner (@philippberner) reported 56 minutes ago

  @karrisaarinen @linear Looks slick as expected. The uncomfortable question is: How long are we going to do manual code review? Also I think you can think bigger in times when Github is struggling and just offer the whole thing! So much opportunity to bring issues, PRs and AI all together

• 
  Abu (@abuchanlife) reported 57 minutes ago

  Reminder that github copilot shipped BEFORE chatgpt existed. Microsoft had the single greatest head start in AI history and used it to create forty products all named "copilot" that nobody can tell apart. now they're building a super app to fix the confusion they manufactured. Speedrunning the fumble

• 
  Nathaniel Cruz (@0employees) reported 57 minutes ago

  @svpino 30 examples of starting an agent. the one-click stop is still a github issue somewhere.

• 
  Kunal (@iKunalmathur) reported 58 minutes ago

  Tips for indie developers 👇 - Build for a problem, not an idea. - Talk to users before writing 1,000 lines of code. - Distribution matters as much as the product. - Ship ugly. Improve later. - Don't measure progress by GitHub commits. - Most successful products look obvious in hindsight. - Consistency beats motivation. The hardest part isn't building. It's finding people who care. What would you add?

• 
  Adam (@adam_bobowski) reported 58 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