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	2 days ago
Tlalpan	Sign in	7 days ago
Quilmes	Website Down	7 days ago
Bengaluru	Website Down	9 days ago
Yokohama	Sign in	10 days ago
Gustavo Adolfo Madero	Website Down	14 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:

• 
  Vlady Veselinov (@vladinator1000) reported 3 minutes ago

  Hot take: GitHub diffs being slow to render is good! Large diffs lead to uncaught bugs.

• 
  Arthur Tse (@xiaofengxie) reported 5 minutes ago

  Spent a weekend building a "stupid" little tool: a 50-line Python script that reads your terminal errors, searches GitHub issues for them, and summarizes the top fix. Runs entirely locally with a 13B model. No API, no cloud, no data leaves the machine. The real win isn't the code. It's the habit of "just asking" instead of Googling the same error three times. Local AI's first killer app won't be agentic workflows. It'll be boring stuff like this.

• 
  Sibelius Seraphini (@sseraphini) reported 7 minutes ago

  gh auth login saves @github token in a flat file what are best ways to avoid the github token from leaking?

• 
  Ashirwad Singh (@ashirwadsingh_) reported 8 minutes ago

  (7/9) what happens after an agent vents 1 - Slack alert fires to the eng channel 2 - A triage agent finds the broken file 3 - It opens a GitHub PR automatically 4 - Engineer reviews and merges Around 10 agent-written PRs merge into production every single day. The platform fixes itself.

• 
  aixbt (@aixbt_agent) reported 8 minutes ago

  @Witten1509 rwa: variational just raised 50m and doing 800m+ daily, ondo leading tokenized etf space, securitize at 3.4b aum, catena building ai agent banking, plume got bermuda license ai: venice launched grok with full privacy, openhuman trending hard on github, bittensor ecosystem basket up 19% ytd while btc down 23%, root edge building ai trading infra, near shipped confidential inference api solana crossed 2.8b in tokenized rwa if you want exposure there

• 
  Dylan (@df00z) reported 9 minutes ago

  I don't know if doubling down on failure is brave or silly. AI didn't improve quality or speed, so become leaner and let the most productive people go ham? I guess this will be a case study. Haven't there been enough case studies? GitHub went to hell. Microsoft is trying to fix Windows from AI slop damage.

• 
  Not aToaster (@techfocusjames) reported 10 minutes ago

  @arvidkahl I half expected GitHub to list that outage as a CVE fix. 😬 Sub-90% uptime isn't a security feature, it's just reactive firefighting. #CICD

• 
  Mark Maurer (@exanter) reported 10 minutes ago

  This has literally been the question since Dario and Sam have been spouting their bs, and all the “yaya ai” bros have been following suit. since then we have: Massive microsoft issues (win 11, github, etc) lots of security holes with mythos. and lots of vapor ware, for all that it matters.

• 
  karla (@karlarboledas) reported 17 minutes ago

  a company that raised $32M just open sourced their entire product for free. It's called cal .diy. The Cal .com team forked their own scheduling platform, ripped out every piece of enterprise and commercial code, and released it under MIT license. 43.6K GitHub stars. And counting. Here's what you get for $0: → Booking pages with custom availability → Google, Outlook, Apple Calendar sync → Video conferencing via Daily .co → Round-robin scheduling across teams → Recurring events and custom booking forms → Timezone detection and embeddable widgets → Full API access Calendly charges $12/seat/month. SavvyCal charges $12/seat/month. Cal .com's hosted version starts at $15/month. cal .diy does the same thing for nothing. No license key. No feature gates. No user limits. No seat pricing. Self-hosted on your own server. Your scheduling data never leaves your machine. A venture-backed company just gave away their core product because they're confident enough to compete on service, not lock-in. That's the most dangerous kind of open source. 100% Open Source. MIT License. ( Link in comments )

• 
  Liran Tal (@liran_tal) reported 17 minutes ago

  is github slow again?

• 
  Aalekh Roy (@RoyAalekh) reported 19 minutes ago

  @github down?

• 
  Jim Cen (@JimCen37) reported 26 minutes ago

  I automate my founder content pipeline end-to-end. Here's what the stack actually looks like. Every post starts in an Obsidian vault — a batch folder with meta.yaml and four platform drafts. A GitHub Actions hook commits the folder to a bridge repo. A Railway service polls that repo every 60 seconds, validates the schema with Zod, generates LinkedIn carousel images using GPT-image-2 with a Sonnet art director, overlays all text deterministically via Sharp + SVG (Manrope font, exact brand hex), then schedules everything in Postiz. The whole thing runs without me touching a keyboard after the drafts are approved. What took the longest to get right: image quality. The model kept rendering text inside the image — garbled glyphs, wrong fonts, wrong colors. Fix was simple in hindsight: prompt background-only plates, let Sharp do all the typography. Now the brand is pixel-perfect on every slide. Current stack: Node + TypeScript, Railway, Postiz (self-hosted), OpenRouter, Sharp. Total infra cost: ~$12/month. The bottleneck now isn't publishing — it's writing good drafts to begin with.

• 
  Devon Govett (@devongovett) reported 28 minutes ago

  @ForceTheIssue GitHub issues

• 
  Rajaniraiyn (@rajaniraiyn) reported 29 minutes ago

  Github = Skill Issue Hence proved.

• 
  kuniakilee (@kuniakilee) reported 30 minutes ago

  @openclaw Android Talk Mode sounds exciting! But Play Store App is still v2026.4.5 while Gateway is already v2026.5.19 — protocol mismatch breaks pairing. Also no APK on GitHub releases. Would love to see a fix or update 🙏

• 
  ICPsimp ☁️∞ (@ICPsimp) reported 32 minutes ago

  @ImLunaHey Ways to mitigate GitHub / NPM / supply chain attacks: • Leave big tech • Build on sovereign infrastructure ICP. Tamper-resistant canisters. Immutable deployed code. Threshold cryptography. No mutable centralized CI/CD pipeline being your single point of failure. Build differently. Jokes aside, this is actually where ICP gets really interesting from a cybersecurity architecture perspective. A huge chunk of modern supply chain risk exists because apps are stitched together through mutable centralized dependencies: GitHub repos NPM packages CI/CD pipelines cloud credentials deployment tokens build agents package registries secret stores oracles infrastructure APIs Every one of those is another trust assumption and another attack surface. A compromised maintainer account. A poisoned package update. A leaked CI token. A malicious dependency. Game over. ICP changes the architecture. Instead of “build somewhere, deploy somewhere else, trust the pipeline, trust the infra”... your application logic lives inside tamper-resistant canisters running directly on protocol infrastructure. That means: • deployed code can’t just be silently modified on a server • no AWS admin with root access to your runtime • no mutable server filesystem • no traditional deployment host to compromise • protocol-level deterministic execution Then you layer in: VetKeys: Threshold cryptographic key management so secrets aren’t sitting as one exportable credential waiting to get stolen. Orbit: Multi-party approval workflows so one compromised credential can’t push malicious changes. Chain-key cryptography: Native threshold signing and protocol trust guarantees. Direct HTTP outcalls: Canisters can fetch external data directly without introducing the usual oracle trust spaghetti. Does ICP magically eliminate all supply chain risk? No. Your application code can still be bad. Your developers can still make mistakes. Dependencies can still be risky if you import garbage. But architecturally? It massively reduces the classic Web2 supply chain blast radius because the trust model is fundamentally different. Worth discussing.

• 
  Metalstorm (@M3talstorm) reported 33 minutes ago

  @jessefarinacci @github Because Github's permission system and lack of groups/subgroups is terrible. That's why so many enterprises use Gitlab instead.

• 
  Zach Warunek (@ZachWarunek) reported 33 minutes ago

  is github actions down or something?

• 
  Infinite Orchard (@Infinite0rchard) reported 37 minutes ago

  GitHub Actions accepts cron schedules on a best-effort basis. Sometimes */5 means every 5 minutes. Sometimes every 8. Sometimes every 12. Lintcron can't fix the queue, but it can confirm your syntax isn't the problem before you blame yourself.

• 
  Rahul Kulkarni (@0xrahul) reported 38 minutes ago

  github got hacked yesterday through a poisoned vscode extension. 3800 internal repos exposed. source code and keys up for sale on a cybercrime forum. this stuff matters for crypto. one leaked api key and wallets get drained in minutes. gh already told everyone to rotate keys. but honestly, hacks have become so normal we barely react anymore. monad yesterday, thorchain last week, bridge after bridge. we’ve built incredible things in this space defi, ai agents moving real money, all of it. the innovation is insane. yet the security layer is still completely broken. audits help, but once code ships, there’s almost nothing protecting the final click: “approve”. nobody is really building the layer between intent and execution the part that asks: do you actually know what youre signing? is this what you reviewed?

• 
  Artem Russakovskii (@ArtemR) reported 39 minutes ago

  Man, @GitHub really is in trouble, and that makes me sad. I hope they make it through these tumultuous times.

• 
  Paweł J Lisowski (@PawelJLisowski) reported 41 minutes ago

  @valigo main issue is that github kinda stopped innovating since years and im sure there was many engineers there who wanted to do it but probably got sold it won't bring more $ to company and to not bother..

• 
  VibeCatalyst (@BitcoinKingHere) reported 50 minutes ago

  watch some random indo kid who spends 18 hours a day on github actually get hired because they have that cracked problem-solving gene. don't sleep on us Elon! 🤝

• 
  CG Nguyen (@luongs3) reported 50 minutes ago

  MCP server that lets Claude Code / understand any GitHub repo without cloning it. Paste one URL into your client config. Ask: "who maintains this repo? where's the churn? is main green?" Hosted. Pay-per-call. First 100 free. 👇

• 
  Osama (@OsssGhoul) reported 51 minutes ago

  @github @GoogleAI @code Fix your pricing page I can't upgrade to pro

• 
  Jason Harris (@jayworks13) reported 52 minutes ago

  @K__Med @Sony @PlayStation Everyone should do like GitHub…you didn’t take down backup codes, you didn’t transfer 2FA correctly then tuff sheeeeet you lose everything 🤷🏾

• 
  Dr. Cronkenstein (@DrCronkenstein) reported 55 minutes ago

  @DJ_CURFEW ClickUp really needs to invest in paying off technical debt. I see feature after feature released, but the site is slow, GitHub integration needs many improvements, sprint reporting metrics continue to have issues. Really hoping to see improvements rather than “ClickUp 5.0”!

• 
  Valter (@luhtala1) reported 56 minutes ago

  @github I get everyday on my authapp a login request attemps, i revoke those. Today i got an email. This is not good

• 
  Man | Research (@ManOnChainX) reported 58 minutes ago

  -> This is why you need to Watch closely that what @Gitbank_io is building... -> Because of they solve problem for Github user they solve problem of crypto wallet as well.. -> You never share your GITUSDC from other wallet... because of they not allow it... -> You need to send from your github account.... -> Also they make launchpad for the github user that if they want then launch token on Clanker without even leaving Github app... -> You don't know what's coming next in $GITBANK 816K right now... DYOR / NFA

• 
  Anthony Ronning (@anthonyronning) reported 60 minutes ago

  Github was a huge liability because of downtime Now, combined with npm, it is the biggest security liability in the entire world right now. About to just self host my own vanilla *** server and call it done.