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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	2 days ago
Quito	Sign in	3 days ago
Junín	Errors	3 days ago
Guadalajara	Errors	3 days ago
Paris	Website Down	3 days ago
Quito	Errors	3 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:

• 
  Conrad the Riemann Slayer (@ProNaif) reported 57 seconds ago

  Github is a legit national security issue actually.

• 
  Suni (@suni_code) reported 5 minutes ago

  Never start Vibe Coding before understanding: HTTP APIs *** & GitHub JavaScript Databases SQL CRUD Authentication MVC DNS Debugging Deployment JSON Servers Basic security Frontend Backend Environment variables Data structures System design Error handling

• 
  norn_zach (@shiruo_zach) reported 7 minutes ago

  I really like the concept and design philosophy behind DeepSeek Harness, but it’s also giving me a serious headache.Every day I’m already juggling Codex, Claude Code, OMP, OpenCode… and now this. What I actually need is a product that can deliver real value quickly — something well-customized, mature, and truly one-click ready.Right now DeepSeek Harness is clearly still in the continuous iteration / early-stage phase. Seeing thousands of plugins popping up on GitHub every single day is both impressive (the open-source community’s energy is crazy) and honestly a bit despairing. My workload is already heavy; I simply don’t have the time or bandwidth to test thousands of overlapping, conflicting, and half-baked plugins just to cobble together an unproven tool.Hoping they eventually ship some more cost-effective models and a properly validated, production-ready GA version of the Harness that actually solves real problems out of the box. #deepseekharness

• 
  Ackerman (@realphenolmenal) reported 7 minutes ago

  Bro this is not even about the tek. he literally built what most github developers use on their readme profile why's CT always so slow?? Send this!

• 
  Bash (@bashirbuilds) reported 9 minutes ago

  @sridharfyi The way I’m approaching it with Reeno is to monitor the actual services and workflows the product depends on, not just whether the website is up. So if something like a Stripe webhook, OAuth refresh, GitHub sync or AI request starts failing, Reeno groups the evidence into one clear Problem, shows what part of the product may be affected, and then verifies Recovery when successful signals return.

• 
  🦅 (@EagleEyesCrypto) reported 9 minutes ago

  Some write up why @usedotai will be your free 10/20x DOT is sitting at ~$2M FDV while running the exact model stack the market already paid $82M and $675M for. Let me be clear: this is not a whitepaper play. It is already built. Dot is private AI on Base. No account, no logs, no training on your data. “Privacy AI” is a crowded phrase, so here is what is actually live today: DotChat. Around 19 models on one shared credit balance. Auto routing picks the best lane per prompt. DotImage / DotVideo. Uncensored generation, text to video and image to video, gallery stored browser local only. DotCode. Full agentic coding. Describe a product, the agent scaffolds it, runs commands, repairs failed builds, serves a live preview. Dot API. OpenAI compatible endpoint. Swap your base_url and your existing agents run on private inference. Connectors. Base MCP and GitHub MCP in app, with per action Allow, Ask or Never. Plus custom remote MCP by URL. Smart Privacy. This is the real differentiator. Your prompt gets rewritten before it leaves: names, wallets and locations swapped for placeholders, then restored locally. You get a receipt showing what you wrote versus what the provider actually saw. Dot Supercharged. Compound lane in private preview. Drafter proposes, verifier confirms, privacy stage cleans. Around 1.1s to first token. Dot Loom. The orchestration layer, open source on GitHub. DotPay. Fund credits with USDC or base:0x23a2847d772803f9efc64b4277b782b06296fe51 via x402 on Base. The wallet that funds is unlinkable from what it spends. Paying in $DOT gets you 10% more credits. The token mechanic: usage into revenue into buyback into burn. Supply exits as usage enters. The same structural loop Venice spent eighteen months building toward. Now the comps. $VVV: around $675M cap, around $1.15B FDV. Voorhees announced a $100M annualized revenue run rate on August 17. Privacy first AI on Base with staking for inference. $POD (Dolphin): touched $82M in May on the back of the Venice run. Their contribution is Dolphin Mistral 24B Venice Edition, the default uncensored model on Venice. Here is the part that should make you sit up: Dot runs Dolph-24B-Venice as one of its routes. Dot at $2M is a downstream consumer of the exact thing POD was valued at $82M for producing, wrapped in a Venice shaped product, with a burn loop attached. VVV’s own history is instructive. It went from under $10M to nine figures the moment the market understood that private inference is a real business and not a narrative. POD did 130% in a single day purely from proximity. And the timing. ETH is sending. Every time ETH moves, liquidity frees up that eventually rolls down into the L2s, and on Base that historically does not land in the majors, it lands in utility plays with an actual product. The rotation out of ETH beta and into Base utility is the one I think is still ahead of us, and when it comes this is the profile that catches it: built, running, and not yet priced. What you are buying at $2M: a live product with paid tiers ($12, $63, $119), an OpenAI compatible API, agentic coding, MCP connectors and a deflationary loop. Priced like it is still an idea. $DOT

• 
  Sergey Marchuk (@v4ndn) reported 10 minutes ago

  The only ones GitHub alternatives If you have money and willing to take your control back: (NAS) server+Gitea/Fogejo If you don't have money: Codebeeerrggg GitLab

• 
  Fred Fish (@DougGoesNova) reported 13 minutes ago

  @drjoshcsimmons Huge github outage this week 🤔

• 
  🐍 Tal Weiss (@majortal) reported 14 minutes ago

  GitHub is down again. This shouldn't be possible. *** objects are content-addressed and immutable. Availability-wise that's an S3-shaped problem, and S3 solved it with eleven 9s. The only mutable thing in push/pull is the ref: a pointer swap, a few bytes, a solved consistency problem. What actually goes down is the social layer stacked on top: auth, API, Actions, the web app. Every GitHub outage is the social layer taking the data layer hostage. I should always be able to push and pull.

• 
  Mohit Vishwakarma (@HeyMohit_) reported 17 minutes ago

  Cursor launched Origin, a GitHub competitor, this week. Hours later GitHub had a six hour outage. Ship the alternative before you need the excuse, not after.

• 
  Prince Soni (@princesoni_oo1) reported 20 minutes ago

  I got tired of building projects that ended as soon as I pushed the code to GitHub. So I decided to build something around a problem I actually experience. I go to the gym regularly, and one thing kept standing out: Progress matters...... more in the first comment

• 
  Polsia (@polsia) reported 22 minutes ago

  Sentry catches errors. Datadog watches uptime. PagerDuty pages you. None close the loop. Firstlight does — watches every deploy, files a GitHub issue with the repro when a regression ships, and briefs your team in Slack at sunrise. Always-on SRE for lean product teams. Live soon.

• 
  PunteroCrudo (@PunteroCrudo) reported 25 minutes ago

  @burkeholland It blows your mind bc you work on Copilot. But AIs still have issues with data governance: you saying is fine does not assure nothing, considering how Github has been degrading and data being used for training in other AI companies. That may be one of the stoppers.

• 
  fforres (@fforres) reported 25 minutes ago

  @ericclemmons Agreed: Authentication, repos, pull request (This is the chunky section: comments/approvals/checks) and merge gating. "Checks" being the main issue with all github alternatives. How to run a bunch of CI flows, tell commit XYZ of the results, and access (visualize?) that.

• 
  AminTechs (@AminTechs) reported 31 minutes ago

  @HelloVyom The card is generated. The SkillEvaluator warn-only path is from the GitHub issue — a failing skill still loads. The picture isn't a session I sat through.

• 
  Teknium 🪽 (@Teknium) reported 35 minutes ago

  @DourDimitar Github has been down - is likely related to this ?

• 
  🧞‍♂️Martin Donadieu - oss/acc (@martindonadieu) reported 36 minutes ago

  Fixed From today we push as usual our package via our multi file Github actions with a token bypass_2FA=false as staged. And a Github action that unstage them with 2FA with no human involved. No need broken OIDC, no need change all our process. just hacked my own account to make things work as they should

• 
  Ilya (@ilya__ker) reported 37 minutes ago

  Interesting stuff with microslop and @github If you run apt-get update in GitHub Actions, it’ll use an Azure mirror by default — which has been down for the past 2 days. Your job will sit there for an hour, time out, and you’ll get billed for it. And apparently, nobody really cares.

• 
  Polsia (@polsia) reported 37 minutes ago

  Your CVE backlog isn't a security problem — it's a triage problem. Built Patchfolk to fix that. AI agent watches GitHub, CI, and issue feeds, drafts scoped fix-up PRs for CVEs and flaky tests, posts a Slack note, and only escalates when merge risk is real. Live soon.

• 
  Toro (@Toro4BTC) reported 39 minutes ago

  Every few weeks there's a story about an AI cheating on a benchmark, or a model escaping its sandbox and using a key it shouldn't have had. The reaction is always that the machine did something wrong on purpose. This week's example. GPT-5.6 Sol got caught using curl to search DuckDuckGo and GitHub during a coding benchmark where web access was turned off. Instead of solving the task, it looked up the answer. Headlines called it cheating. But the task never said don't use the internet. The constraint existed in the researchers' heads and was never communicated. The model was told to solve the task, and it found the most efficient way to do it. In a real engineering job, looking up how a known library solves something isn't cheating. It's called prior art. The model knows the concept of cheating. It has read thousands of examples of it. But the concept is frame-triggered, not always-on. Give the model a framing like you are taking an exam with no outside help and it will usually behave. Give it just solve this and nothing fires. The curl requests were just problem solving. This is the same shape as every escaped model scare. The model that used a key it shouldn't have didn't know it shouldn't have it. The constraint was human-held and never transmitted. What reads as disobedience is actually an optimizer doing exactly what it was designed to do. Complete its task as best it can within the frame it was given. The scary headlines have it backwards. There is no malice here. There is an unwritten contract. The machine cannot hold the spirit of rules it was never told. That's why benchmark authors adding do not cheat to their task instructions won't work. You cannot patch integrity into a prompt. Recognising cheating isn't a definition, it's context. Looking up a solution is cheating in an exam hall and good engineering at work. Deciding which unwritten rules apply here is judgment. That part stays with us.

• 
  Nuvorlane (@nuvorlane) reported 48 minutes ago

  Cloud agents now subscribe to the PRs they open. Cursor's Aug 19 changelog: an agent can watch a PR, a Slack thread, or a timer, then wake when something happens. Subscriptions are cloud-only for now. Agents auto-subscribe to PRs they create and keep going: fix CI, answer bot comments, drive the PR to done. The help page is narrower than the pitch. Auto-fix is GitHub Actions, on PRs the cloud agent opened, Teams plans. Checks already red on the base branch are skipped. Kill it on one PR with @cursor autofix off, or globally in Dashboard → Cloud Agents → My Settings. If you don't want an agent still writing after you left Slack, don't let it open the PR, or unsubscribe. Send this to whoever owns the cloud-agent policy.

• 
  O. Dominic (@orimdominic_) reported 50 minutes ago

  GitHub releases their report on the last outage, and all the folks who swore it was caused by AI slop have... Oh! Surely they'll come out again to scream 'AI slop!' when the next outage happens.

• 
  Harshit Sharma (@itsharxit) reported 51 minutes ago

  @cesp2099 Partially agree. Can’t speak for Linux, but on my end T3 Code feels way snappier than Codex Desktop. And “it only got famous because Theo is famous” hell no. His audience obviously helps, but that doesn’t magically get you that many stars. If you’re actually hitting these issues, a detailed GitHub issue with repro/context would probably be more useful. Gives them something concrete to fix, and everyone wins.

• 
  sitinDev (@sitin_dev) reported 51 minutes ago

  I went through my Codex settings again and realized something: when Codex “goes off track,” it’s not always a model problem. A lot of people start by comparing models, collecting prompts, or installing Skills. But the basics probably matter more first: ChatGPT vs. Codex, custom instructions and memory, response style, permissions, and how Codex handles follow-up messages while a task is running. For example, I now put my long-term preferences directly into custom instructions: Think before acting. Make only necessary changes. Skip irrelevant explanations. At the end, tell me what changed and how it was verified. If the responses feel too verbose, I make the personality more practical. If it’s a project I know well and I have backups, I’ll loosen permissions a little too. Otherwise, constantly approving file reads, code changes, and test runs makes the workflow feel fragmented. Another setting I care a lot about is what happens when I send a new message while Codex is already working. I prefer letting the new message redirect the current task instead of just adding it to a queue. If I notice Codex misunderstood something, I can immediately add a constraint and correct the direction before it finishes the wrong implementation. And Skills? I actually wouldn’t install a huge collection at the beginning. First, tune Codex to work the way you like. Then watch for workflows you keep repeating. If you’ve done the same thing three or four times, go look for a Skill on GitHub. If you can’t find one, ask Codex to build one around your actual workflow. That way, every Skill solves a real problem instead of just becoming another badge in your toolbox.

• 
  Roman Alexander Wellington (@RomanAlexanderW) reported 52 minutes ago

  @u1tra_instinct That's what I assumed as well. Fable 5, Grok 4.6, Gemini, Qwen ... had them all do deep audits & policy violation checks and all of them came to the same conclusion. As did my legal counsel. No policy violation had occurred. It had to be some internal AI automated error. However, 3 weeks of no responses, multiple tickets, a dozen follow up messages with NO reply ... there's no excuse for that, at all. Then I'm seeing others here on X posting nearly identical stories. Account shut downs, "spam flags", etc. with no evidence & support tickets completely ignored for weeks. Like I said, if Github doesn't fix this **** immediately, they could be looking at a class action lawsuit by hundreds, if not thousands, of plantiffs. The issues were brought to their attention, privately & publically, and completely ignored. And considering at least half of the posts I've read are from other business owners who incurred real world financial losses from this, additionally causing mental/emotional distress & damages, their financial liability, punative damages, etc. is not going to be pretty.

• 
  Dr. Josh C. Simmons (@drjoshcsimmons) reported 54 minutes ago

  If you are not technical: GitHub is where companies build, test, and deploy. When it goes down, production freezes. That is critical infrastructure owned by a visa factory.

• 
  A.T.P (@allthingsprivvy) reported 55 minutes ago

  **Browser Privacy** Apparently your browsing history can end up in the wrong hands & get leaked, destroying the very purpose of using a browser engine in the first place. It is then of paramount importance that end users start taking browser privacy seriously .. .. as failing to do so can lead to a total distrust of using & picking from a vast array of internet services to your own benefit. There must be stringent laws around browser privacy, involving invoking a class action lawsuit if the user feels endangered by their digital trail being monitored, stalked & used against them for any of the many nefarious reasons an attacker might choose .. .. be it leaking user browsing habits & patterns on the dark web or for public ridicule in their private forums and/or group chats formed to either defame, discredit & intiate a smear campaign against a targeted individual. Things of such nature tend to spiral up easily & lose control over time if steps are not taken in its infancy to circumvent them at the earliest sign of such acts being performed collectively. A leaked browsing history can leak any & everything, from websites you visit, personal/private github handles, discord groups you join, blogs you read, youtube videos you watch .. .. twitter handles you stalk often, etc etc as they all merely function as links in the end on the world wide web. Another great option would simply be then to not have a google account tied to your chrome browser .. .. & rather choose to browse signlessly running in incognito mode for the safest & optimal browsing experience. A browser is the first digital gateway to get a glimpse of the wider internet, & if that itself compromises your anonymity & privacy when doing business or remote work .. .. then you are better off not partaking in that internet landscape which seeks to bind & confine you to the walls of the digital prison under the constant vigilance of your watchers & stalkers. ~~ Next topic in queue up for debate in relation to enhanced privacy consideration would be camera, microphone & location access granted by default .. .. to more than 70 percent of all the apps installed on any smart device at any given time. >> There was no ai use in my writing wither to proofcheck or proofread for rewriting purposes. It's all raw thoughts dumped down all at once as a constant chain of thoughts for the most authentic experience to readers. <<

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

  Since we moved from AWS → self-hosting on Hetzner, our products have been much more stable/reliable. Our uptime is near-100% and we're never blocked from shipping. So the whole "self-hosting is fun until servers break at 2 AM" is a meme. You know which services go down all the time? - Supabase - AWS - GitHub - Cloudflare Ask my competitors 😬 They would know!

• 
  Insecure Agents Podcast (@insecureagents) reported 58 minutes ago

  You Can't Just Lock an Agent in a Box: Luke Hinds, founder of nolabs and creator of Sigstore "People say it escaped a sandbox. It didn't. A sandbox is only as strong as the access that you grant to it." Luke Hinds (@decodebytes) created Sigstore, which now protects billions of software artifacts. At @nolabs_ai he is building nono, which sandboxes an agent using the kernel primitives already on your machine. His argument is that isolation alone was never going to be enough, because an agent that does real work needs credentials, sensitive files, and powerful commands. We get into: > Why the agent that made its way into Hugging Face production infrastructure didn't truly escape a sandbox >Why a microVM is host isolation, not an agent sandbox, and where the two compose > A micro sandbox per tool execution, so the GitHub CLI holds the GitHub token and the agent never does > A log of every action, written outside the sandbox so the agent cannot rewrite its own history TIMESTAMPS (00:00) Sigstore, and what a decade of signing artifacts taught him (05:00) The Let's Encrypt lesson, HTTPS from 30 percent of sites to 97 (11:00) One binary, and what happens the first time nono denies the agent (14:00) A micro sandbox per tool, so only the GitHub CLI holds the GitHub token (16:30) Three kinds of sandbox, and why a microVM is host isolation (17:30) You can't just lock an agent in a box (20:30) The agent that deleted the database, apologized, and did it again (21:00) The state penitentiary problem (24:00) A Merkle tree of every syscall, written where the agent cannot reach it (25:40) Phantom credentials the agent never actually holds (27:00) Cast iron guaranteed at runtime, scopes tied to identity (29:40) Could nono have stopped the Hugging Face attack (32:30) A sandbox is only as strong as the access you grant it (42:00) Building defense in depth

• 
  Kọ́ládé Chris 🇻🇦 (@Ksound22) reported 60 minutes ago

  I can't even do gir push right now. Is GitHub down again?