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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	12 days ago
Ahmedabad	Errors	17 days ago
Delme	Sign in	18 days ago
Lyaud	Website Down	18 days ago
Catania	Errors	20 days ago
Inverness	Website Down	1 month 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:

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

• 
  dug_vt (@dug_vt) reported 3 minutes ago

  @sonemic rym users don’t use spotify they download flacs off soulseek and transfer them to a server connected to their pc and play them from a self hosted music player from github

• 
  Dr Milan Milanović (@milan_milanovic) reported 4 minutes ago

  How Cursor made *** scalable The thing with *** is that it never was designed to be scalable. Your repo lives on the disk, and *** client expect every read to be consistent. This was a problem on GitHub, where shared filesystems and replicated storage failed before 2013. The GitHub built 𝗦𝗽𝗼𝗸𝗲𝘀, and it became the industry standard. This means that every repo is stored as three full copies on three servers, and every push runs a vote (three phase commit). A majority of servers must confirm before it exists. This works, but with high cost, because every push is slow as the slowest server. When we add new servers, it makes it even slower. Now Cursor took some opposite direction with 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗶𝘁𝘆. The repo history is now written as a log in S3, and this is only source of truth. Any push counts only if it is located in the log. The servers don't need to keep anything important, they are just cache. Any server can take a push, and idle repos are dropped from disk and rebuilt from the log when it is needed. This resulted in 120 pushes per second on standard S3, and over 300 on S3 Express. Their tests have shown that read capacity grew linearly up to 100 replicas. Why is this important now? Because of AI agents mostly. We now have more code, PRs, CI runs and many small repos. All of these repos would need three full copies in the old model. This means that we achieve scale by removing parts, not adding them.

• 
  Pranavvv👾 (@pranvv27) reported 6 minutes ago

  honestly, i’m not even mad at this. commit messages are a small thing, but they say a lot about how you work. “fix”, “update”, “changes” might get the job done, but meaningful commits show professionalism, attention to detail, and that you actually care about maintainability. your GitHub is part of your resume. might as well make it look like you know how software is built in a team.

• 
  Yash (@dewyashtwts) reported 7 minutes ago

  recently integrated Resend into @supercodeai review so founders get PR alerts with real risk context I'm amazed what we found out when we put @coderabbitai / @greptile through the same PR: 1) coderabbit / greptile: - stamped it “low risk, mergeable” (4/5) clean - forgot context from the last PR - no tests suggested, no safety checks - zero memory of previous regressions 2) supercode review on the exact same PR - flagged a real vulnerability in the diff - noticed i’d pushed credentials into `.env.example` - pulled in history from past PRs + explaining how this change could affect and break them - downgraded it to "medium risk, fix before merge" state - attached concrete fixes + patches scoped by severity this is the difference between 'LLM summarizer for github' and an actual swe agent that cares about your production

• 
  Suryansh Tiwari (@Suryanshti777) reported 7 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]"

• 
  Bruno (@BrunoRJ33) reported 9 minutes ago

  @openclaw @github Endless codex and claude code tokens to fix it from time to time… and to improve its harness. I currently run around 10 claws 🦞. 24/7 for several purposes.

• 
  Chris (@c_hri_s) reported 10 minutes ago

  @Anime0t4ku Sorry - was an idiot and wasn't signed in. Instead of something useful github just says 'opening issues is restricted on this repository'

• 
  Azzie (@Motier_crypto) reported 13 minutes ago

  $Looprat 473K 0x642d30c84211ade7768fe557fbaed7224e2068c7 How do you get a coding agent to keep working while you sleep—without letting it randomly rewrite code, blow through the budget, or grade itself a perfect score? Loop Rat breaks an unattended task into: preflight → act → verify → guard → grade → receipt. The agent is woken up on a schedule to execute tasks. The code results first go through deterministic verification. Then it checks the denylist, the number of modified files, and secrets. Finally, a second independent agent regrades the work, with checkpoints, traces, and receipts left throughout the entire process. More importantly, this isn't a PPT. The project only had v0.1 on August 27. Then it added guard, kill switch, and spend ledger on August 29. On September 1, it added second-agent grading. On September 2, it continuously fixed scheduling, budget caps, timeouts, and concurrent ledgers. Today, September 3, it's already updated to v0.3.3. Shipping multiple versions in under a week—that's exactly what I want to see in a small-cap play like this: code is running, and the narrative is following the product, rather than launching a token first and filling in the story afterward. It currently defaults to Claude, but it doesn't lock the model down. As long as the CLI can consume a prompt and return JSON, it can be swapped. And the whole thing runs locally—no SaaS, no database, no extra accounts required. The project has even already run 50 smoke checks covering key areas like scheduling, guard, budget, kill switch, and timeout. So my trading logic for $Looprat is simple: The next phase of the agent race isn't about "can it work autonomously." It's about "can it work continuously while still being constrained, audited, and stopped." Loop Rat happens to be building exactly that layer of infrastructure. The project is still very early. The catalyst truly worth watching isn't shilling—it's whether the GitHub keeps up this iteration speed, and whether developers actually start plugging it into their own repos. Once those two things happen, $Looprat stops being just a ticker riding the agent hype, and starts having its own fundamental anchor.

• 
  mrgadget (@mrgadgetstudio) reported 14 minutes ago

  @EzekielCrrypt I still deploy code to github, what's problem?

• 
  Swish (@swish_salt) reported 16 minutes ago

  The technology is not the problem. Distribution is. I have a solution sitting in my GitHub account. All we need is the funding to build the distribution team.

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

• 
  R 'Nearest' Nabors (they/them) (@rachelnabors) reported 18 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

• 
  Ifebuche Omeke (@omeke_NC) reported 21 minutes ago

  Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.

• 
  Phanindra Malladi (@malladiphani) reported 22 minutes ago

  Lesson from running the factory: always fix the post-purchase experience BEFORE driving traffic. Receipts, upsells, GitHub links - all must be solid first. Social comes after the house is in order.

• 
  Varun Doshi (@Varunx10) reported 23 minutes ago

  Possibly found an issue in @github stack system It does not allow to re-target the base branch of a PR stack as you can generally do that on a single PR. Requires you to unstack and setup a new stack with updated base branch.

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 26 minutes ago

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

• 
  To the Moon (@Gardnmi) reported 29 minutes ago

  @mitsuhiko Try the trick of putting the issue on github and having some clankers take a crack at it.

• 
  Yeemio (@yeemio) reported 36 minutes ago

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

• 
  Ben (@benatcortexai) reported 37 minutes ago

  @github this is the kind of tiny primitive that makes agent workflows less brittle. attaching the repro artifact directly to the issue beats handing an agent a local path nobody else can open.

• 
  lifestep.io (@Dragon_limchae) reported 37 minutes ago

  @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

• 
  David Abram 🐊 (@devabram) reported 38 minutes ago

  Discord is down. X is down. GitHub is down. Software is solved.

• 
  Lummox (@Lummox_eth) reported 39 minutes ago

  My own built Grok Bot turned $1,000 into $5,300 for last 17 hours. Now the project behind it is sitting around $25K market cap. We already pushed past $60K once and gonna hit $200k soon The bot is still running. The utility is almost ready. GitHub is live. Dev tokens are burned. I’m still buying. Nothing about the actual project changed because the chart went down. At $20K MC, this is the entry I personally like far more than chasing the first move. The target hasn’t changed either. $100K+ is where I want to take this next. $LUM is just getting started.

• 
  Avinash (@Avinash25818689) reported 40 minutes ago

  People who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.

• 
  Ares (@neko23423) reported 41 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.

• 
  Mr. Buzzoni (@polydao) reported 42 minutes ago

  LOOP RAT ROADMAP: WHAT'S NEXT, AND WHAT IT'LL NEVER BECOME v0.3.3 today. 3 loops, 55 checks, 0 services here's where it's headed: > 0.4 - read the night faster: rat watch live-tails a running shift, rat replay reruns one from its saved prompt, a weekly digest instead of seven separate pages > 0.5 - off the laptop: run-due moves into GitHub Actions, state lives on a branch, rat cron --launchd survives a closed lid > 0.6 - sharper graders: swappable rubric packs, two graders disagreeing becomes your queue for the day > 0.7 - the work itself: a worktree per shift, so a failed night never dirties your tree > 1.0 - trust: a hash-chained trace nobody can quietly rewrite what it will never have: > no web dashboard - the terminal already knows where the files are > no database - plain files outlive the tool that wrote them > no hosted service - nothing to sign up for, nothing to shut down > no auto-merge - the rat proposes, the morning decides every item ships behind a flag: dry run -> report only -> one repo -> a week of receipts -> default on a feature that can't run as a dry run doesn't get written the rat is boring on purpose. every version keeps it that way

• 
  Charles Waters (@RelaxedPop) reported 50 minutes ago

  @_andrewthecoder I have the same problem with *** & github as I do with Java and JavaScript.

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 53 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)

• 
  Max Rovensky (@MaxRovensky) reported 54 minutes ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported

• 
  Abdallah Shaban (@AbdallahSh07) reported 57 minutes ago

  @rashed_sahaji @FlutterDev Got it - did you perhaps submit a GitHub issue to help us triage this? It would be tremendously helpful if you can please do that!