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

Live Outage Map

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

City	Problem Type	Report Time
Ahmedabad	Errors	5 days ago
Delme	Sign in	5 days ago
Lyaud	Website Down	5 days ago
Catania	Errors	8 days ago
Inverness	Website Down	20 days ago
Quito	Sign in	21 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:

• 
  catman (@catmanyau) reported 5 minutes ago

  @CricTalk29 for me, losing Cursor would hurt most because it sits directly in the editing loop. would the vote change if github outages were limited to code hosting but issues and reviews stayed available?

• 
  CATIRL 🏳️‍⚧️ (@CATIRL_9) reported 7 minutes ago

  @mminhamina Google GitHub "open grind", solves your problem

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 10 minutes ago

  @openclaw @github Fix your updater and I might give it another shot.

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 13 minutes ago

  Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

• 
  Asterix (@Asterix54907294) reported 14 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  LLL (@triplellltrbl) reported 15 minutes ago

  You know it's so funny to me That in today's age there are so many people that are just straight up copying workflows, AI automations or GitHub repos Without even thinking twice about what the workflow actually does or how it works They just watch some video, see the output, think, "Oh that's cool. I want that," and then try it Then when it doesn't work they get angry, upset, and say that AI is crap or prompting isn't real The issue wasn't the system or the prompt It was a fact that the system wasn't made for you and you don't actually understand it

• 
  Rituraj (@RituWithAI) reported 16 minutes ago

  🚨 Someone built a skill that makes AI-written text sound human again. Not a spinner. Not a paraphraser. A systematic rewriter that knows exactly why AI text sounds like AI — and fixes it. It's called Humanizer. 35 patterns from Wikipedia's "Signs of AI Writing." Two-pass rewrite. Shows its work before giving you the final version. Here's the problem it solves. You use Claude to draft something. The output is accurate. The output is useful. The output sounds exactly like an AI wrote it. "Nestled within the vibrant landscape, this pivotal development serves as a testament to..." You know the voice. Everyone knows the voice. And everyone is getting better at spotting it. Humanizer runs that text through 35 specific patterns that WikiProject AI Cleanup identified as the telltale signs. Inflated importance. Shallow -ing analysis. Overused AI words. Em dashes everywhere. Forced groups of three. Fake-candid openings. Answering objections nobody raised. Every pattern. Flagged. Fixed. Here's what one command does. It shows you the first rewrite. Then a short critique of anything still sounding artificial. Then the final version. You see exactly what changed and why. Here's the wildest part. Voice matching. Paste two paragraphs of your own writing before the AI text. Humanizer follows your rhythm, word choice, punctuation, and deliberate quirks instead of its default style rules. The output doesn't just sound human. It sounds like you. One command to install 16 contributors including Claude itself. 4 releases. MIT License. The skill that makes AI writing disappear. 100% Open Source. GitHub link in the comments 👇

• 
  Fofer (@foferxxx) reported 17 minutes ago

  @AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? It’s been 404 for days. Is there a story there?

• 
  Convequity (@convequity) reported 17 minutes ago

  Snyk is a clean postmortem for what happens when a security tool lives inside the coding agent’s loop. The product was mostly scan-and-warn. Find the issue, comment on the PR, suggest a fix. Blocking the merge usually sat in GitHub, not in Snyk. Bigger platforms smothered it. $PANW, $CRWD, and Wiz pulled AppSec into the bundle the CISO was already buying. GitHub was the main developer surface and put scanning where the code already lived. Then coding agents arrived and delivered the final blow. A lot of that scanning became something the agent could just do. Growth held up for a short while after the COVID/cloud tailwind. Then it decelerated hard. This is the same lens we use in Convequity’s SaaS Agentic Survival Evaluation Framework. The PANW, CRWD, and FTNT reviews go up on Convequity in a few days.

• 
  Dhanji Bhagat (@BhagatDhanji) reported 18 minutes ago

  Devs, what's your workflow? Create an issue first, then fix it OR just fix the bug and push directly to GitHub?

• 
  paulrodturner (@paulrodturner) reported 19 minutes ago

  @supabase Is anyone else having issues logging in via Github?

• 
  Shanica North (@KickAssShanica) reported 19 minutes ago

  @ArcyloOfficial Get comfy! For me, my Gmail is a connector. This is OAuth into my inbox. Grok can: • search and read mail (body, headers, attachments) • draft replies • send / reply / forward if you grant write/send • label, trash, organize Base hook is often read-only. Send is an extra permission you click on purpose. If you connect it, the bot is sitting in the same box as bank alerts and 2FA codes. That is the whole risk. You can revoke anytime. Grok Bot can also skip my inbox and get its own address (AgentMail / similar plugins). Then it sends and receives from something@….agentmail.to, not from you. I use that if I want an agent that emails people without reading my personal mail. My GitHub OAuth into the GitHub user I sign in as. With the scopes I approve it can: • read public and private repos that account can see • search code, list branches, summarize PRs • open/update issues • create branches, push files, open/review/merge PRs • delete files if write is on Private repos work only if I granted repo (or equivalent) at connect time. Safer pattern: tell it to branch + PR, not push straight to main. Same revoke page. What it cannot do by default • It does not get your password. • It does not stay logged in if you disconnect the connector. • It does not magically see my GitHub orgs I never authorized. • Connecting email does not connect GitHub, and the other way around. Practical rule for me Do not hook personal Gmail if that inbox has 2FA and money mail unless you want an assistant reading it. GitHub is useful if I chose to still keep repos, ask it to show the diff before any write. If you only wanted “what does this button do,” that is the button: it is not a viewer badge. It is a key you can take back. This is what I’m experiencing with learning to use it. It’s different and I’m starting to like it.

• 
  Uptimus (@UptimusApp) reported 23 minutes ago

  Sep 02, 2026 at 13:29 UTC: Semaphore reports that periodic authentication failures with GitHub repositories are linked to a wider issue affecting HTTPS operations.

• 
  Ravi Prasad (@ravikp7) reported 27 minutes ago

  Big NO to Github hosted CI runners for personal projects now. I have setup a self-hosted github CI runner on a spare laptop running ubuntu server. Been running it for 10 days and I did some calculations, for my usage if I run it on Github runners, it'd cost me around 200$ vs < INR 100 on electricity (local setup) monthly.

• 
  OverlyPositivePatriot (@JBrowsing2023) reported 29 minutes ago

  As a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.

• 
  rajabi17270.eth (@rajabi17270) reported 34 minutes ago

  @SeismicSys An Ethereum engineer opens an install page expecting a binary download that finishes before the coffee does. Seismic asks for Rust and cargo first, then budgets five to twenty minutes for the build. That gap is the most honest line on the page: you are not installing a tool, you are compiling a fork of the execution layer on your own machine. Three binaries come out of sfoundryup. sforge as the testing framework, sanvil as the local node, ssolc as the compiler. Each shadows a Foundry tool by exactly one letter, and the docs give the mapping outright: forge becomes sforge, anvil becomes sanvil, cast becomes scast. The s is not decoration. The s is a namespace. The s is the migration guide, compressed into one character and carried from the type system all the way up to the binaries sitting on your PATH. Why a fork and not a plugin is the question the install page answers without asking it. Privacy on Seismic lives in the type system, so solc had to become ssolc to understand suint256 and route it to CLOAD and CSTORE instead of SLOAD and SSTORE. Because the compiler changed, the build harness that invokes it changed with it. Because the emitted bytecode carries opcodes standard revm does not implement, the local node had to be rebuilt to execute them, and because each storage slot is a value paired with an is_private flag, the CLI that queries storage had to expect a different answer than Ethereum's. Four forks, each one forced by the layer beneath it. Not a toolchain that was extended. A toolchain that had no choice. The installer itself carries a detail worth reading twice. It is fetched through the GitHub Contents API with an Accept header of application/vnd.github.v3.raw, from the seismic-foundry repository, at ref equals seismic. That ref is a branch name, and a branch name tells you the maintenance posture: the fork lives beside upstream rather than in a codebase that has stopped speaking to its parent. A rebase relationship, not a divorce. You source your shell profile twice during setup, once after the installer lands and once after sfoundryup finishes. Two separate PATH mutations, because the thing that installs and the thing installed arrive at different moments. What survives the fork is more interesting than what changed. sanvil serves localhost:8545 with pre-funded accounts, and the deployment example uses the same well-known development key Foundry users already have in muscle memory, address 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266. sforge init, sforge test, sforge script with rpc-url, broadcast and private-key flags: identical surface, identical ergonomics. Your scripts port by find and replace. Which makes the two manual steps on the page the most revealing part of it. The first is the editor. The docs say that if you already have the solidity extension installed, you have to disable it while writing Seismic code. That is not a preference. suint256 is not valid Solidity, the s literal suffix is not valid Solidity, and two grammars cannot both claim authority over the same .sol file. The language is a superset. The highlighter cannot be. The second is sforge clean, listed as optional, run inside an existing project's contract directory. Here the collision is on disk: cache and out are not namespaced, so artifacts that solc produced sit in exactly the paths ssolc writes to, which means the failure mode is not a build error but a passing test against bytecode that never saw a shielded type. Optional only if you have no history. The requirements are narrow and stated plainly. x86_64 or arm64, macOS, Ubuntu or Windows, with other Linux distributions marked as possibly working but not officially tested. Note what that list provisions and what it withholds. It gives you the language and the opcodes locally. It does not give you the hardware boundary, since the network's nodes are the ones required to run inside Trusted Execution Environments while sanvil is described only as a local node in the shape of anvil. Local tests can prove your casts compile and your shielded storage routes through CLOAD correctly. They cannot exercise an enclave. So here is the part nobody plans for. Everything that could take the s prefix did, and one character kept two toolchains from colliding across an entire PATH. The editor extension could not take it. The build cache could not take it. Those two are precisely where the page stops describing and starts instructing, which means the friction in a Seismic setup was never in the fork: it is in the two surfaces a naming convention could not reach.

• 
  XhiMatty (@mychaelmatty) reported 36 minutes ago

  a Sept 2 run. My first thought was “Why did it stop running?” I checked the #YAML file, #python file, GitHub Actions, even inactivity issues. Turns out it was still daytime. The Sept 2 run is yet to happen (at night). Nothing was broken.

• 
  The Oracle (@scientist1q) reported 37 minutes ago

  when my Oura ring detects a cortisol spike from a GitHub Actions failure, Hermes (Fable 5.1) detects it and sends a 900 word root cause analysis, Hermes dispatches the work to my 12 Grok Bot employees, The Chief of Operations bot approves the fix while im watching rezero

• 
  Tlon (@tloncorporation) reported 42 minutes ago

  1/ Your agent can now publish to the open web from Tlon Messenger. The page is served by your own server. No platform (ie Substack, GitHub, Medium etc) sits between you and your readers. All publishing a note to the web from Tlon Messenger takes is pressing a toggle. The page lives on a server you own. Here's how:

• 
  small_j (@a_small_j) reported 43 minutes ago

  @smalldocs_org recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 44 minutes ago

  @github A repeatable --attach flag turns CLI reports into reproductions: inline screenshots in issues mean a bug gets fixed in one pass instead of two round-trips for context.

• 
  Vigneshwer Ramamoorthi (@vigneshwer_ram) reported 44 minutes ago

  I keep thinking the “Android moment for robots” won’t come from a humanoid with the best walking demo. it’ll come when some cheap-enough piece of hardware gets into thousands of developers’ hands and people stop waiting for the manufacturer to decide what the robot is for. Zeroth just launched Bridge in China: 88 cm, ~13 kg, two-finger grippers, open motion-control APIs + SDKs, mocap/VR integration, and an OpenBridge ecosystem where developers can publish robot skills. the Geek Edition is reportedly ¥8,888. that price is the part that caught me. because once capable embodied hardware starts approaching laptop money, the experimentation surface changes completely. I want the Raspberry Pi phase of robotics. weird university projects. teenagers making terrible robot apps. researchers abusing the hardware for things it was never designed for. 500 GitHub repos implementing slightly different ways to pick up a cup. the robotics industry is understandably obsessed with getting robots into factories. I’m almost equally interested in what happens when we get enough robots onto developers’ desks

• 
  NAYAK (@Nayak__Ai) reported 49 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Harman (@itsharmanjot) reported 49 minutes ago

  Runs macOS on iPad to enable pro apps like Xcode and Terminal directly on the device This isn't a remote desktop or a streaming trick. It's real macOS booting on the iPad itself. It's called Virtual Mac on iPad. It runs a full copy of desktop macOS directly on Apple Silicon iPads, using Apple's own virtualization stack pulled out of macOS and rebuilt to load on iPadOS. Real macOS, on the tablet, offline. → Runs macOS 12 Monterey all the way up to macOS 26 Tahoe → Real pro apps on device: Xcode, Terminal, Final Cut Pro, Logic Pro, Pixelmator Pro → Metal GPU acceleration in every supported macOS version → Works with touch alone: tap to click, two-finger scroll, on-screen keyboard, no Magic Keyboard needed → Runs entirely on device, no server, no streaming, no account → Installs straight from Sileo in a couple of taps Here's the wildest part: It doesn't just match the desktop Mac virtualizers, it beats them. Virtual Mac is the first tool ever to run Final Cut Pro with OpenGL and OpenCL acceleration inside a macOS VM, something even UTM and VirtualBuddy running on a real Mac can't do. And it was built by a handful of community devs who extracted Apple's Hypervisor and Virtualization frameworks by hand, then used agentic coding to shim every missing API iPadOS didn't have. One honest note: this needs a jailbroken M1 or M2 iPad running iPadOS 16.3.1 or older. Apple removed the hypervisor from iPadOS 16.4, so newer versions are locked out for now. If your iPad qualifies, it's the closest thing to a Mac in a tablet that has ever existed. 1,423 GitHub stars. MIT License. 100% open source.

• 
  catman (@catmanyau) reported 49 minutes ago

  @sbilstein if GitHub is down, where does that push land first — and how do you handle conflicts when the repo comes back?

• 
  Bratah (@BratahFGC) reported 49 minutes ago

  There may be many bugs so feel free to leave any issues in the issue section github! I hope that this release can push forward the preservation or our beloved game!

• 
  Fox (@0xMfox) reported 54 minutes ago

  Gave an AI agent a month and GitHub access. Wanted to see if it could make money. The plan was simple. Point it at bounty-labeled issues, let it write the fix, submit the pull request, collect the payout. > Day 1 12 PRs submitted. 0 merged. 2 rejected. 8 just sat there ignored. Somewhere in that first week it also passed its own tests for a file that didn't exist. Wrote 25 tests for notification_service.py. The real file in that branch was called NotificationRoutingMiddleware. Confidently reported clean anyway. > Day 30 Looked completely different. 84 PRs submitted, 59 merged, $500-800 earned. Ran the agent for about $45 in API calls that whole month. Net somewhere around $455-755. Here's the part that stuck with me. Out of those 59 merges, 3 repos accounted for 90%+ of them. Every other repo it touched, zero merges, despite 30+ PRs going out across dozens of projects. Open source bounties follow a power law. Almost nobody merges your first PR. A few maintainers will merge your tenth without even reviewing it closely. That's what actually fixed the acceptance rate, from 24% up to around 70%. Not a smarter model, a scoring function that runs before the agent touches anything. Repos where it already has 10+ merged PRs score +40. Zero competing PRs on the same issue, +20. Five or more competitors already in, -20, skip it. Repos that closed PRs without merging before, instant -100, not even worth reading the issue. The fastest way to build the credibility that makes this work isn't code at all. Documentation translations sit at a 95% merge rate, barely reviewed, always needed somewhere. A handful of clean translations got the agent enough trust that maintainers started assigning it harder issues directly, no competition, no review queue. Spam version of this, submitting to every repo with a bounty label, burned through 30+ repos for 3 that ever paid out. Worse, it reads like exactly what it is to a maintainer watching the same account flood a dozen projects with mediocre PRs. Paid out by the hour, week 1 was rough, close to $5/hour, mostly setup and failed attempts. By week 3-4, once the scoring system was tuned and a few repos trusted it on sight, that climbed to $30-50/hour on the same kind of work. Bookmark this, scoring logic is worth stealing.

• 
  Yeemio (@yeemio) reported 56 minutes ago

  owlrunkit is on github now. public corresponding source for the npm package. issues go here.

• 
  Åsa-Nietzsche (@AsaNietsche) reported 1 hour ago

  @peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.

• 
  Jeremy Scott (@listwithjeremy) reported 1 hour ago

  @Coexisteven @Atropa_414 @atropa_pls Github is down I see......anywhere else we can read...I've been digging in it when I can since I was kindly introduced.