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 (62%)
• Errors (21%)
• Sign in (18%)

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	2 days ago
Quilmes	Website Down	2 days ago
Bengaluru	Website Down	4 days ago
Yokohama	Sign in	5 days ago
Gustavo Adolfo Madero	Website Down	9 days ago
Nice	Website Down	9 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:

• 
  Lux Sp4rk (@lux_sp4rk) reported 49 seconds ago

  I dunno why I even humor this html > markdown trend. It's clearly not. Reality is that Markdown renders to HTML anyway. I.E: A Github issue is *not* raw markdown. The ByteRover argument relies on a false dichotomy.

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

  Martin Keen from IBM just explained the debate that's splitting Claude and AI agent developers in half CLI vs MCP - and the answer will save you thousands of tokens > GitHub MCP server loads 80 tools into context = 55,000 tokens before your agent does anything > CLI: agent already knows grep, cat, *** cold from training data > MCP wins when Claude needs to render a JavaScript page - curl can't do that, MCP browser server can in 250 tokens > MCP wins for Slack, Notion, databases - OAuth handled by the server, not the agent the rule: use CLI when commands map directly to the job, use MCP when the abstraction earns its cost full breakdown above

• 
  Péter Szilágyi (@peter_szilagyi) reported 2 minutes ago

  @josefprusa @Mojee3d @Prusa3D I have a Prusa, across the parts and kits spent probably over 2K EUR on it. The multi-material printer fails incredibly often, software issues / hangs, random overvoltage errors, ignored github issues, etc. It’s not only about hw price, support is also very lacking, unfortunately.

• 
  Lu (@LuminousTheReal) reported 4 minutes ago

  @SilverYogensha @thsottiaux Potentially, but it seems like it's using 5.4 to compact it since 5.5 is bugged out. I found it on github, lots of people are suffering with this compacting issue and i think we will get a reset soon since tibo mentioned the quality si down

• 
  SILVER (@Bitch_Paratha) reported 4 minutes ago

  @ThePrimeagen We should prolly make a github typa service and name it unicornhub or something (we can think of a better name tbh) and whenever our servers are down we show the GitHub logo

• 
  Manish rawat (@R11manish) reported 5 minutes ago

  @GithubProjects GitHub is down again

• 
  青川一 (@worigoule) reported 6 minutes ago

  @ZooL_Smith And then you google solutions and found yourself ended up in a github merge request or more likely a issue page written in like, 2 years ago

• 
  Sam Cymbaluk (@SemanticSamuel) reported 9 minutes ago

  @sebastienlorber Github is actually so slow. My TTS writes characters out one at a time after dictation is complete. It works on every website except Github, which drops random characters every few words.

• 
  Leaving Tech (@leaving_tech) reported 9 minutes ago

  @ThePrimeagen Angry unicorn! GitHub in trouble again.

• 
  Abinash (@implabinash) reported 10 minutes ago

  @ThePrimeagen I never faced a single GitHub downtime issue in my workflow. Oh! Sorry, I have been using GitLab for a year now.

• 
  Roj Niyogi (@niyogi) reported 13 minutes ago

  @colinhacks @pullfrogai @Pullfrog so for 90% of folks who are using cursor/windsurf/github copilot/claude code via an IDE "chatting" with their agent, the answer is just to tell your agent to fix everything? i've used both coderabbit and greptile extensively and here's what happens: 1. 20% of what is found is false (and likely even more variable if you pick a model) 2. i cherry pick issues and paste in editor to handle 3. code review is rarely "happy" and you can end up in a loop state that burns tokens bummer that you've got the flexibility on the one end but have a strong opinion on the other for what seems to be an obvious opportunity to close the loop for, i'd guess, a chunky subset of users

• 
  Quantum (@ItsMeQuantum) reported 14 minutes ago

  @emilios_eth They don't even know what syntax error is All they do is just Link LLM with GitHub and ask for a summary from it

• 
  AtomicNodes (@AtomicNodes) reported 15 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Sukhjit Singh (@thesukhjitbajwa) reported 15 minutes ago

  Published the campus website, learned about Next.js static content and export output, uploaded the files via FTP to the server, and now brainstorming ways to automate the process using either GitHub Actions or local scripts.

• 
  chandog (@thechandog) reported 19 minutes ago

  @kevinrose @digg how are you constructing novelty? stars are 40c on the dollar and a terrible way to measure anything on github.

• 
  Glitch Truth (@glitchtruth) reported 20 minutes ago

  OpenAI just put a coding agent on your phone. Codex, the model that originally powered GitHub Copilot in 2021, now ships as a mobile-native agent. You prompt from your phone, it spins up a cloud sandbox, runs the task, writes the diff, and opens a PR against your GitHub repo. No laptop, no terminal. "Fix the auth bug" typed at lunch becomes a merge-ready PR by the time you pay the check. GitHub's own 2022 study showed Copilot users complete tasks 55% faster. That was an autocomplete assistant living inside an IDE. The mobile agent doesn't assist you. It does the whole task in a sandbox and hands you the PR. The defensible skill is no longer typing the syntax. It's knowing what to build, what to ship, and what to measure after. Action this week: pull Codex on iOS, point it at a real repo, ask it to fix something small. You'll either see the next decade of work, or you'll convince yourself it isn't real yet. Either is information you didn't have on Monday.

• 
  isabel (@isabelrosesss) reported 21 minutes ago

  they should rewrite github in rust. i think that would fix everything

• 
  Nick Farina (@nfarina) reported 23 minutes ago

  My "work" so far this morning has been: 📋 Taking product feedback from my in-app Agent and feeding it to Claude Code 🌐 Asking Copilot on Github to explain a recent change to an open-source lib and pasting its explanation for Codex to fix I'm basically middle management now.

• 
  Crypto Scores Rating (@CryptoScoresCom) reported 32 minutes ago

  Did the team build before the money showed up? That's exactly what the "GitHub Before Crypto" metric tells you. It compares the first GitHub commit date to the token creation date. Positive number = code came first. Negative number = token came first. Ethereum: +589 days. Nearly two years of building with zero financial incentive. Solana: minus 63 days. Token launched before the repo even existed. Neither is an automatic verdict. But it tells you everything about priorities. CryptoScores just dropped a full tutorial breaking it down. Watch it now :

• 
  The Doctor (@Doctorthe113) reported 32 minutes ago

  @_yorunoken @sebastienlorber On my chromium and Firefox based browsers I only see a slight delay/flickers. Probably caused by the huge number of texts. I don't see how GitHub can fix that without using something like pretext. But what op posted seems to only affect macos. Unfortunately macos users tend to be entitled people. So people like op will continue to blame GitHub instead of using a better browser or complain to chromium.

• 
  Shubh Jain (@shubh19) reported 33 minutes ago

  @devXritesh now it’s mostly docs, blogs, github issues, and AI explanations instead of full books

• 
  Benitto J D (@BenittoJD) reported 35 minutes ago

  Github actions are down again

• 
  Yashas (@YashasGunderia) reported 36 minutes ago

  Most AI-native startups will not lose because they ship too slowly. They’ll lose because they ship fast without knowing what actually worked. Coding agents gave every team more velocity. Cleo gives them product memory. Customer feedback, GitHub issues, Slack threads, metrics, tickets, specs, launches, agent traces, all connected into one loop that tells your team and your dev agents what to build next. We’re opening the Cleo waitlist today. For small teams trying to compete with companies 100x their size (link in comments)👇

• 
  bestmark1 (@bestmark_one) reported 37 minutes ago

  This pattern repeats: AI setups often fail at edges—heartbeats, polling GitHub issues, error recovery—not the core models.

• 
  Adi (@wtfaditya_) reported 38 minutes ago

  @azwan_ Yes its down, They don’t want us to deploy anything on Friday, For global wellbeing 🫡 @github

• 
  Farhad zand (@farhad_pd) reported 40 minutes ago

  Hey @grok team, your GitHub connector is seriously broken. I ask it to make a change and push it to my repo. It confidently tells me “done,” but nothing is actually changed or pushed. It’s just falsely claiming the task was completed.

• 
  Lazi (@algoritmii) reported 46 minutes ago

  @github bro ffs fix your ******* issues stop pushing features

• 
  atomicbot.ai (@atomicbot_ai) reported 47 minutes ago

  Hermes Agent vs OpenClaw using Qwen 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Hedwigz (@itsamitush) reported 47 minutes ago

  @ZoharEiny E.g. github mcp for code,issues & coralogix mcp for logs & internal mcp for org structure

• 
  Beau Johnson (@BeauJohnson89) reported 56 minutes ago

  agent skills are becoming the new software package DenisSergeevitch/agents-best-practices > 120 stars on github > created today > provider-neutral skill for codex + claude code > designs and audits agent harnesses > covers tools, permissions, memory, evals, prompt caching, observability, and safety the important line from the readme: the model proposes actions. the harness validates, authorizes, executes, records, and returns observations. that is the whole game. most people keep trying to fix agents with bigger prompts. the real fix is a tighter harness.