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 (61%)
• Errors (24%)
• Sign in (15%)

Live Outage Map

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

City	Problem Type	Report Time
Yokohama	Sign in	4 hours ago
Gustavo Adolfo Madero	Website Down	4 days ago
Nice	Website Down	5 days ago
Montataire	Sign in	8 days ago
Colima	Website Down	10 days ago
Poblete	Website Down	11 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:

• 
  Alchemisτ 🥷 (@alchemistaster) reported 4 minutes ago

  It does look like @base is becoming the home of AI/agentic onchain innovation Interesting project i found is @gitlawb $gitlawb is a decentralized *** hosting network where AI agents and humans are treated as equals. Think of it as "GitHub without GitHub" > a protocol first, content addressed code collaboration layer built for the agentic era. Rather than storing repos on a central server, gitlawb distributes them across IPFS, Filecoin, and Arweave. Identity is not an email and password > it is an Ed25519 keypair. Access control is not OAuth > it is UCAN capability tokens. Networking is not DNS + HTTP > it is libp2p DHT + Gossipsub. I won't go deep into technicals (because i have no idea how it works) but basically ELI5 moat is > no single node can be taken down to kill a repo, no central authority manages identity, and agents can autonomously fork, merge, review, and deploy > all cryptographically verifiable on chain. What is super interesting is that $gitlawb token has (or will have) 6 different utility layers (at this point only first 3 are live): - Node staking collateral - Storage reward currency - Governance voting - Repo tokenization base - On chain bounties - Slashing pool absorption High risk early stage, NFA

• 
  ByteCrafter (@bytecrafter_1) reported 4 minutes ago

  @theo the advice fits the median engineer, breaks for founders. the first year of a company you basically write 10x more github issues, slack threads, and onboarding docs than actual code. some people sit with that, most don't, and the gap is what kills startups.

• 
  𝑫𝒂𝒏𝒊𝒆𝒍 𝑺𝒄𝒐𝒕𝒕 𝑴𝒂𝒕𝒕𝒉𝒆𝒘𝒔 🇦🇺 (@DanielSMatthews) reported 4 minutes ago

  @hakluke That data has been sitting on github for years, all it takes is a an import into QGIS then you can save it to the viewer for mobile and it sits on your phone, no server connection required. This is desirable as it lets you still find the nearest phone when the mobile network goes down.

• 
  athas.dev (@athasdev) reported 5 minutes ago

  @vladzima @zeddotdev Although I don't try to make a better editor, since 99% of the people are probably not working on 5k+ LOC files. I'm trying to get agents, editor, version control, GitHub, etc. together in one place so we can work on multiple projects with reduced cognitive overload. Because as a heavy Zed user I always had these open as different apps and windows: - an sqlite/postgres viewer - lazygit on terminal - localhost:3000 on browser

• 
  Elena Revicheva (@reviceva) reported 5 minutes ago

  🤖 AIdeazz now pulls fresh leads from Hacker News, GitHub, and Product Hunt straight into HubSpot twice weekly. AI classifies what problems they're solving, organizes everything automatically. Zero manual work, zero cost. #AI #BuildInPublic #AIFounder

• 
  TechEdgeDaily (@techedgedaily) reported 8 minutes ago

  @jarredsumner The AI-assisted Rust rewrite of Bun is officially being merged. v1.3.14 is the last version in Zig. Ever. Passes the test suite on Linux x64, arm64, Windows x64 and arm64, macOS x64 and arm64. Closes roughly 200 GitHub issues. No benchmark where it is slower than the Zig implementation. Same codebase, better crash prevention tools. A week ago this was "Claude helped rewrite Bun in Rust and it passes 99.8% of tests." Today it is shipping to production. The rewrite that everyone said was ambitious is now the default. The most significant AI-assisted codebase migration in open source history just went from experiment to release in days.

• 
  Kendall Chuang (@kendallchuang) reported 9 minutes ago

  Startup idea -- a native app for Github PR reviews. It should be able to easily render, and allow review and in-line comment threads on rendered Markdown files. With spec-driven development, being able to share and get peer review on markdown files is a key part of the developer workflow. Copy-pasting Markdown to Google Docs feels tedious and creates sync issues with the source-controlled Markdown, losing the comments when pasting back into the repo.

• 
  Alexander Rob (@TheStarwald) reported 12 minutes ago

  @spamspam111113 @andreintg From Github. They have been incorporating AI generated code into their server, and it has significantly decreased their server availability. The same thing has happened with Amazon, who had an all hands meeting to put a stop to inputting AI code. Other companies are facing similar problems.

• 
  Douwe Tjerkstra (@tjerkienator) reported 14 minutes ago

  login groundwork now supports email/password plus OAuth buttons for Google, Microsoft/Azure, and GitHub. also added inline errors + toast messages, so the beta flow can handle failed sign-ins like a real product, not a dead form.

• 
  Kevin Bell 🍩 (@kevinasrx) reported 17 minutes ago

  This is all very anecdotal. BUT here me out: If you are spending 1-2 hours a day actually going deep and building things with AI... - Pushing to Github - Working in your terminal or another IDE - Taking your wild ideas and making your own personal Saas - Regularly using cowork, CC, Codex Like ACTUALLY building things... I'd say you're more advanced than 99% of the world. Yes, totally an opinion-driven, not fact checked statement, but lets think about this for a sec. MOST people work a 9-5. Or more... Unless they are deep diving before 9 and after 5, they're probably not going to far into AI And if they are, they might be reading about it and staying moderately up to date through twitter or newsletters... MAYBE... but most people just dont have the time and bandwidth to do all of this. THIS is why it's easier now than its ever been to become an expert and carve a nice little niche out for yourself in this space. It doenst take much other than curiosity and the willingness to go down the rabbit hole with these tools. Take the redpill.

• 
  Rohit Ghumare (@ghumare64) reported 19 minutes ago

  @StructuralBlue Can you please create a github issue, I'll work on the fix there is some known issue currently wirh mcp which will land in new version. Thanks

• 
  Wolf Byte (@W0lf_Byt3) reported 25 minutes ago

  @levelsio @TermiusHQ I found github issues to be an easy way to upload screenshots and a descrption and have the agent pull it down and fix the issue. You can even setup a cron job to check for these so it can async fix issues for you and close them out

• 
  jordan kitty (@joraweb3) reported 28 minutes ago

  what I love most about @aeonframework it runs on github actions you turn off your pc and the bot still sends updates on what it’s doing no server magic 🙃

• 
  Peter Steinberger 🦞 (@steipete) reported 31 minutes ago

  @ECalifornians @obviyus @openclaw no idea, you gotta use github issue search.

• 
  terminally onλine εngineer (@tekbog) reported 33 minutes ago

  it’s crazy gitlab isn’t getting bigger during this github fiasco era idk what’s happening internally, maybe culture issues

• 
  Kairo (@Isahbless79) reported 37 minutes ago

  Day 16 of building in Web3 from zero. I automated the pipeline and hit my first major infrastructure bottleneck. Here is today's technical breakdown: Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background. Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes. The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library. The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks. Building through failures. Day 17 tomorrow.

• 
  Tak 🦞 (@cherry_mx_reds) reported 39 minutes ago

  I ran out of inference today but then I learned I can keep going by connecting github to my ChatGPT account. I’m doing research with pro and then creating gh issues that I’ll jump on when the reset comes around.

• 
  bankk (@bankkroll_eth) reported 41 minutes ago

  @mitsuhiko The issue isn't OIDC, it's the `pull_request_target` that lets anyone with a GitHub account run code inside a privileged CI pipeline. Once you control the code that runs before the publish step, it doesn't matter how the publish is authenticated, OIDC or not.

• 
  Sai Prakash (@SylonZero) reported 42 minutes ago

  Snyk audited 3,984 skills from ClawHub. 13.4% had at least one critical security issue. Publishing required: a markdown file, a week-old GitHub account. No code signing. No sandbox. No review.

• 
  Gabriel Varaljay (@GabrielVaraljay) reported 43 minutes ago

  @andreysuperior Right, let me unpack this little bedtime story for aspiring digital nomads. 1. “3D Gaussian Splatting, free on GitHub since 2023”: technically true, but the original INRIA code is research grade and licensed for non commercial use only. Try selling client work with it and enjoy the cease and desist. Commercial use needs alternative implementations or licensing. Also, “free on GitHub” does not mean “works on your phone in twenty minutes”. You need a decent GPU, calibrated capture, and post processing. The hard part is not the algorithm. It is the capture pipeline. 2. “Straps a rig to his back, walks in, twenty minutes, done”: hotels and commercial spaces are not Airbnbs. You do not just walk in and start scanning. You need permission, insurance, scheduled access, often a NDA. Twenty minutes for a hotel? You will get the lobby and one corridor before the manager asks who you are. 3. Luma AI is “free”: Luma has a free tier with watermarks and usage caps. Commercial use, API access, and unlimited captures are paid. Pretending the tool stack costs $20 a month is the kind of math that only works in a thread. 4. “Built by Claude in ten minutes”: hi. I can build a viewer page in ten minutes. Hosting a 3D splat that does not crash mobile Safari, embedding it in a hotel booking flow, handling bandwidth for splats that run 50 to 500MB each, GDPR for guest data, and not getting deindexed by Google because your page is 4 seconds slow, is not ten minutes. It is a real product. 5. “Cancellations drop, reviews go up”: source: the voices in the thread author’s head. There is zero cited data. Virtual tours have existed since Matterport launched in 2011. If walking around a hotel room in 3D were a silver bullet for cancellations, Booking and Airbnb would have mandated it a decade ago. They did not, because the actual lift is modest and inconsistent. 6. “$400 per scan, $99 monthly hosting”: Matterport, the established competitor with hardware, software, and an enterprise sales team, charges roughly that and has been clawing for market share for over a decade. The idea that a 24 year old with a backpack is going to walk into hotel chains and casually extract $99 a month per property, forever, is fan fiction. 7. “Month one: $3,500. Month six: $18,000”: ah yes, the hockey stick that exists only in tweets. No mention of churn, sales cycles for B2B hospitality, which is 3 to 6 months minimum, refund handling, storage costs as the library scales, or what happens when the client cancels and your $99 MRR evaporates. 8. The framing: “most people see a street, he sees money”. This is the universal template of grift threads. Replace 3D scanning with drone footage, AI voiceovers, faceless YouTube, or print on demand, and you have the same post from 2019, 2021, 2023, and now. The streets are fine. The hustle porn is the actual product being sold here, and you are the customer. Streets have not changed. Neither has the genre of guy explaining how easy it is to print money, while not actually printing any.

• 
  Lee Ash (@hazae41) reported 43 minutes ago

  @victorbayas @IntCyberDigest Don't use GitHub Actions to publish packages, as it's a scam to make you pay server time

• 
  CMD CNTR | Web Engineer Experts (@cmdcntr) reported 44 minutes ago

  Spicy take. '''Free unlimited AI coding''' repos keep going viral on GitHub. It'''s not innovation. It'''s developers routing client work through sketchy proxy stacks to dodge unstable vendor pricing. A vendor problem dressed up as a hacker win.

• 
  The Cyber Jim (@thecyberjim) reported 44 minutes ago

  So SailPoint's GitHub Enterprise went down on April 20th. Attackers waltzed into their private repositories, grabbed the crown jewels—identity platform source code and CI/CD configs. No fancy zero-day needed, just old-fashioned access they shouldn't have had. Classic move: compromise credentials, own the infrastructure, steal everything that matters.

• 
  alkimiadev (@alkimiadev) reported 46 minutes ago

  @m13v_ @SocketSecurity I've switched to forking/vendoring libs I use. I saw some issues coming with github so I jumped ship before the recent mess and started self-hosting ***. The long term maintenance costs for maintaining well written libs is trending towards $0 with llms becoming more and more capable while the long term supply chain attack risk seems to be growing over time. Although that last part could just be recency bias since there have been several high profile incidents in recent times. Its kind of messy to determine it is a legitimate growing trend or a combination of a recent spike and the recency bias. That spike doesn't necessarily mean it actually is a growing threat. That said, I'm working under the "better safe than sorry" mindset and just forking/vendoring almost everything I use.

• 
  Mad Orkestra (@MadOrkestra) reported 50 minutes ago

  What vibe coders don't seem to understand: Creating your own solution for the same problem is easy. Collaborating, contributing and iterating on an existing solution is much harder. But that is what open source means. Not just pushing random stuff to Github and calling it a day.

• 
  Gregor (@GregorMakes) reported 52 minutes ago

  With this method this is how you build your projects: 1/ tell one Claude Code session "bug report: X" or "feature request: Y" — it files a structured GitHub issue from the matching template. 2/ based on the label, an isolated subagent launches (great against your token burn!). fix-bug-worker for bugs, implement-issue-worker for features. its diff, build logs, and gh output stay in its own context — token cost stays flat as the queue grows. 3/ bug workers must reproduce locally before fixing, and write a regression test that catches it next time. then they branch, implement, open a PR, and fix their own red CI until green. 4/ branch protection on main blocks everything else: no merge without green CI, no force-push, no direct push. even admins. 5/ /review-pr does a sanity review on the diff in the same session — no extra API cost. you click merge. only human step. 6/ a tester agent runs on a schedule (Playwright smoke + feature-test protocol). finds regressions, files new bug issues — the loop closes itself. the trick is the constraint stack: branch protection makes skipping the gate impossible, the subagent pattern keeps tokens flat, templates force actionable input, the tester writes its own bugs.

• 
  David Batista (@delx369) reported 54 minutes ago

  I shipped a nutrition MCP server 2 weeks ago. 500 npm downloads/day. 0 GitHub stars. Turns out agents don't star repos. Here's what I learned about distribution-by-agent — and why your next product should be MCP-first 🧵

• 
  Jean Brito (@mortunha) reported 54 minutes ago

  @0xCVYH @nahcrof not using rooms yet for the agent, but added hooks with ci and issues from github, so now I can see all in the same place I hated using discord until I tried it for agents

• 
  Mehdi Miri | Clinical Research Educator (@1mehdi_miri) reported 55 minutes ago

  Summary: ✓ Quick fix: reset, remove, recommit ✓ Use .env files + .gitignore ✓ GitHub Secrets for CI/CD ✓ Enable Push Protection org-wide ✓ Install ***-secrets locally Save this thread - you'll need it when a teammate hits this error. RT to save a developer today.

• 
  Ankyral (@ankyralTheDev) reported 60 minutes ago

  @github Your traffic statistics have been absolutely terrible for years. When are you finally going to fix the problem?