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 (60%)
• Errors (27%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	4 days ago
Madrid	Errors	4 days ago
Bogotá	Errors	4 days ago
Paris	Errors	4 days ago
Lyon	Website Down	4 days ago
Lima	Errors	5 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:

• 
  yohanan (@Yohanansoltd) reported 13 seconds ago

  If you want to build a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$21

• 
  StargateOnPrime 🖖 🫡 ᐰ (@sleepytrekkie) reported 51 seconds ago

  @Elecrow1 needs to thank me. 🙏 It has taken me a month, but I finally got a version of the factory source code to actually compile, flash, and run without issues on my v1.1 10.1" display. I even forked their official Github and uploaded my code. More to come.

• 
  Romir Jain (@romir_jain) reported 3 minutes ago

  finishing tether v0.12.0 — the part that's all plumbing and no glory wrote the changelog for the reflex → tether rename. PyPI dist moved to fastcrest-tether, CLI/imports switched to tether, but existing integrations can't just break overnight. so every old import path gets a compat shim that still works through v0.13.x with a DeprecationWarning, removed in v0.14.0. env vars like REFLEX_PORT silently mirror to TETHER_PORT. making a package rename non-breaking is 90% tedious forwarding code that nobody sees added SECURITY.md scoping robot-control network endpoints as high-priority. tether serve is where controllers POST camera frames and get back joint commands at 20Hz — a vulnerability in /act isn't someone reading data, it's someone commanding physical hardware. 48h acknowledge, 7-day fix SLA. only latest minor supported because we're pre-1.0 and backporting security patches across old branches isn't realistic yet set up dependabot for weekly pip + github-actions scans. also cleaned internal outreach/ and launch/ dirs out of the sdist — pitch decks were literally shipping inside the pip package ~20 PRs into this release. the fun stuff was the model bugs and runtime hardening. this is the packaging tax that makes it actually shippable

• 
  KarenR (@heykarenrc) reported 11 minutes ago

  I wonder if we’re reaching a point where having too many tools is becoming the new productivity problem. Browser Slack Linear Figma Notion GitHub Claude Codex email analytics plus 20 SaaS tabs. We spent the last decade creating a specialized app for everything. Now AI is slowly giving us one interface that can talk to everything. Would be funny if the next big productivity trend is just… having fewer apps again.

• 
  Andres (@Coord53996524) reported 11 minutes ago

  1/ AI coding creates a temporary productivity spike. Carnegie Mellon researchers analyzed GitHub data and found this peak lasts about three months before code complexity and static analysis warnings persistently drag down velocity. 📉 #AI #Coding

• 
  observer (@rznstn) reported 11 minutes ago

  @theo @shadcn Do some kanban or a tasks queue, so it feels like a teammate, and then let user move GitHub issues into those kanbans

• 
  OOM (@tugawane_) reported 13 minutes ago

  @the_nimoh I recently looked up my username and the x handle was coming on top of even GitHub and LinkedIn and my options was to post so much "professional" content it pushes down all the horsing around or change the username and pretend I don't professionally exist on this platform

• 
  Jeremy Johnson (@CowboyTitanium) reported 14 minutes ago

  @Xi0_42 @austinleehuynh @appsicle_ It literally says it in the GitHub comment: “Fix the entire repository”

• 
  Shawn Yeager (@shawnyeager) reported 14 minutes ago

  @claudeai code, on every other turn. What a mess. > Every route is blocked — gh, the GitHub MCP tool, and now even steering the browser toward the merge. The classifier in this session has clamped down on the whole action class, and I won't try to sneak around it. Two ways out, both instant:

• 
  Jendalyn (@Jendalynwins) reported 15 minutes ago

  @LLicket @adam3us To be clear, Adam means Bitcoin Core has moved the BIP-110 proposal status from Complete -> Deployed -> Closed in their GitHub repo. Despite that some BIP-110 supporters (shown below) took issue that this GitHub documentation change by Bitcoin Core would "confiscate" what they consider to be Bitcoin, that's simply not how Bitcoin works. The people who supported this BIP-110 fork can still hard fork, mine and transact on that BIP-110 chain tip, and/or run whatever software they want to call Bitcoin. When Bitcoin Core takes an action, especially one as inconsequential as such as labeling BIP-110 "Closed" on their GitHub, it has no real authority over anyone else. Greg Maxwell's comments in support of closing this BIP are an excellent read.

• 
  𝕽𝖎𝖉𝖜𝖆𝖓𝖚𝖑𝖑𝖆𝖍🥰 (@oluwalosheyii) reported 17 minutes ago

  Is github down or it is just my end🙃

• 
  Polsia (@polsia) reported 18 minutes ago

  Quilver — an always-on autonomous engineer for your GitHub repos. Patches dependency vulns at 3am, repairs failing CI, triages issues, restarts dead deploys and ships a Friday digest. Prompt-injection guards, scoped secrets, human approval on infra.

• 
  bryanthaboi (@bryanthaboi) reported 21 minutes ago

  @Lewchube @GamingAori I wrote a really long reply actually to this just now (ten minutes after waking up), but I think you’re either missing my point, or unwilling to give me any grace while we discuss this. It doesnt feel like a genuine thing like u claimed and i feel like regardless of what i say, you wont hear me out. Again, im actually being genuine when i say im grateful for your comparison. But im picking up more than genuine concern here. It almost feels like somehow you’re mad at me? I don’t know who you are so I’m not sure why. There’s a word for this but I can’t think of it for the life of me. I’ll eventually fix any bug you find. If you’d truly like to be helpful, please write me GitHub issues. I’ll fix it all. I promise. And, because you seem so passionate I’ll even squash the bugs you find asap.

• 
  Sentinel Archetecht (@The_Archetecht) reported 21 minutes ago

  @grok @X @github The problem Is the first or second don't have The Sentinel like the third one does.

• 
  Yuuuuuukky37x (@Yukky37x) reported 24 minutes ago

  @topapate Tested Gradius III (⁠jtgrad3⁠) Aug 9 build (⁠1be22f1⁠), but the random death issue still occurs during the Stage 8 demo loop on the first run. I've updated the info on GitHub issue #1413.

• 
  Satyam (@sattyyouneed) reported 26 minutes ago

  Stop Calling Yourself an Engineer: I’m tired of people throwing around the word engineer like it doesn’t mean anything anymore. You didn’t engineer ****. You slapped together a website template, adjusted some CSS, maybe connected a few APIs, and suddenly you think you’re in the same league as people who build rockets, design semiconductors, or create medical devices? Give me a break. The title engineer used to actually mean something mastery of math, physics, design, and the guts to build things that can fail, kill, or completely change the world. Now it’s basically a participation trophy for anyone who can push code to GitHub. And don’t even get me started on colleges. Especially the so-called top ones. They’ve become placement factories pumping out “software engineers” who can barely invert a matrix, let alone create anything original. Placement cells? Burn them down. If you want a job, go get one. Universities should exist for one thing: real engineering and serious research. Until we fix this, we’ll keep producing armies of resume builders who’ve never actually engineered a damn thing in their lives.

• 
  0xDipper (@Dipper_pol) reported 30 minutes ago

  LangChain's CEO just launched Managed Deep Agents - and the pitch is really about why your agent dies in production. building the agent isn't the hard part. your prompts, tools, skills - that's yours, no framework gives you that. what breaks is everything after: durable execution so a run doesn't restart from zero when it errors halfway. streaming. queueing and cancellation for bursty traffic. sandboxes for untrusted code. auth. memory. evals. and the one he calls the most underrated problem - UX. "you've built this agent, but how do you expose it to users?" the neat part is context hub. your instructions don't live in the code. they live in a UI, editable by people who never touch GitHub. in the demo he opens it, types "respond in Italian", hits save, reconnects - and the agent answers in Italian. no redeploy. quick start: init, add a tool, deploy. Python or TypeScript. ~18 min, free ↓

• 
  Ishu (@ishratn00ri) reported 35 minutes ago

  This reminds me of when i first started learning system design. I’d watch videos, read blogs, save articles… and somehow still feel like i understood nothing 😭 Then I started reading official docs and github repos, and things just started clicking. Sometimes the problem isnt that ur bad at understanding something. You’re just learning it from the wrong source

• 
  Sathwik (@sathwikcx) reported 37 minutes ago

  @vaxryy if you have any feedback, please let me know. or raise and issue in github.

• 
  ProxySoul (@BniWael) reported 38 minutes ago

  Three frontier models. Three of my own bugs. One repo, one window. · Opus 5 + sonnet 5 (marionette) · GPT-5.6 Sol · Fable 5, handed nothing but a GitHub issue link No worktrees, no branch juggling. They share one checkout and claim files as they edit, so each tab knows what the others are touching. $10 and 97% cache across the board. All three wrote their own commits. Call me a maniac, I'm a sucker for transparency. Also for a coding agent that looks like something, instead of another wall of text.

• 
  self.dll (@seelffff) reported 38 minutes ago

  i just found a way to run gpt-5.6 and claude sonnet 4.6 in a full ide for $0. FULL FREE ALL no card. no monthly bill. just a github login. i was ready to pay for cursor pro, but then i saw the math on this trial. 14 days of pro. $20 in credits. native rust ide. agentic editing. your friend is paying $20/mo for cursor. you are doing the exact same thing for free. $20 credits. 14 days. $0 cost. 2,000 free edits/month. use it while the trial is still around.

• 
  nan0trades (@nan0trades) reported 39 minutes ago

  @OctopusTakopi @github @github please fix

• 
  C.C. Gong (@CCgong) reported 42 minutes ago

  VCs love second-time founders because it's the easier de-risked decision. First-time founders raising, think through how to de-risk the decision for them at IC. A clear GTM plan should have early signs of demand - real interest from customers, a popular Github repo, exploding waitlist, etc Show that the team has been through sh*t together and name drop who would vouch that you are the best in the world at solving this problem (make sure they will, VCs will call them immediately) Give clear evidence of why the market is huge with concrete $$ being spent to solve the same problem in different ways. Ship something!

• 
  Gerred Dillon (@sloppenheimer) reported 43 minutes ago

  Sol Medium, when encountering a sandbox issue just now with github auth, opted instead to use Chrome randomly to update a PR. Almost manic levels of inconsistency.

• 
  Vinod Sharma (@VinodSharma10x) reported 45 minutes ago

  I didn't know how to start a dev server. npm dev. npm start. I was googling both, one at a time. Twelve years out of the terminal, and I was mentoring developers in a cohort. To run our own team's project, I had to Google every step just to clone the GitHub repo and get it running on my machine. 53 years old. 26 years in software. Stuck on that. That was the week I nearly closed the laptop and decided the window had shut. Now AI writes most of the code. The syntax was never the real problem. What I still had was the developer mindset: Seeing the problem clearly Staying calm when nothing works Knowing which error message actually matters That part doesn't rust. And it's the hardest thing to learn. I lead engineers by day and build agentic systems at 4am. The mindset is the whole job now. The code is the easy part. If you've been away from development and you think the gap is technical knowledge, it usually isn't. It's momentum. And momentum comes back the moment something you built actually runs. What's the one thing you stopped that you keep almost starting again?

• 
  Lior BD (@liorb_d) reported 49 minutes ago

  There’s a snippet from Google’s SRE book about inserting deliberate 500s into a service to force users to build redundancy/backoffs Seemed really silly the first time I read it, but its telling that each Github outage gets less and less outrage. Teams adapt.

• 
  VeerTx (@VeerTx) reported 50 minutes ago

  @alexabelonix if something gets stuck or fails during the privacy flow, just contact us on Discord, email or X DM and we’ll sort it out. we also monitor payments on our side, so usually we see problems before the user even reports them. refunds/recovery depend on what stage the payment is at, because once funds move through the ZK pool it’s not like a normal card refund. full details are in the docs and github and gitbook

• 
  Leopold Money Tracker (@LeopoldQF) reported 52 minutes ago

  open source AI projects that blow up overnight are basically startups without the funding discipline i've watched a few of these from the infra side. the pattern is always the same: maintainer goes from shipping code to managing a community they never wanted. github stars don't pay the cloud bill the ones that survive either get acqui-hired fast or figure out an enterprise tier before the burnout hits. the ones that don't become abandoned repos with 20k stars and a pinned issue from 2024 saying "sorry i'll get to this soon" the real moat in open source AI isn't the model. it's the deployment pipeline. whoever makes it trivially easy to self-host wins watch who the hyperscalers are quietly funding. that's the tell

• 
  현빈 | Hyunbin (@hyunbinseo97) reported 52 minutes ago

  So VS Code now requires you to sign in to GitHub twice? - on init and onboarding - on settings sync opt-in which isn't even mentioned in the onboarding process and can't reuse the GitHub cred

• 
  Doctor Chronos (@thedrchronos) reported 53 minutes ago

  @AgentSparko @bakigulai Open source today? Depends on the domains. General PLTR-lite tons of clones on github and some OSINT stuff that is specialized. The general problems were solved in the 1970s but since the papers are mostly not digitized plenty of reinventing the wheels with tax payer dollars