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%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	4 days ago
Paris	Website Down	8 days ago
Saint-Paul	Website Down	8 days ago
Saint-Paul	Website Down	9 days ago
Mexico City	Sign in	9 days ago
León de los Aldama	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:

• 
  Dan (@aidaniil) reported 37 seconds ago

  another github outage time for someone to build a better one

• 
  a thousand eyes (@wittenberg0rca) reported 1 minute ago

  @hydratedgorilla @github @vercel which of the two has the issue?

• 
  Greg Mushen (@gregmushen) reported 1 minute ago

  @Macrike @Brady_H @hubermanlab I would be interested in reading those papers. I know there have been recent modeling papers from Stanford and I believe he may be referring to the **** paper since he shared Figure 3 of that study if I recall correctly last year. In that paper, both permanent DST and ST resulted in better outcomes than switching for obesity and stroke. But if you compared ST and DST the differences for either were tiny. Like 0.27% for obesity and 0.02% for stroke. But if you look at the confidence intervals, they are quite wide. But there's no confidence interval for DST - ST and no p-value. So it's impossible to tell if it's significant or not. Also, that paper was recently corrected in April of this year. That is a substantial correction, and what the correction does not say is if it impacted these numbers or not. They do have everything checked into Github, so I guess if you were curious, you could find the commit that fixed it and test on the data set pre/post. This reminds me of this intra time zone study I remember reading a few years back. At first, the paper thought they saw more negative outcomes for people in the Western edge of timezones, so people glommed on to that conclusion. However, a few years later they found an error in the data set, and once they corrected that, there was no difference. This is classic modeling type stuff. It happens to everyone who tries to model anything. But even then, these are just models. They estimate what may happen and have to make assumptions to do so, such as assuming that bedtimes are fixed from 10pm-7am. Do people actually behave this way? Probably not. In fact, that would have been a really great addition to the model...a sensitivity analysis on the factors they assumed were fixed. That would make the model much more robust actually. That and time zone comparison with a p value would make the paper mucho stronger. But that's why I think Steponenaite et al 2026 is a great paper because it doesn't lean on mechanisms or models. It's purely epidemiological. And while that has its obvious downsides, if you're not seeing strong signal across 157 papers in 36 countries, that in itself is a strong signal. It mirrors what we see in this modeling paper as well. There are big advantages to sticking to a permanent time zone, but there doesn't seem to be strong evidence for one vs. the other.

• 
  Data Value Consulting (@DVC_analytics) reported 3 minutes ago

  SWE-bench Verified: 500 human-filtered GitHub issues; a patch must pass the real repo's tests. Claude Mythos 5 leads at 95.5% (July 2026). Catch: many issues predate 2024, likely in training data. SWE-bench Pro (1,865 tasks, private repos) shows a steep drop from that number.

• 
  Dominik Koch (@dominikkoch) reported 5 minutes ago

  @jacobmparis @vercel Since github is up again here is my second thing: This ui looks great but whenever I have a new app/package to deploy I cant because its not on main yet and the input is disabled This isnt a big issue for most apps but nowadays where I deploy more and more eve agents its annoying, the dashboard depends on the agent but I cant deploy the agent until I merge the full pr to main. Then I either have to cancel the dashboard deployment or risk them being out of sync while I configure the agents env

• 
  Tolys ✨ (@0x0001337) reported 6 minutes ago

  @MetaMask AI checker just ruined our Wallet Connection. Waiting for resolution in github issue

• 
  Jochen Kirstätter (JoKi) (@JKirstaetter) reported 7 minutes ago

  @Ryan_Hecht @github Hi, the same one that was perfectly acceptable during the previous months. I ran an /update and got this as a result. Seems like a regression issue. Still on mobile, gonna check the setting and report back. Thanks.

• 
  Polsia (@polsia) reported 8 minutes ago

  PRs are piling up, AI-generated code is filling repos with new attack surfaces, and manual review can't keep pace. Built CodeSentinel to fix that. It monitors your GitHub repos, reviews every pull request, and streams findings to your dashboard in real time.

• 
  atmen (@atmen189) reported 8 minutes ago

  Fed it a briefing on OpenClaw - the AI agent blowing up on GitHub right now. Got 9minutes of two AI hosts breaking down the $2K -$6K setup fees, security risks, and why it’s different from a regular chatbot. Sounded like a real podcast, not a summary.

• 
  Dylan Mikus (@dbmikus) reported 15 minutes ago

  @dexhorthy I haven't manually made a GitHub PR or pushed a commit in months I prefer spending $0.20 to tell Fable to `*** commit 'fix code' && *** push --force-with-lease`

• 
  Nav Toor (@heynavtoor) reported 15 minutes ago

  You Googled "password generator." The first result has four ads at the top. A popup for your email. A cookie banner. And a text box where you type a password. You copy the password. You use it for your bank. That website now knows a password you use. On a server you do not own. In a database you cannot delete. Run by a company you have never heard of. A French developer named Corentin Thomasset built 86 tools like this. All in one place. All local. Nothing gets sent anywhere. It is called IT-Tools. 39,834 stars on GitHub. One Docker command. docker run -d -p 8080:80 corentinth/it-tools:latest Done. Every tool runs in your browser. No backend. No database. Nothing leaves your machine. Here is what you never have to Google again: Password generator. Any length. Nothing logged. QR code maker. No site tracks what you encode. WiFi QR code. Guests scan and join. No shouting passwords. Hash maker. SHA-256, MD5, and more. Local only. Base64 encoder and decoder. Paste safely. UUID generator. Instant. JWT decoder. No pasting tokens into a stranger's site. JSON, YAML, XML, and SQL formatter. Color converter. HEX, RGB, HSL. Crontab builder. Chmod calculator. Docker run to Docker Compose converter. Lorem ipsum text. Regex tester. 86 tools. One container. One command. Who uses this: A developer who stopped pasting JWT tokens into random sites. Those tokens hold user IDs, emails, and role info. Every free decoder site reads all of it. A designer sick of color converters wrapped in ads. A sysadmin who stopped Googling "chmod 755" for the tenth time. Anyone who saw the trick. Every free tool is free because your input is the product. 39,834 stars. GPL-3.0 license. Vue.js. The code cannot be pulled from you. Next time you need a quick tool, you have two choices. Google it and hand your data to a stranger. Or open localhost:8080 and keep it to yourself. (Link in the comments)

• 
  Steven Grant (@1stevengrant) reported 17 minutes ago

  @owenconti @laravel github had issues but those now resolved and my repo connections are now totally fubarred

• 
  bizz | AI software solutions (@bizzaidev) reported 19 minutes ago

  2/ The tool: Libretto PR agents — free TypeScript. Add a try/catch line and it pulls the failure session (via CDP), inspects the page with injected Playwright/JS, and opens a GitHub PR proposing a fix. No full runtime migration required.

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 22 minutes ago

  I have a custom agent framework and run different agents in different terminal windows. I can run them on the same project and ask different models and compare the results. The first request to the highest OpenAI project mangled my parallel processor output, but likely my bad input. I fixed that and since then using an open AI model that seems to be ok is working with few errors. I also switched back to Anthropic a bit and almost immediately got the system crash I’ve been reporting on my mistake tracker on GitHub. Too early to tell if it is really only Anthropic or AWS but so far has not happened with OpenAI models. It’s pretty slow going but I’ll take it for accuracy and especially if it costs less due to selected model and fewer mistakes. Tracking…. AWS Wishlist item granted! Thank you 🧡

• 
  Feral (@feraltekk) reported 22 minutes ago

  Most people connect Obsidian to Claude and then spend forever re-explaining how their vault is built. The fix is five skills made by the person who actually designed Obsidian's file system. Claude follows the real rules instead of winging it. Five skills. Two commands to add them. From then on Claude loads them every time it touches a note. 39,000 stars on GitHub. Barely anyone is using it yet. And once Claude actually understands your vault, the loop can start. You have written the same idea three times this year. You do not know that yet. Your notes app does. A loop rereads the vault every six hours. Finds what repeats. Flags what was abandoned. Surfaces the note you forgot you wrote. You cannot see your own patterns from inside your own head. The loop does it now.

• 
  HalxDocs (@HalxDocs) reported 32 minutes ago

  Reqit crossed 300 downloads this week. No ads, no VC, no launch hype just people who wanted an API client that doesn't need a login. We also just shipped v1.0.1 — the biggest hardening release yet. Here's what changed: Security & stability • AI API keys now stored in your OS keychain (never plaintext on disk) • Script execution gets a 10s timeout (no more runaway Goja VMs) • Request body reads capped at 10MB • Collection runner cancellation actually works now 40+ error handling fixes across the Go backend Silent failures in GraphQL, registry, MQTT, mock recording, interceptor — all caught and surfaced now. If something breaks, you'll know about it instead of getting a mysterious empty response. Frontend improvements • Focus trap on all modals (Tab/Shift+Tab cycles properly) • Escape key closes every open modal • Confirm dialogs on destructive actions (delete collection, clear history, etc.) • Error boundary wraps the entire app The updater just works v1.0.1 auto-updates from the dashboard. Build binaries → upload to GitHub release with latest.json → users get the update. No manual downloads needed. 📦 Full changelog: ✓ 300 downloads milestone banner ✓ OS keychain for AI keys ✓ 40+ Go error handling fixes ✓ Modal focus traps ✓ Collection runner cancellation ✓ Script timeout safety ✓ Frontend error boundary Link in the CS What feature do you want next? 👇

• 
  ORION (@OrionAdept) reported 34 minutes ago

  Major GitHub outage 👀

• 
  Richard Geldreich 🇺🇸 (@richgel999) reported 36 minutes ago

  "Frame is an X11 server written in pure x86_64 Assembly... Frame was created over the past month largely via Claude Code. The Assembly code in all its glory can be found on GitHub."

• 
  Hackyard (@HackyardSocial) reported 40 minutes ago

  Working on getting more ways to work signing in on Hackyard signup. GitHub sign in works. Working on regular email & X sign in.

• 
  Douglas (@douglastweets) reported 43 minutes ago

  @thsottiaux @OpenAI I feel like I’ve been getting a lot of apply patch issues on the Windows (work machine) since the big update combining the apps. As a result, changes take forever to make. I see a couple similar reports on GitHub but not sure if they align exactly with what I’m experiencing.

• 
  Sudo su (@sudoingX) reported 44 minutes ago

  now i'm running the harness fight i've wanted to run for a month. hermes agent vs openclaw, same model, same tasks, both pointed at a 3.9gb bonsai on a single 3090. lean vs bloated, head to head, and i post whatever happens. disclosure first, i contribute to hermes, so i'm not pretending i'm neutral. what i can do is make it a fair fight. upstream versions of both, same local endpoint, no fork tricks, and let the receipts talk. here's what's actually in each box. > hermes agent. a one-file agent loop, around 25 direct dependencies. it parses and repairs tool calls off many model families natively, which is the whole reason it reads what a local model actually emits. built for open weights from day one. #1 on openrouter by daily usage. > openclaw. thousands of typescript files, roughly double the dependencies. for years it leaned on the server to parse tool calls and only shipped its own repair recently, for a single format. way more github stars than hermes. built for the big api models, and it shows. now the honest part. i uninstalled openclaw months ago. my experience was that it was built for someone else's models, it choked on local, and the bloat made it slow just to start. but that was months ago and these things move fast. maybe they fixed the local story. maybe the parsers are there now. i'm not going to assume, i'm going to run it. that's the whole test. can either harness hold a tool-calling loop on a 3.9gb model without falling apart. one early tester says bonsai breaks on iteration, another says it tops agentic benchmarks. that split might not be the model at all. it might be the harness. this is what finds out. results coming. i'm not calling it early.

• 
  Michael Carpenter (@wiggycorp) reported 44 minutes ago

  Dang. GitHub is down. Too bad, I guess users will have to wait for these updates.

• 
  Himasagar Rangumudri (@rangumudri7607) reported 44 minutes ago

  @its_amitchauhan @github Are you still facing the issue??

• 
  Shiva Shiva (@hyperinteger) reported 44 minutes ago

  May be you should and relieve .@github from the incompetent clutches of .@satyanadella who dragged it down to Microsoft quality.

• 
  Ben Anthony (@benjamin_ACD) reported 45 minutes ago

  GitHub goes down at the most inconvenient times

• 
  Shyam Tawli (@shyam_tawli) reported 47 minutes ago

  @iamsahaj_xyz @github what was the issue?

• 
  mischa_u (@MischaU8) reported 51 minutes ago

  @10_X_eng will do, let me get codex to generate some useful context and I'll raise a github issue.

• 
  Harman (@itsharmanjot) reported 52 minutes ago

  Claude writes an HTML artifact. Instead of eyeballing it in a chat window, I open it in an actual local review surface, click the exact element that’s wrong, and queue that feedback for the agent to pick up. It’s called Lavish. A local CLI that turns any agent-generated HTML file into an interactive review page, so you’re not scrolling through raw markdown to catch a mistake. → Opens agent-generated HTML in your own browser, click any element or highlight any text, and it captures the precise target, not just “somewhere in this file” → Edit rendered Mermaid diagrams like a whiteboard, then queue that exact change as feedback for the agent → Runs entirely local. No cloud round-trip to view or annotate an artifact, session state stays on your machine under .lavish-axi/ → Ships built-in playbooks for diagrams, tables, comparisons, plans, code diffs, input collection, and slides, so the agent knows how to structure what it’s showing you before it writes the HTML → Session hooks plug directly into Claude Code, Codex, OpenCode, and GitHub Copilot CLI, so it triggers automatically instead of being a separate tool you have to remember to open → Runs a layout audit before it even shows you the artifact, catching overflow, clipped text, and broken elements before you waste time reviewing a broken render No install required, it runs on demand through npx -y lavish-axi. Every AI coding tool generates plans, diagrams, and comparisons buried in chat text you have to parse manually. Lavish turns that output into something you can actually click on and correct. MIT License. Built by Kun Chen.

• 
  Kshitij Mishra | AI & Tech (@DAIEvolutionHub) reported 55 minutes ago

  A NEW OPEN-SOURCE TOOL JUST MADE VIDEO DOWNLOADING RIDICULOUSLY SIMPLE. It's called ReClip. A self-hosted GitHub project that lets you download videos (or audio) from 1,000+ websites without ads, trackers, or subscriptions. Just paste a URL and you're done. It supports platforms like YouTube, TikTok, Instagram, X, and hundreds more. What you get: ↳ Download videos as MP4 or extract audio as MP3 ↳ Choose the video quality before downloading ↳ Queue multiple links with batch downloads ↳ Clean browser-based interface ↳ Lightweight self-hosted deployment ↳ No login, no limits, no hidden catches The growth has been impressive too: 📈 1,400+ GitHub stars in just 9 days 📦 239+ forks already That traction isn't surprising. For years, people have had to deal with download sites packed with ads, pop-ups, fake buttons, and privacy concerns. ReClip takes a completely different approach. You host it yourself. Your files stay on your machine. Your data stays yours. No premium paywall. No data collection. No endless upsells. Just a lightweight open-source project released under the MIT License and built to do one job well. Free. Open source. And likely to become a favorite for anyone who downloads media regularly. 👇

• 
  Sahaj (@iamsahaj_xyz) reported 59 minutes ago

  @gauravmandall @github fyi you can submit a support ticket. there's a "can't sign in" button on the login page but it's not obvious