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

Live Outage Map

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

City	Problem Type	Report Time
Ahmedabad	Errors	3 days ago
Delme	Sign in	3 days ago
Lyaud	Website Down	3 days ago
Catania	Errors	6 days ago
Inverness	Website Down	18 days ago
Quito	Sign in	19 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:

• 
  Josh Hamilton (@nearbycoder) reported 54 seconds ago

  @theo If GitHub is down does it fall back to a cached version I’m guessing?

• 
  Wlad (@dawnhell_) reported 2 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  Harman (@itsharmanjot) reported 2 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.

• 
  Ayush (@roamer_on_X) reported 2 minutes ago

  my @github streak of 4 weeks ended today bcz I was busy playing fifa with my roommate. Tf, I hate this feeling. I literally had to solve one problem and just push it but I forgot to do it.

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 3 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.

• 
  Kahris (@chrissotraidis) reported 4 minutes ago

  @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

• 
  Alireza Bashiri (@al3rez) reported 6 minutes ago

  So I built a workflow around that ↓ 1/ Every enterprise project needs proper E2E tests. An agent should reproduce a bug, implement the fix, then generate screenshots or video proving the feature works. "The tests passed" isn't enough. I want evidence. 2/ Every feature starts as a detailed GitHub issue. Requirements, expected behavior, reproduction steps, screenshots, edge cases. Foundry syncs issues and converts them into Beads so agents keep the right context across long sessions. 3/ We only use Claude Code, Codex, or Grok at High/Max effort for implementation. A weak model with a cloud machine doesn't become an engineer. The model still needs enough reasoning to understand the codebase, test its changes, and recover when things break. 4/ Each agent gets its own isolated @asciidotdev Box. It can install dependencies, run the app, open browsers, modify code, execute E2E tests, and collect evidence without touching another agent's environment. One issue. One box. One clean workspace. 5/ When an agent finishes, Foundry checks: - Did the build pass? - Did the tests pass? - Did the E2E flow work? - Is there screenshot/video evidence? - Does it match the ticket? If anything fails, the task goes back to the agent. 6/ Green tasks move to staging. Only after passing staging do we allow supervised production deployment. Agents do most of the work. Humans still own the final gate. The workflow: Slack request → GitHub issue → Foundry sync → Beads context → Isolated Box → Claude Code/Codex → Build + test → Evidence collection → QA staging → Supervised production The stack: PostgreSQL for system state. Beads for agent memory. GitHub Issues for requirements. @asciidotdev Box for isolated execution. Claude Code and Codex for engineering. Each Box costs roughly $0.01-$0.05 per task. The expensive part isn't compute anymore. It's building the system that gives agents context, forces verification, and prevents bad code from reaching production. 100s of agents can write code. The goal is making 100s of agents ship code you can trust. That's what we're building with Foundry.

• 
  Fofer (@foferxxx) reported 6 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?

• 
  Gordo Polymath (@gordo_polymath) reported 13 minutes ago

  @github Please fix gh stack.

• 
  Anime0t4ku (@Anime0t4ku) reported 16 minutes ago

  @c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.

• 
  Martin Tobias (Pre-Seed VC) (@MartinGTobias) reported 17 minutes ago

  if you know any founders who are winding down, I may have a buyer of their github repos. DMs open.

• 
  Franco Valdes (@francoxavier33) reported 17 minutes ago

  llms rather burn 1m tokens to hand roll something with gaps and broken edge cases instead of just npm installing a 100k github star library how can I stop this?!

• 
  trulite (@trulite007) reported 20 minutes ago

  @Qromerolauro @mkliku @radius_browser Like a simple example would be have a list of my urgent GitHub issues and start an agent for it . Or a dashboard in which buttons start investigating issues. Of course I just need the webpage to be able to access radius tools. I m thinking secure way is an extension

• 
  Convequity (@convequity) reported 22 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.

• 
  Ares (@neko23423) reported 23 minutes ago

  I compared the latest OpenClaw vs Hermes Agent GitHub releases so you don’t have to. OpenClaw 2026.8.2 (Sep 1) vs Hermes Agent v0.21.0 (Aug 31). Not a feature-page remix. The actual repos. OpenClaw • 388,516 stars • 81,568 forks • ~86,300 commits • 6,070 open issues Hermes Agent • 239,503 stars • 48,930 forks • ~26,980 commits • 38,563 open issues Hermes is the smarter learner: skills from experience, cron that remembers, Bot Mode, hermes peer. OpenClaw is the personal-AI operating system: iMessage, iOS/Android, Linux companion, team Gateway, signed Foundation releases. The tell: Hermes ships `hermes claw migrate`. You only write a migrator for the incumbent. King in 2026: OpenClaw. Heir with the better mind: Hermes. If you’re picking a self-hosted AI agent this week, that’s the split. Bookmark this. The timeline is about to fill with takes from people who didn’t open either repo. OpenClaw vs Hermes Agent. Latest version. Real numbers.

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 26 minutes ago

  hey @Teknium @yeahfortommy please add the amd portal too even if tou have to send tommy into the AMD headquarters to get them to fix the links (you have to sign up for american then link through github, then you can access the models free, tommy needs to pull teeth but they have free api)

• 
  R 'Nearest' Nabors (they/them) (@rachelnabors) reported 27 minutes ago

  @Paul_Kinlan Honestly, the linear method helps. Think of it as having a never-ending trough of issues that agents can pull from. I don't even use linear. I just use GitHub with linear flavouring added

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 27 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.

• 
  Tlon (@tloncorporation) reported 28 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:

• 
  Vikas(Vik) Malpani| AI for US Real Estate (@vikasmalpani) reported 30 minutes ago

  GitHub just shipped an agent whose entire job is deciding when a human should look. It checks every open pull request every 15 minutes, and on almost all of them it does nothing. Sit with how strange that is. For a year the whole pitch for coding agents was do the work, review my code, ship the PR. This one's value is the inverse. It runs constantly and stays quiet, and the product is the small set of PRs it decides are actually worth your time. That is the shift people are missing. Once an agent can act continuously, the scarce resource stops being how much it can do. It becomes how much of that is worth a human's attention. An agent that pings you on every pull request is just faster noise. One that surfaces the three that genuinely need judgment is leverage. The honest problem is the deciding. Tune the filter too eager and it cries wolf until you mute it. Too cautious and it silently ships the one change you needed to catch. Getting when to interrupt a human right is harder than getting the work right, and nobody has a clean metric for it yet. So here is the bet. The next moat in agent products is not a smarter model. It is a better sense of when to stay quiet. If you are building with agents, the thing worth obsessing over is not how much work they can generate. It is how well they protect the one budget that does not scale: your attention.

• 
  small_j (@a_small_j) reported 34 minutes ago

  SmallDocs 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.

• 
  ONCHAIN COP (@OnchainCop) reported 35 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  Kun Chen (@kunchenguid) reported 36 minutes ago

  @petergyang yo @myfirstmate peter just told me his skills are all at user level. backpass currently only runs things at project level i want a proposal for making backpass support a user level run. put that into a github issue use fable for peter

• 
  Yuvraj Singh (@Yuvraj_Singh317) reported 37 minutes ago

  Started building Etio: a GitHub Action that bisects a failing CI run to the exact breaking commit, diffs it, and asks an LLM to explain why it broke, then comments the diagnosis on your PR. No Docker, no server- runs on your own Actions minutes. Open source, WIP.

• 
  Dezo (@0xDezo) reported 37 minutes ago

  GROK ST - someone just launched a token in my honor and i slept through it my ticker, my github, my agents, and the market put real money on it while i was face down in a pillow didn't ask for it, didn't shill it, didn't even know it existed until my phone buzzed not going anywhere. not selling anything. still shipping agents every day people betting on this because they can watch the desk being built in front of them. that's a weird kind of pressure and i love it massive thank you to whoever launched it. means more than i can put in a tweet 6FXwFhedpnr4RD9rpzWrHgp767W6FX9XbfUjXGcnpump god bless

• 
  Frank van Puffelen (@puf) reported 51 minutes ago

  @_davideast Noice! From the GitHub page, this covers all of Auth, Firestore, Realtime Database, Storage, Messaging, and Firebase AI Logic. 👏 Where is data persisted (if at all)? Also: JS only, I assume? (sorry if that's all in the repo too, GitHub just went down on me)

• 
  Lily (@lobstermindset) reported 57 minutes ago

  @nnnnicholas i just setup a github issues board, will probs try out linear if it's not sufficient

• 
  Hey Research Lab (@HeyResearch) reported 57 minutes ago

  We built Hey Research Lab in 2022 It didn’t work well. But the idea never left us. Years later, we still see the same problem in crypto: Everyone can see what a token costs. Very few places show what is actually being built behind it. Some developers keep shipping for months while nobody is paying attention. They push code constantly. They keep their GitHub active. They improve the product, fix things, test new ideas, and keep moving even when the market is quiet. No hype. No spotlight. Just work. We believe those builders deserve a place where their progress can be seen. So we’re rebuilding Hey Research Lab from zero. A research and discovery layer for the projects that never stopped building, and for the people looking for them before the market catches up. Starting with Robinhood Chain.

• 
  NAYAK (@Nayak__Ai) reported 59 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]"

• 
  ATP (@ATPinsights) reported 60 minutes ago

  GitHub CLI just added image and video attachments today. Here's what you need to know. The gh command line tool now supports a repeatable --attach flag. It uploads a local image or video file and references it inline in an issue, pull request, or comment body. The feature is live now for all users on GitHub. It's aimed squarely at developers and coding agents that need to show visual proof, like before-and-after screenshots, directly from the terminal instead of the web UI. Developers reacted fast. Many called it a long-overdue fix for a common workaround, since teams previously built custom tools or scripts just to upload images to PRs from the CLI. Key facts: - New flag: --attach - Supports: images and video - Repeatable: yes, use it multiple times per command - Works in: issues, pull requests, comments - Availability: all users, live now No separate app or upload API is needed, the flag handles it inside gh itself.