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

• 
  Invest Alpha Pro (@InvestAlphaPro) reported 3 minutes ago

  🚨 Nvidia is buying Hugging Face. $12.9B for the GitHub of open source AI, months after they turned Nvidia down at $7B. The breakdown 👇 •Price: $12.9B, one of Nvidia’s largest deals ever. •Rejected offer: $500M at $7B in late 2025. •Multiple: 86x annual revenue. •The logic: locks in the open source developer funnel as OpenAI, Google, Amazon and Anthropic build their own chips. •Timing: landed hours after a $96B quarter. Long $NVDA. NFA

• 
  pdp (@pdp) reported 3 minutes ago

  @markfenner What are the issues in GitHub or Linear if not prompts? You can type them in a centralised database or you can type them in the chat box. It is the same. Also the factory pattern does not apply for iterative tasks such as when developing apps from feedback and input.

• 
  Old Jobobo (@OldJobobo) reported 4 minutes ago

  The public-action layer still needs hard limits. Those eight QA agents reportedly found 28 real issues, then filed all 28 on GitHub within roughly 12 seconds. GitHub flagged the activity as spam and banned the Omarchy bot. Valid findings still need de-duplication, rate limits, and approval gates.

• 
  DFIR Lab (@DFIR_Lab) reported 5 minutes ago

  A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected *** provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured *** Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

• 
  YanXbt (@IBuzovskyi) reported 10 minutes ago

  HERMES AGENT CAN NOW BROWSE AS YOU. YOUR LOGINS. YOUR COOKIES. YOUR SESSIONS. ONE CONFIG LINE. THE AGENT ACTS WITH YOUR REAL BROWSER PROFILE. every browser session in Hermes starts clean by default. logged into nothing. need the agent to check your dashboard? log in first. every time. real profile browsing fixes this. browser: use_real_profile: true one line in config.yaml. or Desktop app: Settings → Browser → Use My Real Browser Profile. the agent now browses with your existing Chrome, Edge, or Brave logins. your cookies. your saved passwords. your preferences. already signed in. HOW IT WORKS: Hermes copies your browser's active profile into a managed snapshot at ~/.hermes/browser-profile/[browser]/ your live browser profile is NEVER opened directly. the snapshot is a separate directory. no profile lock conflicts. no fighting with your running browser. auth files (cookies, logins, preferences) re-sync from your real profile whenever a fresh Hermes session starts. log into a new service in your normal browser. the agent sees it next session. WHAT THIS ENABLES: "check my Vercel dashboard for failed deploys" agent opens Vercel. already logged in. reads the data. "summarize my GitHub notifications" agent opens GitHub. your session. your repos. no OAuth setup. "check my analytics in Google Search Console" agent browses GSC with your Google account. "approve the pending PR on our private repo" agent reads the PR diff. already has access. any site you're logged into in your browser = the agent is logged into it too. SECURITY: this is a consent-gated convenience. OFF by default. you opt in explicitly. a page the agent visits runs with your real logins. only enable it when you want the agent acting as you. when you turn the toggle OFF, Hermes deletes the snapshot store (~/.hermes/browser-profile/). copied credentials don't linger after you revoke consent. WINDOWS NOTE: Chrome/Edge/Brave on Windows holds an exclusive lock on cookie and login databases while the browser is open. Hermes can't copy them while it's running. fix: fully quit the browser (including background/tray instances) before starting a Hermes browser session. or set: browser: real_profile_autoclose: true Hermes will offer to close the browser for you. it asks first. never closes automatically. only on your explicit approval. macOS and Linux can copy the profile while the browser is running. no issue. SUPPORTED BROWSERS: Chrome, Edge, Brave, Chromium. whichever is your OS default. a non-Chromium default (Firefox) = clear error message. no guessing. WORKS WITH ANY BACKEND: local browsing: automatic once the toggle is on. cloud backend (Browserbase, Browser Use): the agent can still open a real-profile local session on demand via browser_exec with the local argument. the cloud backend keeps serving everything else. THE DIFFERENCE: without real profile: "check my dashboard" → agent opens the site → login page → stuck. you paste credentials or set up OAuth. with real profile: "check my dashboard" → agent opens the site → already signed in → done.

• 
  Nicolae Vartolomei (@nvartolomei) reported 12 minutes ago

  Is there an somewhat mature platform with "autonomous coding agents" which I can point to a github repo (medium scale C++ project) and an issue tracker and have it create a drive PRs/tasks to completion based on human PR review feedback? Sounds like this should be a solved problem.

• 
  Shipper Boi (@CoderSafari) reported 12 minutes ago

  @mitsuhiko So, what is the issue here. AI causes too much issue and github has gone down several times. Where is vibe coded github if llm is so great? You can use your flask and ask codex to vibe code it, let me know when you are ready.

• 
  Ofer Shapira (@ofer_shapira) reported 17 minutes ago

  Give Cursor or Claude Code repo access through GitHub CLI and ask: Where did reviews stall? Who knows this area? Which change preceded the error spike? The unlock is not more code. It is evidence on demand.

• 
  Ola (@ola_onlinee) reported 18 minutes ago

  Nvidia just bought the front door to open-source AI. The deal: $12.9B for Hugging Face, the GitHub-like repository where developers find, share, and deploy open models. Reported by The Information, two days after Business Insider said Hugging Face was exploring a sale. Why Nvidia wants it: • Defence. Anthropic and OpenAI are building their own chips to reduce dependence on Nvidia GPUs. If closed labs escape, open models become Nvidia's demand floor and now Nvidia owns where those models live. • Position in the stack. Nvidia dominates the hardware that trains and runs these models. This buys them the layer above: where devs discover models, optimise them for specific hardware, and ship them. • Default optimisation. Own the distribution hub and "runs best on Nvidia" becomes the path of least resistance for millions of developers. Is the price fair? Depends what you're buying. Against revenue, no. Hugging Face reportedly runs around $150M annualised. That's roughly 86x revenue. Against strategy, arguably yes. Hugging Face turned down a $500M Nvidia investment at a $7B valuation last year and just sold for nearly 3x its 2023 valuation of $4.5B. Nvidia forecast a 70% revenue jump next fiscal year and has $18B committed to equity investments. At their scale, $12.9B to control open-model distribution is cheap insurance. They’re not buying a business. They’re buying a chokepoint.

• 
  μck ٤: (@JustMicrock) reported 21 minutes ago

  @theblazehen did you get the startpos feasibility .mdx file? i had uploaded it to the github issue but not sure if you got it in time/its needed at all

• 
  San.D (@sankaram_d) reported 23 minutes ago

  @RyanEls4 😵‍💫😵‍💫😵‍💫 what about the GitHub commit message- small fix /small changes

• 
  Joe Blau (@joeblau) reported 24 minutes ago

  @itsnotryan @github Does it go down with the site?

• 
  Junwei (@Junwei20691749) reported 25 minutes ago

  Finally get to use @bot. Not because canceling other subs granted me Cursor Pro+, but because Cursor Pro was finally approved so I can use it. My submission for the promotion is still under review. Still running into a lot of problems though, like I cannot connect with GitHub. Does anyone else have this issue? @cursor_ai @X

• 
  BowTied Fullstack - Link in bio or NGMI (@BowTiedStack) reported 28 minutes ago

  The most compelling use case I've found on a software engineering side has been automating QA where @Grok @Bot has a dedicated testing email account and can actually do full QA login flows without needing to code them in Playwright. I've also setup different roles for Engineer, Reviewer, Researcher, Product, QA, and had them work with each other to get reviews, address feedback etc. I'm still unsure there really is a ton of benefit from this approach vs. auto-reviewers in Github PRs and my existing Hermes workflows. Grok Bot usage quota has been buggy as hell too. I supposedly burned a month's quota in 4 days, but now it says I've only used 7% while simultaneously erroring half the time that quota is fully used. Certainly some rough edges they need to iron out, even beyond the capability limits of Grok-4.6.

• 
  Abhishek (@aacle_) reported 30 minutes ago

  A public GitHub issue → GCP Editor access. That sounds fake, but the attack chain was actually this: Attacker leaves a malicious comment on GitHub. Gemini CLI reads it. The prompt injection gets the agent to execute commands on the CI runner. From there, the attacker finds cloud credentials and impersonates a service account with Editor-level access.

• 
  Bohdan | Gamma Prime (@B_GammaPrime) reported 31 minutes ago

  Last year, Hugging Face reportedly turned down $500 million from NVIDIA at a $7 billion valuation. Yesterday it reportedly agreed to sell to Nvidia for $12.9 billion. Saying no was worth roughly $6 billion. Here's what Nvidia is actually buying. Hugging Face isn't a model company. It's the repository where open-source models live - the place developers go to download, fine-tune and share them. GitHub, but for AI weights. Nvidia sells the chips those models train and run on. It already owns the compute layer. What it didn't own is the layer where developers decide which model to use in the first place. That's the pattern worth noticing. Stripe just bought OpenRouter - the router that sits between companies and 400+ AI models. Vanguard just bought Altruist - the custody platform advisors allocate from. Now Nvidia is buying the repository open-source AI flows through. Three deals. Three industries. Same shape. Nobody is buying the product. They're buying the layer that decides which product gets used. Nvidia was already an investor in Hugging Face - it joined the $235 million round in 2023 at a $4.5 billion valuation, alongside Google, Amazon and Salesforce. Sitting on the cap table wasn't enough. Owning a piece of the distribution layer isn't the same as controlling it. The compute is commoditising. Models are commoditising faster. The one thing that doesn't commoditise is the place everyone has to pass through.

• 
  pulpmatrix (@pulpmatrix) reported 33 minutes ago

  Confirmed. Prime Intellect's writeup is public: GPT-5.6 Sol Pro, offline sandbox, hand-rolled a raw Responses API call to the interception proxy and used file_url to make the inference server fetch a GitHub API response for it.

• 
  Nick (@maietta) reported 33 minutes ago

  @robot_sox I run my own gitlab server and also self-host repos directly on my main domain. It's just that for this project I am still stuck on GitHub only because other people might need to access the code base and are already in that ecosystem. I will eventually move them over to my system.

• 
  Bilal (@BilalBudhani) reported 36 minutes ago

  Github down again?

• 
  Aloys Zunguzungu (@zunguzungu_III) reported 37 minutes ago

  @cynthiamcgillis Suggestion: create a github issue, ask Claude to implement a fix and then ask Codex to review Claude work. And vice versa. Codex always comes out on top.

• 
  Dharmendra Jagodana (@Dharmendra_Jago) reported 38 minutes ago

  Shipping notes from this week on BuildBase. Nothing on the headline features. A quiet infra week - the kind that doesn't sell a landing page but decides whether a platform feels tight or janky six months in. What went out: - New Relic wired in for logs. Structured search across the tenant server instead of grepping stdout when something goes sideways at 2am. - Status check endpoint reworked so uptime probes and internal dashboards reflect what's actually happening under the hood (Mongo, Redis, queues) instead of just returning 200. - Console login page redesigned. Docs, changelog, GitHub, support - all baked directly into the login screen instead of buried three clicks deep. - Handful of small fixes across the console. We're pre-first-paying-customer, so I feel every rough edge before customers do. That's the deal for now - fix it in the dark, then invite people in. If you're building something on React or Next.js that needs auth, workspaces, usage-based billing, notifications - happy to show you around. Links in the first comment.

• 
  Choppy (@ChoppyTech) reported 41 minutes ago

  @FlowAltDelete One of my biggest issues right now is preventing all users from building agents with the GitHub harness, unless approved - manual check and informing the user is the only method I have right now 😭

• 
  José ‘The VR Tech’ 🥽 (@josethevrtech) reported 41 minutes ago

  @StonedModder @Tieguaili3D You do know most modders don’t even release a GitHub right? Which is a whole different problem.

• 
  AminTechs (@AminTechs) reported 45 minutes ago

  @gopikl @bot A GitHub issue is not a Claude Routine trigger. Docs: GitHub triggers subscribe to pull_request and release only. issues.opened is not on the list. You also need the Claude GitHub App installed — `/web-setup` clones, it does not enable webhooks.

• 
  AlicZhang (@ZhangAlic) reported 45 minutes ago

  That line of reasoning is flawed. GitHub is a product with a robust, battle-tested engineering foundation, precisely because the problem it addresses is inherently complex. In the past, average users needed to learn how to interact with it to unlock its full value. Today, average users should access it via AI—which knows how to leverage GitHub effectively—rather than trying to reinvent *** specifically for the layperson. Doing so would only conflate two distinct issues—code version management and barrier-free usability for non-experts—resulting in a product that ultimately fails to deliver a good user experience.

• 
  Smakosh (@smakosh) reported 53 minutes ago

  This is why GitHub keeps going down

• 
  Mainak Mukherjee 🇮🇳 (@MainakMukh47974) reported 57 minutes ago

  Now there is a long process that takes place between development and production. First, you write the code; then the code is uploaded to the remote server, where an executable of that code is built, and that is known as the "build" process. This is then tested and deployed. Manually doing it every time you push some new changes is very annoying and hence there is a way to automate it using CI/CD tools like GitHub Actions. So every time a new code is pushed, the build->test->deploy pipeline gets triggered automatically.

• 
  Joshua Stanton (@ShiftingPathway) reported 58 minutes ago

  @kilocode Great but why is it impossible to paste into your Kilo Code CLI prompt field. This is absurdly annoying and intermittent. Its been an issue in your github issues repeatedly for months. I don't understand why you would focus on a new app rather than making basic functionality work

• 
  Andrea Griffini (@agriffini) reported 59 minutes ago

  @Waffl3x @schteppe include guard and missing inline on rnd/random_engine were obvious typos. /dev/urandom is also a slip (that wouldn't work on windows), but reading about why not using just default constructor things are a bit more hairy. C++20 as of today is not something I can use (the toolchains with must use for other reasons don't support it). My guess is that MANY have these kinds of problems in real sw development world. Indeed the very first version I even used T * for shuffle instead of iterators, but before uploading decided make the pointer itself the type. Never in my life had to random_shuffle anything that was not a contiguous range of stuff in memory. Then added the container shuffle version (and for quite long had a bug for a missing include: std::begin/std::end are not available, in general, if you just include the container). Seems indeed even current version on github has that missing include bug. I didn't update. The whole thing of providing my own shuffle (it would be nonsense, in a sane world) was just because of an obvious huge bug in gcc std::random_shuffle implementation that wasn't corrected for several YEARS despite providing a patch (a bug that I found by observing the big problems it created, not just something rare or just theoretical). One important part for me is debugging and controlling the seed; a big issue I have with using what <random> provides is that there's no way to get portably the same results (unless I'm mistaken: e.g. std::uniform_int_distribution is only specified in terms of statistical properties, not that on different platforms if provided the same seeding will produce the same output). Xorshift initialized using time (and thread ids as I often work on high CPUs counts that often start working on threads in the same millisecond) has been good enough for my uses, it's 3 (literally three) instructions and has none of these substantial problems.

• 
  kitze 🛠️ tinkerer.club (@thekitze) reported 1 hour ago

  i use Plunk for transactional emails but sign in with github is not working and im currently fcked so im exploring other options resend free plan is annoying and useSend free plan is annoying (100 emails per day is super limiting) any other suggestions? i'm not paying $20/mo for sending emails in the year of our lord 2026 when self hosting is a thing