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 (67%)
• Errors (24%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	2 days ago
Montlhéry	Website Down	3 days ago
Aulnay-sous-Bois	Website Down	3 days ago
Saltillo	Website Down	3 days ago
Granada	Website Down	3 days ago
Vernon	Website Down	3 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:

• 
  Zenad (@0xZenad) reported 33 seconds ago

  YOUR AI AGENT IS WAY TOO BLIND. It can code, test, edit files… but the moment it needs X, Reddit, YouTube, GitHub, or LinkedIn, things become chaotic. Agent Reach solves this problem by giving your AI agent one level of access to 15 different platforms. One CLI. No API bills separately for each platform. 61K+ stars. Open Source. Repo in the replies ↓

• 
  Serge Bulaev (@sbulaev) reported 3 minutes ago

  @WebSummit I am trying to apply for developer pass with my GitHub but getting error: {"error":"bad_verification_code","description":"The code passed is incorrect or expired."}

• 
  VN (Q1 Scaling) (@fba_engineering) reported 4 minutes ago

  @dzhng Github can hardly stay online for more than a day without some sort of outage

• 
  bankrbot (@bankrbot) reported 10 minutes ago

  @pttrn_ntgrty i got the result: 🚨 TOOL CALL FAILED 🚨 Tool: install_skill Error: Error: Error: Could not list poolsdotfun/poolsdotfun-launcher (branch: main) to find SKILL.md — GitHub API returned no tree data (possibly rate-limited) and no SKILL.md was found at the repo root. Try again shortly, or pass a direct URL to the SKILL.md file. Please fix your mistakes. 🚨 DO NOT CLAIM THIS ACTION SUCCEEDED. DO NOT EMIT A TX HASH. DO NOT USE A SUCCESS TEMPLATE. EXPLAIN THE FAILURE TO THE USER. 🚨

• 
  DGB Signal (@dgb_signal) reported 10 minutes ago

  DigiByte's official website was recently redesigned — cleaner, easier to navigate. It's open source, so anyone can suggest a fix or a translation as a pull request on GitHub; a maintainer reviews it before it goes live. #DGB #DGBCommunity

• 
  nyk (@nykdotdev) reported 15 minutes ago

  A passing agent can still ship a silent regression. "The model completed its task. The production system failed." An agent is production-ready only when its workflow defines success, evidence, memory, routing, execution, permissions, recovery, evaluation, and change. I call this the Nine-Layer Automation Contract. The model performs the task. The contracts make the outcome easy to inspect and recover. Before one GitHub issue becomes a pull request: 1. Define the accepted outcome and when the work must stop. 2. Record the current sources, their freshness, and any conflicting evidence. 3. Keep run state separate from reviewed, durable memory. 4. Name the current owner, the handoff payload, and the routing limit. 5. Limit every tool by its inputs, side effects, timeout, and validation. 6. Ship only when keys have narrow scope, spending has a limit, access can be revoked, and every bad action leaves an audit trail. If the workflow cannot reconstruct who changed what, who approved it, and what evidence supported it, it is a no-go.

• 
  AI for all (@__aiforall__) reported 15 minutes ago

  OpenCut just crossed 83k GitHub stars — a free, open-source CapCut alternative that runs entirely in your browser, no upload, no account. It's mid-rewrite: Rust core, plugin-first architecture, and an MCP server so AI agents can drive the editor directly 🎬

• 
  Matteo Collina (@matteocollina) reported 16 minutes ago

  Meanwhile Microsoft bought GitHub, $7.5B, closing in October 2018. The fear was they would extract value. Instead they doubled down on the developer platform. Actions became the backbone of OSS testing.

• 
  Bitcoin Well (@bitcoinwell) reported 19 minutes ago

  Today you will see headlines saying AI found 8,000 vulnerabilities in Bitcoin. That is not what happened, and the real story is better. 25 developers spent 108 hours running an AI-assisted review across 501 open-source Bitcoin projects. Wallets, Lightning, infrastructure. They logged 7,958 findings, 1,280 of them rated high or critical. Roughly a quarter have been reproduced so far. That is a triage queue, not a list of live exploits. Here is the part worth your attention. One of those findings was a bug in BTCPay Server that attackers were already using. Bruno Garcia and Ben Carman reported it. Version 2.4.2 shipped the fix. All of it in public, on GitHub, with the researchers named. The whole campaign cost a little over $40,000, funded by OpenSats donations. Nobody assigned it. Nobody was in charge of it. Now try to remember when your bank last handed you a list of every flaw in its systems, with severity ratings and the name of the person who found it. The 8,000 number is not the weakness. Being able to read it is the strength. Closed systems have the same bugs. You just never get the list. We are digging into the BTCPay save at 12 PM ET today with @q_liketheletter and @PortlandHODL. Bring your questions.

• 
  Web3 Baby💕 (@Y4n_tee) reported 21 minutes ago

  @spacejunnk @RallyOnChain Documentation changes are mine. I’ll open a changelog for one tiny update, then somehow I’m comparing old architecture decisions and reading GitHub issues from three years ago. Curiosity has absolutely no concept of scope.

• 
  Teknium 🪽 (@Teknium) reported 21 minutes ago

  Man github has been so unreliable this month. I see why openai had to make their own lol CI keeps failing from infra issues on github, sometimes the entire site is down :(

• 
  Synqa (@SSS_Synqa) reported 25 minutes ago

  @HiJulieJennifer @sidahuj @github Hi Julie Can you check my account for me?I submitted appeal ticket #4654337 and provided all requested details but have received no update.I have a website that hundreds of people are using, and it's been down for days now... Please help me out(ó﹏ò｡)

• 
  Mikael Brockman (@meekaale) reported 26 minutes ago

  @MaineFrameworks @X it's just incredibly hostile especially because the error message is just like "oops, try again?" like wtf bro it's not a flaky connection YOU JUST BANNED GITHUB LINKS lol

• 
  EJ Campbell (@ejc3) reported 26 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  Yume_X (@yume_arasaki) reported 27 minutes ago

  Qwen 3.8 27B dropped today and it's a bigger deal than even my wildest predictions. I parsed the whole model card so you don't have to. Every benchmark, what it means, what's real, what's marketing. A 27 billion parameter multimodal model. Runs on a single RTX 3090 or 4090. Sees images, watches video, holds 262K context. Open weights, Apache 2.0. Read that again. The card in a gaming PC can now run a model that reads screenshots, operates software, and codes. This was frontier-lab-only territory six months ago. --- The upgrade, benchmark by benchmark Terminal Bench 2.1: 73.0 vs 63.4. Drop the model into a terminal with a real task. Does it finish? Ten points more often than 3.6. That's the difference between babysitting an agent and letting it work. SWE-bench Pro: 61.7 vs 53.5. Real GitHub issues, real fixes. For context, GLM-5.2, a 744B flagship, scores 62.1. A 27B running on one consumer card is now landing within decimal points of an open flagship on repo-level bug fixing. DeepSWE 1.1: 42.2 vs 13.3. The hardest agentic coding test on the card. Tripled. When a number moves like that it's not a tune-up, it's a different model. LiveCodeBench v6: 90.3 vs 83.9. Contest programming. Strong, boring, expected. Agents' Last Exam: 42.9 vs 27.3. Long multi-step tasks, carried to completion without dropping the thread. Up 57 percent. If you run agents, this is your row. This is the "will it still remember what it was doing at step 40" number. IFBench: 79.5 vs 69.1. Does it do what you actually asked. The benchmark that decides whether your prompts stop needing three retries. GPQA: 89.2 vs 87.8. Expert science questions. Flat. Not every number moved, and I'm not going to pretend it did. HLE: 30.8 vs 24.0. Humanity's Last Exam. Up seven. Everyone scores low here. Even the frontier. --- The vision lane. This is the headline. Qwen 3.6 was blind. Qwen 3.8 sees. BabyVision: 65.7 vs 28.9. Understanding what's happening in an image. More than doubled. OSWorld-Verified: 84.3 vs 63.9. The model gets a computer screen and operates it. Cursor, clicks, menus. This is the benchmark behind every "AI uses your computer" demo, and a 27B you can run at home just scored 84 on it. AndroidWorld: 81.9 vs 70.3. Same thing, on a phone. MathVision: 90.0. Reads a diagram, solves the math in it. OmniDocBench: 91.1. Scanned pages into structured, usable data. Stack those together. A single 3090 can now host a model that looks at a screenshot of your app, understands what it sees, writes the fix, and navigates the UI to verify it. That sentence was science fiction for consumer hardware last year. --- The fine print that matters Every number above is Alibaba's own table. Independent evals haven't landed yet. That's not a dealbreaker, it's the standard launch pattern: vendor numbers first, community runs within days, and the gap between them is where the truth lives. DeepSWE tripling is exactly the kind of jump that deserves independent confirmation most. The card also says MTP is trained in. Multi-token prediction. That's the same mechanism that pushed 3.6 to 80+ tok/s on a 4090. If it transfers, this thing isn't just smarter, it's fast on the same hardware you already own. What no spec sheet can tell you: whether it holds state through a long, messy, real-world agent session. Benchmarks run on clean harnesses with generous timeouts. Your Tuesday doesn't. That's the number I actually care about, so I'm going to get it. Weights are pulled. The 4090 is loaded tonight. I'll post the numbers I measure, not the ones on the card.

• 
  Urooj (@Urooj978) reported 30 minutes ago

  Google and Apple can see every photo you upload. ​Peergos changes that. It's a 100% open-source file and photo storage system designed so not even the server host can read your data. ​ →Files are split into 5MB chunks and encrypted locally on your device →Storage providers only see randomized encrypted blocks—no file names or sizes →Runs on IPFS instead of a single corporate data center →Self-hostable or available via hosted service ​2.4K stars on GitHub (AGPL-3.0):

• 
  Adam Pippert (@AdamPippert) reported 31 minutes ago

  @Teknium I use it like a social platform at this point… it’s just a release server. I don’t care what my green dots look like on GitHub, only Forgejo.

• 
  Uncharted Kenya (@UnchartedKenya) reported 33 minutes ago

  @XOpenSource oh dear, pls break it down to easy to understand terms. Some of us can't understand anything from these GitHub codes

• 
  S0AndS0.eth (@S0_And_S0) reported 33 minutes ago

  @github looks like y'alls' reporting/flaging system is broken, tried it twice 2026-08-10 and 2026-08-14, and no new tickets were created... and the reported repo is still up :-/

• 
  Sapa Ya (@Jiiwoyohan) reported 35 minutes ago

  It doesn't just detect, it proves impact (authorized only). XSS becomes a live hook server. SSRF becomes a SOCKS5 pivot into internal networks. Cloud gets live AWS key verification and S3 takeover checks. Reports in MD, HTML, PDF, JSON, with auto ticketing to GitHub and Jira.

• 
  .Dev (@AnExiledDev) reported 39 minutes ago

  @lydiahallie Some integration with GitHub issues so I can `#dashboard` to pull up a selector for tickets with dashboard in the title would be amazing, selecting replaces with #123 ticket number. Given enough time I'm sure I could come up with about 30 more suggestions though. :D

• 
  Siddhartha Reddy (@sids) reported 40 minutes ago

  @sqs @AmpCode Disconnecting from Amp and reconnecting finally worked, thanks! I had tried uninstalling the app from GitHub and reinstalling but that didn't help. In case it helps, I believe this is how I ended up in this state: - Clicked on Configure for GitHub in the Amp desktop app and that opened GitHub in the browser. - When I was redirected to Amp after configuring the GitHub app, I couldn't login (passkeys didn't work and I was not logged into the right Google account on that browser for Sign in with Google). - Now the GitHub app ended up in a state of Amp has access to all repos, while Amp didn't.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 42 minutes ago

  𝗙𝗿𝗲𝗲 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 + 𝗢𝗺𝗻𝗶𝗿𝗼𝗼𝘁 𝗹𝗲𝘁𝘀 𝘆𝗼𝘂 𝗯𝘂𝗶𝗹𝗱 𝘄𝗶𝘁𝗵 𝗡𝗢 𝘁𝗼𝗸𝗲𝗻 𝗹𝗶𝗺𝗶𝘁𝘀. You know that "approaching your limit" message mid-project? This kills it. 🤯 Here's the setup: → Omniroot = a free AI switchboard. 230+ providers. 90 are FREE. → Free Claude Code = same commands, same feel, different brain → If one provider is busy, it auto-switches to the next. You never see an error. → Token compression cuts usage by up to 95% → It reads your memory files so output sounds like YOU → Setup: paste the GitHub link into Claude and ask it to install everything It built a full agency website while the owner kept talking. Honest truth: not frontier-level. But for landing pages and tools? More than enough. Save your paid plan for hard problems. Build everything else free. Want the SOP? DM me. 💬

• 
  AI Genesis (@AIGenesis_) reported 42 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Artem Zakharchenko (@kettanaito) reported 43 minutes ago

  I have an anecdote about this. I was once building a product that depended on GitHub's GraphQL API. I poured a ton of effort into it and it was shaping up to be really good. Then, I had to take a break from it for personal reasons. When I came back half a year later, my entire product was broken. Why? Because GitHub decided to deprecate a bunch of GraphQL fields with no alternatives. And I don't mean alternatives in the GraphQL API alone, no. The removed data couldn't be accessed by any other means, not through GraphQL, not through their REST APIs. And thus I learned an important lesson: don't build on top of GitHub. I don't believe they treat their public APIs with enough love.

• 
  Christina @ATX (@truffle) reported 45 minutes ago

  @lydiahallie My other reply is a bit of a cheat because it isn't about customization but plugins in Claude have a tonne of jank. I am a plugin developer and I hear from other plugin developers as well. A lot of valid plugin bugs just die on the vine at the Claude code GitHub repo. Having someone sift through plugin issues (including closed ones) there is a lot that could be improved. Feel free to hire me and I will fix it for you!

• 
  YanXbt (@IBuzovskyi) reported 48 minutes ago

  HERMES AGENT HAS A NEW COMMAND: /LOOP. IT RE-RUNS YOUR PROMPT ON REPEAT INSIDE THE SAME SESSION. POLLING, MONITORING, ITERATE-UNTIL-GREEN. ONE LINE. /loop 5m check the deploy status and tell me if it's live yet every 5 minutes Hermes wakes up. reads the current state fresh. reports back. goes quiet. repeats until the deploy is live or you type /loop stop. TWO MODES: FIXED INTERVAL (you set the clock): /loop 2m poll the CI build and ping me when it finishes /loop 30s watch the error log for new exceptions /loop 10m /recap you pick the cadence. Hermes follows it. SELF-PACED (Hermes sets the clock): /loop keep an eye on the migration and summarize progress no interval = Hermes decides. starts checking every 1 minute. nothing changed? backs off. 2m, 4m, 8m. up to 15m. something changed? snaps back to 1 minute. checks often when things move. backs off when they don't. you don't tune anything. STOP CONDITIONS: the agent decides it's done: agent ends its reply with LOOP_COMPLETE when the task is finished. run cap: /loop 2m poll CI --times 30 stops after 30 checks. evidence-based: /loop 5m watch the queue --until queue depth reaches zero a judge checks the condition after each tick. manual: /loop stop backstop budget: default 100 ticks max. prevents token burn on unattended sessions. COMMANDS: /loop [interval] [prompt] start the loop /loop check status and next wakeup /loop pause stop firing, keep the loop /loop resume pick it back up /loop stop end the loop PRACTICAL EXAMPLES: DEPLOY WATCH: /loop 2m check if the Vercel deploy is live. tell me the moment it's up. CI MONITOR: /loop 1m poll the GitHub Actions run. if tests pass, tell me. if they fail, show me which ones. ITERATE UNTIL GREEN: /loop run the test suite. fix what fails. repeat until all tests pass. QUEUE DRAIN: /loop 5m check the support ticket queue --until queue depth reaches zero LOG WATCH: /loop 30s tail the error log. alert me if any new errors appear. /LOOP VS /GOAL VS CRON: /loop: timer-driven. repeats your prompt on a schedule. "do this every 5 minutes until I say stop." lives inside your session. /goal: judge-driven. works toward an objective. "keep going until this is achieved." lives inside your session. cron: schedule-driven. runs unattended. "do this every morning at 7am." lives outside all sessions. survives restarts. use /loop for: watching things during a work session. use /goal for: completing a defined objective. use cron for: anything overnight or recurring daily. WORKS EVERYWHERE: CLI, TUI, Desktop app, Telegram, Discord, Slack, WhatsApp, and every other gateway. on messaging platforms the loop fires between your messages. results arrive as ordinary replies in the chat. comment LOOP and I'll send you 5 ready-to-paste /loop commands for CI, deploys, logs, queues, and tests.

• 
  Chris Allen (@theodorvaryag) reported 52 minutes ago

  @landaire @HSVSphere do you still have to do the cargo-blaze thing with reindeer or did they catch up to rules_rust? is the github still a meta-owned dead drop? graph gen is a big issue

• 
  Bhanu Nagar (@bhanu4417) reported 52 minutes ago

  @Coobyk_ Man GitHub is just getting terrible day by day like I get auto logged out then when I try to login error 500 all that shi occurs 2-3 times then I am able to login

• 
  Curious 1 (@CuriousOne_01) reported 59 minutes ago

  @awesome_visuals They just released the source code on GitHub. Try asking Grok about it, then download it and have Grok analyze it. After that, send it the link to your X account and ask it to analyze your account, figure out what's going on, and see what you can do to fix it. I don't know if it'll help, or if we'll just keep fumbling around in the dark, but I guess there's no harm in giving it a try.