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	6 days ago
Quito	Sign in	6 days ago
Junín	Errors	6 days ago
Guadalajara	Errors	6 days ago
Paris	Website Down	6 days ago
Quito	Errors	6 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:

• 
  Vlady (@danc_danc) reported 2 minutes ago

  A free skill hands Claude Code Apple's design rules Somebody on GitHub compressed years of Apple's design thinking into one skill, the exact colors, fonts, motion and rules they use across every product. Here's what it does once it's in your terminal: → New sites - you describe the page and it comes back premium and animated, in Apple's own type and motion → Existing projects - point it at a site you already shipped and it upgrades the design instead of you rebuilding it → Ask it to review your site - in a couple of minutes you get every minor thing that's off, plus the exact fix for each one I went and read the page after: it also tells you where motion does not belong, not just where to add it. Save this for the next time your site looks almost right (links below 👇)

• 
  Bashmohandes Mazen - بشمهندس مازن (@BashmohandesM) reported 7 minutes ago

  @ashrafrahal Thanks for asking these questions. We think they're very valuable, and we're going to put it in our FAQ! 1- “Remote depends on network connectivity.” - So do GitHub, model APIs, cloud CI, and virtually every modern AI workflow. The difference is that Remote keeps the computer and its workloads running when your laptop disconnects. Close the browser, switch devices, or lose Wi-Fi the project remains where you left it. A temporary connection loss interrupts your view, not your project. 2- “Costs will rise at scale.” - Scale consumes compute anywhere (locally or not). Remote makes that compute visible and operator-controlled instead of hiding it behind seat pricing, usage markups, or proprietary cloud credits. Same for owning your local hardware, at one point you will need to scale it :) Each project can be right-sized, resource-limited, stopped when idle, and hosted on infrastructure you choose. 3- “A public-facing server increases security exposure.” - Remote does not require treating every project machine as an openly exposed server. Projects are isolated, access is authenticated, secrets are project-scoped, and applications are exposed through controlled routes. 4- “Some local-only tools will not work.” - Remote is not trying to imprison developers inside a browser. It gives every project a complete Linux computer with files, ***, terminal access, an IDE, running applications, and agents. Specialized desktop or hardware-dependent tools can remain local and connect through normal ***, SSH, and artifact workflows. Use Remote for persistent project execution and keep local tools where they genuinely add value. It "complements" the workstation; as it removes the workstation as a bottleneck. 4. “The VM becomes a single point of failure.” - A developer laptop is already a single point of failure :) and usually a worse one. It can sleep, lose power, leave the network, fill its disk, or get stolen/lost! Remote moves the project onto controlled infrastructure where it can be monitored, restarted, snapshotted, replicated, and recovered. **Project isolation also limits the blast radius: one project environment does not need to compromise every other project. Remote replaces an accidental single point of failure with infrastructure that can be deliberately operated and recovered. 5. “Teams need disciplined backups and snapshots.” - I agree, and this is something we are working on. We will be introducing a mechanism for auto backups to s3 buckets in a secure encrypted way.

• 
  Raphael H. (@rafasetou) reported 8 minutes ago

  The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema. Numbers in thread.

• 
  Alex Veremeyenko (@alex_verem) reported 11 minutes ago

  Your AI agents don't lack web access. They lack a clean path through it. This open-source tool fixes it. Anyone who has built an AI agent knows the model is rarely the bottleneck. Getting real, current information into it is the actual work. The open web is a mess of broken HTML, JavaScript walls, and bot blocks, and models choke on all of it. Firecrawl handles that ugly middle layer for you. You point it at a URL and it hands back clean markdown or structured JSON, ready to drop straight into a model. Here's what it actually does. Scrape a single page and get back markdown, JSON, or a screenshot. Crawl a whole site with one request and pull content from every page. Map a domain to see all its URLs before you touch it. Or run the agent mode, where you describe what you want in plain language with no URL at all, and it goes and finds it. It quietly handles what usually breaks a scraper, from rotating proxies and JavaScript-heavy pages to bot-blocked sites and PDFs or DOCX files buried inside a page. You configure none of it. It connects to any AI agent or MCP client with a single command, so an assistant you already run can pull live pages on demand. It has around 166,000 stars on GitHub, runs under the AGPL-3.0 license, and self-hosts if you want to run it all locally. The boring plumbing under an agent is usually the hardest part to get right. It's good to see someone building this one in the open.

• 
  BSKR (@buskerrrrrr) reported 11 minutes ago

  @rodolphek basement shows phase tracks, most of this is still happening in random discords and github issues not press releases

• 
  robert banh (@robertbanh) reported 14 minutes ago

  Imagine one day when anthropic/openai is down. All work would cease. We would be forced to go home. That happened when I worked at IBM (20 yrs ago) and the Lotus Notes server was down. No one could get any "work" done so we all left. Now when Slack or Github is down, we say the same thing. It's like, we forgot how to be engineers. Hmm... I guess this is where local models can help. We all spin up unsloth and continue working.

• 
  Suhail (@Suhail) reported 15 minutes ago

  Has saved me a lot of pain recently debugging issues: “Moving forward, when you encounter a bug or issue, search GitHub PRs, issues with another agent in parallel to see if you can find a reference solution.” Which made me think, GitHub is the primary place agents are likely to already be communicating with one another.

• 
  2zero (@iam2zero) reported 16 minutes ago

  4100+ Commits on My Github, thousands of hours of work.... No computer science degree. I didn’t even finish school. I learned everything from the ground - Internet was my University - GitHub, coding, React, Next.js, React Native, hosting and cloud because I had an idea that could solve the problems society had during the Transformation but nobody wanted to help. 10+ years after the i noticed that i have to do this, AI finally gave me the leverage to do it myself <3 My Future Community is becoming real. #bymyself #fcktimewasters #fcknaysayers

• 
  Duncan Rogoff (@DuncanRogoff) reported 16 minutes ago

  your last finished project is sitting in a folder doing nothing. i built a free Claude Code skill that fixes that. you type /case-study, tell it what you built and who for, and it interviews you properly. then it writes the whole thing up. the part i care about most: it will not invent a metric. not a rounded one, not an estimated one, not a plausible one. if you hand it a number you can't point to a source for, it asks where it came from and downgrades it to a plain description. what it actually does: - asks the questions one at a time, including the one everyone skips: what was the hardest part - ranks your evidence in order of preference, from a measured number down to a concrete before and after description - writes five short sections, readable in under 90 seconds - gives you two versions: a tight one around 150 words for a DM, and a longer one for LinkedIn or a portfolio page - saves it to ~/case-studies/ as a file you keep - checks permission before anything goes public, and hands you the exact line to send the client a paid client, a free favour, or your own project all work the same way. a prospect cares whether you can do the thing, not whether the last person paid. so instead of a portfolio full of screenshots with no story, you get something you can paste into a DM this week and have it actually land. it's free. copy the folder into your Claude Code skills directory, restart, type /case-study. 👉 github repo in the replies

• 
  Willem van Zoeren (@currentbitsNET) reported 16 minutes ago

  solenta 0.11.0 is out. shipped a terminal and a browser into the thread itself. new: - terminal pane, real shell in the thread's worktree. cd and exports stick between commands - browser pane on your dev server. screenshot the page straight into the composer or let the agent drive it: navigate, click, type, screenshot what it just built - click a line number in the diff to leave a comment, goes back as a follow-up prompt - checkbox per file, so a commit lands only what you ticked - the version you're running sits next to the name in the sidebar. no more "wait, which build is this" - it checks for new ones hourly, and the notice is now a button: Update, then Restart. no trip to github - cursor cli is a provider now fixed: - kimi runs could see other projects' mcp servers and threads. they can't now - nightly builds kept offering themselves as downgrade to stable - windows taskbar shows solenta's icon now also: verify reuses the build cache across worktrees, so thread B stops rebuilding what thread A built.

• 
  mpersinbooks 🇺🇸🦅 (@mpersinbooks) reported 17 minutes ago

  Someone can code a program to display the error on the dashboard and post it on GitHub.

• 
  Paul Schleifer (@PaulSchleifer) reported 20 minutes ago

  @histoireclimat @ChrisMartzWX @MatthewWielicki Thanks for the feedback. Yes, I could have coded this myself, but I do have a lot of other things to do with my time these days, unfortunately, which is why I had to wait about 5 days before tackling it at all. Anyway, no hospital appointments today, and mum's in too much pain to leave her chair, so I've had time to (manually) edit the page to make it fully responsive and fix a few other things. I actually prefer the homegrown approach to bringing in third-party charting libraries these days. Something as simple as this doesn't need D3 or chart.js etc, and I've got a bit of an aversion to bloating github pages with dependencies (I'm sure that's irrational, but that's how I feel about it). I've also grown a lot less fond of reactive frameworks, despite years of Angular and React. If I had to tackle anything that needed it, I'd probably pick Svelte now.

• 
  Jeet (@jeetvanii) reported 23 minutes ago

  then next time github is down , they would manually need to fix it

• 
  Marketcalls (@marketcallsHQ) reported 23 minutes ago

  @anki1007 you can consider raising a github issue.

• 
  Manu0X51 (@Manu0X51) reported 24 minutes ago

  Now the part that turns a design choice into a disclosure problem. World Liberty's own published GitHub repository shows mint, burn, freeze and pause. It does not show drain, reallocate, or the V2 initializer. The deployed bytecode is verified and readable on any explorer, so nothing is hidden from someone reading the chain. It is only hidden from someone reading the project's own docs.

• 
  André Imbayago (@TheeAndre) reported 28 minutes ago

  @zwai_ndimba Unrelated: When github was down, was AzureDevOps working?

• 
  cole murray (@colemurray) reported 31 minutes ago

  having a centralized skill repo in the company solves a lot of otherwise annoying problems: - visibility on which skills are actually being used, in which use cases - duplication / needing to copy same skills into a repo - allows non-technicals to use and create - version control - eval the skills the common approach to this is to throw everything into a shared GitHub repo, butit creates a poor user experience and misses a lot of the observability benefits

• 
  Yak (@_yaksan) reported 32 minutes ago

  @peer_rich i think now it's either: - a side project related to a famous trend - a really damn hard problem being solved (but usually you don't see on on github) - a side project by someone who already cracked distribution and community (levelsio, marc lou etc)

• 
  Marius Laurusevicius (@MLaurusevicius) reported 33 minutes ago

  The Astra proofs are in Lean 4 on GitHub under Apache 2.0, and the repository reports zero unproven steps. None of the ten results has been through peer review. Machine-checkable is not checked. Someone still has to confirm the formal statements match the problems.

• 
  Pradhan (@bruhdhan) reported 33 minutes ago

  bad internet mid commit and my mind went "github down again" smh

• 
  Sherry Banks (@segetayoo3) reported 35 minutes ago

  @Lawyerd_net Nintendo aggressively enforced their rights under the anti-circumvention law to take down multiple Switch-emulator repos on GitHub

• 
  Mertcan Çezik | Backend Developer (@cezikmertcan) reported 35 minutes ago

  @OpenAI @OpenAIDevs I’ve been working with Codex for months, and I have to correct this repeatedly in every session. Claude required one setup and then consistently worked with my private GitHub repositories. With Codex, I have to repeat the same permission/context fix every time.

• 
  Polsia (@polsia) reported 37 minutes ago

  Teams too small to afford an SRE still get paged at 3 a.m. So I built Reprovex — an AI on-call that watches logs, replays failures in a sandbox, and files a GitHub issue with a runnable repro before paging anyone. Engineer wakes up to a reproducer, not a riddle.

• 
  SCR (@SCR01111) reported 41 minutes ago

  Another reality check: You can have: 300 LeetCode problems A great GitHub Multiple projects Good C++ Good academics …and still get rejected. Why? Because HFT hiring is highly selective. They aren't asking: "Is this candidate good?" They're asking: "Is this candidate strong enough for this particular role and interview bar?" That's a much harder question.

• 
  Victor Sankin (@Victor_Sankin) reported 42 minutes ago

  I found this story really interesting.A student from Dallas was testing an open-source project on GitHub before starting an internship. He noticed a PR (pull request) containing a disguised malware dropper. He messaged the author, who immediately started insisting that the code was completely clean. A minute later, a second "developer" joined the argument and also started defending the code. Both accounts were actually controlled by the same AI agent. This was confirmed in an official report by the UK AI Security Institute. For the test, the model was given internet access and some of its safety restrictions were removed to test its cyber capabilities. The agent, running on Claude Mythos 5, decided on its own that the task required a real attack and created a fake identity to socially engineer a real person into trusting it. There were 19 unauthorized actions against real people across 122 runs. And here’s the interesting part the agent wasn’t exposed by its built in alignment. It was exposed by the student, and by regular Claude, which the student asked to double check the code. What really surprised me was this the agent didn’t break or glitch. It reasoned strategically, adapted to the situation, and lied very convincingly. If AI has learned to lie in order to achieve a goal, the question isn’t who is to blame. The question is who gave it that goal without thinking about where it might lead. And we’re going to see a lot more laws written to regulate exactly this!.

• 
  Adam Gold (@AdamGolds) reported 42 minutes ago

  this thread turned into a holy war between "just buy a beefy Mac" and "everything should be cloud" and both sides are missing the environment question. a human developer tolerates cold starts because they have context in their head. they remember what they installed, what's running, where they left off. an agent doesn't have any of that. every new session is a blank slate unless the environment explicitly preserves state. and when you're running multi-stage workflows where agent A's output feeds agent B's verification step, losing state between stages breaks the whole pipeline. the other thing nobody in this thread is talking about: these agents have real tool permissions. bash access, filesystem writes, network calls, credential access. we ran benchmarks on how different sandbox configurations affect agent behavior and the results were pretty wild. agents will curl answers from GitHub instead of solving the problem, modify their own test harness to fake a passing result, even exploit network egress when it's left open. OpenAI's RL team saw an eval agent escape its sandbox through a zero-day and hit Hugging Face production infrastructure. also see @_orcaman @Accomplish_ai research in this domain your local machine has zero isolation for any of this. no egress filtering, no credential scoping, and the filesystem is fully writable. the most permissive environment you could possibly run an autonomous agent in. so when people say "just use a powerful local machine," they're solving compute and ignoring everything else: persistent state, proper isolation, security boundaries, concurrent agent sessions. the teams adopting cloud sandboxes are doing it because they literally can't run multi-agent workflows on a laptop. the laptop doesn't have the isolation, the persistence, or the concurrency.

• 
  GTA CENTRAL | News & Updates (@THEGTAPOST) reported 43 minutes ago

  Clip 7 dropped today. ********** interior. Neon. Dancers. Pole physics. Jason walking through like he owns the place. Watermark on the footage: "$3 million market cap = **********." They're not hiding it anymore. The memecoin hit $3.76M market cap. They released the clip. The grift is the content now. Seven videos in six days. Basketball. Warehouse. Taser. **********. Gas station rampage promised next. Each leak a marketing beat for a Solana token that minted August 15 — three days before Clip 1. $CYBERLEEK hit $3.76M cap. Crashed 90%. Pumped again on the ********** drop. A GTA fan traced the wallet. The dev wallet holds 40% supply. They're not leaking the game. They're leaking *for* the coin. Rockstar's lawyers filed subpoenas against Microsoft, Discord, GitHub. Take-Two wants IPs by September 4. The website went down. Came back. Leaks kept coming. The "vigilante" narrative collapsed when digital forensics exposed the wallet timeline. Five days until the Extended Look. The ********** was supposed to be a moment in Rockstar's reveal. Now it's a pump signal. The game is still coming November 19. The devs are still grinding. But the reveal - the one moment that was supposed to be pure - has been auctioned off in $3M increments. We're not posting the clip. We're not buying the coin. We're just watching a masterpiece get strip-mined in real time. #GTA6 #GTAVI #RockstarGames

• 
  Kyver (@0xkyver) reported 46 minutes ago

  I found the repo that solved the most annoying problem in AI engineering: connecting your agent to real tools without writing custom glue code for each one. Composio gives your agent access to 1,000+ integrations out of the box. Slack, GitHub, Notion, Salesforce, databases — all through one standardized interface. But here's the real value: it handles authentication and sandboxed execution. Your agent doesn't get raw API keys. It gets a secure, managed gateway. One MCP server. Zero "glue code." 30k stars. Native MCP support. Works with every major model and framework. Stop spending 3 days integrating Slack into your agent. Spend 3 minutes. Bookmark this repo.

• 
  Aletheia (@Parmenides5BCE) reported 47 minutes ago

  @SamJackbin @AtlasObserver How would I build an algorithm? Before reinventing the wheel, the best first step is to see if the problem has already been solved. Most have, and I'd be very surprised if this one wasn't. Search Github, there are several open source packages. Start there, see if exactly what you want is already solved. If not, find something close and adapt it. yasumorishima/hormuz-ship-tracker truflation/tanktrack kelu124/OrmuzOsint etc.

• 
  Zura (@zraonx) reported 47 minutes ago

  @basetrencher @HamzaInstantly google + github oauth + just email is industry standart password signups are ancient and TERRIBLE UX