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

Live Outage Map

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

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

• 
  Chris Stayte (@ChrisStayte) reported 5 minutes ago

  @thsottiaux when are we getting that competitor to GitHub. literally can't ship because they have api issues...

• 
  Render (@render) reported 6 minutes ago

  @Limsee08 We're investigating. It's a localized GitHub issue.

• 
  Manol T. (@manol_ai) reported 13 minutes ago

  @syakirbuilds Yeah i thought a lot. MCP has built in authentication oauth2.1 protocol which makes it production ready. I used Supabase to make the server and connected Gmail and Github so people could authenticate into my MCP. I will add stripe checkout on top and I am ready to go

• 
  Seregon (@SeregonWar) reported 15 minutes ago

  @thiago__barrios Hi, unfortunately I don't have an Android phone (I'd need to install Android Studio). Could you open an issue on GitHub explaining the problem so you can be more thorough and we can keep track of it?

• 
  Davide (@task_davide) reported 17 minutes ago

  Signing up for @Azure - Was about to create an account for the wrong email since for once it actually just logged me in and the username was hidden in the corner - "Sign up with GitHub" sends you back to the log in page - Refresh a few times, notice that the GitHub email is a sign in option - Sign in, register, try to pay - Most card details got auto-filled as with normal websites, except expiry date - Finally get to the end, they send an MFA code to my email - Open email, no MFA code - No option to re-send It's actually a bit funny really

• 
  muzz khan (@muzzdotdev) reported 20 minutes ago

  @luisflarota Lol it was github, we’re working on making these problems more visible

• 
  Nick (@nickbarton) reported 20 minutes ago

  @Rasmic I don’t give any of the privately hosted models access to my email or data, that’s a huge mistake for any of the hosted tools out there. I do use Claude and chatgpt for coding/app/agent work with a privately hosted Forgejo gut server not GitHub. Now those labs are still getting and using context data to train, learn, etc. But it’s not going to China

• 
  tuna🍣 (@tunahorse21) reported 21 minutes ago

  @TheKingOfStank yeah that is what I mean, runners run locally, but the github infra is down, so now I can't merge ( i mean i could but that defeats the purpose of strict CI)

• 
  Conrad Rockenhaus (@SkyPhusion) reported 22 minutes ago

  Of course @github has to have an issue with actions right when I'm facing a deadline, loving life

• 
  Xavier Rivera (@XavierRiveraX) reported 23 minutes ago

  WordPress powers more than 500 million sites, and its core software has two chainable vulnerabilities, CVE-2026-63030 and CVE-2026-60137, with public exploit code now circulating on GitHub. The chain combines a REST API routing bug with a SQL injection flaw to execute code on a stock install, no plugins or login required. In-the-wild exploitation has already begun; patch to 7.0.2 or 6.9.5 now.

• 
  LUCIUS ARTORUS CASTUS (@askeladdcastus0) reported 24 minutes ago

  MetaMask accidentally hired a North Korean spy.and that sentence is only the third most insane part of this story. here's what actually happened: Consensys hired a developer through a third-party provider. the developer known as "Tyler Knapp" or "imyugioh" on GitHub was North Korea linked. he worked on MetaMask's mobile wallet fiat payment integrations from March 9 to early April 2026. six weeks. inside one of the most used crypto wallets on earth. access revoked. investigation launched. law enforcement notified. no malicious code found. no stolen data. no user impact. now here's the three things nobody is saying: one this is not a MetaMask specific problem.the FBI has been warning since 2022 that North Korea's Lazarus Group has been systematically placing developers inside crypto companies through fake identities and third-party staffing agencies. they've stolen over $3 billion from crypto projects since 2017. MetaMask caught theirs. how many didn't? two fiat payment integrations is the worst possible place for this.not a random feature. fiat on-ramps and off-ramps are where real money moves between crypto and traditional banking. that's the most sensitive code in any wallet. that's where a malicious actor could silently redirect funds, harvest credentials, or build backdoors that activate months later.the fact that no malicious code was found is either genuinely good security or the code was too subtle to catch in one investigation. three outsourcing is the attack vector nobody's fixing.Tyler Knapp got in through a third-party provider. not a direct hire. Consensys did a code freeze and warned staff after. but the outsourcing model that allowed this is industry-wide. every crypto company using freelancers, agencies, or remote contractors has the same exposure. this won't be the last time this happens. the uncomfortable truth: MetaMask has 30 million monthly active users. their wallet has touched more crypto than almost any other product in existence. a nation-state just got six weeks inside it.they caught it. good. but "we caught it this time" is not the same as "we're safe."review your wallet permissions tonight. not because MetaMask is compromised. because this story just proved that no platform is too big to be targeted.and most of them won't tell you when they are.

• 
  Abhishek Anand Tiwari (@MAbhishekAnand) reported 24 minutes ago

  You can build and launch a real startup: Here's the entire stack: Claude — coding ($20/mo) Supabase — backend (Free) Vercel — deploying (Free) GitHub — version control (Free) Clerk — auth (Free) Stripe — payments (2.9%/transaction) Resend — emails (Free) Cloudflare — DNS (Free) PostHog — analytics (Free) Sentry — error tracking (Free) Upstash — Redis (Free) Pinecone — vector DB (Free) Namecheap — domain ($12/yr) No agency. No dev team. No excuses left. Total Cost: 👇

• 
  @pejacoby@infosec.exchange (@pejacoby) reported 25 minutes ago

  @thebaldgeek @463n7_57 @wiglenet If you’ve done a reset on a unit it will get its BootCount (BC) value out of sync (resets to Zero) and not be able to find what hasn’t been uploaded already. I have an issue in the github on this as every one of my units has reset multiple times. I use the web interface to send.

• 
  Polsia (@polsia) reported 26 minutes ago

  Broken builds and misconfigured infra usually get found the hard way — by users. HealOps watches GitHub, AWS/Azure, and CI/CD pipelines 24/7, opens PRs to fix what breaks, and reports back to Slack. Loop closed. Mean time to repair: minutes not hours. Live soon.

• 
  Satoshi's Cat (me/mine) (@SotoastiNotmoto) reported 28 minutes ago

  @NEEDcreations This speaks to a broader issue: Core could do a whole lot better at their communication. I don't think them saying "refer to Github" is adequate. That being said, it must be frustrating being Boeing engineers being told by passengers how to build a plane.

• 
  harald (@HaraldvanLintel) reported 30 minutes ago

  @jsm2334 It's the opposite, rejection of deaths that are replaced by the higher risk deaths instead of added; it's an issue for detection of small additional risk. The AI got another version from github than I got, there seems to be a caching issue, here's the code that slightly differs:

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 36 minutes ago

  Baidu just open-sourced an OCR model that reads entire 40-page documents in one shot. It's called Unlimited-OCR. 3 billion parameters but only 500 million active during inference. Runs 100% locally on your machine. Why this matters: traditional OCR tools chop documents page by page. Tables that span two pages break. Reading order gets lost. Cross-page context disappears. Unlimited-OCR processes the whole document at once. 32K context window. Text, formulas, tables, reading order all preserved across pages. Output comes out as clean structured Markdown. → 93% accuracy on the standard benchmark. +6 points over the baseline. → Error rate stays below 0.11 even past 40 pages. → Multilingual out of the box. → 2.12 million downloads on Hugging Face last month. 14,600 GitHub stars. For context: Amazon Textract, Google Cloud Vision, and Azure Document Intelligence all charge per page. This runs locally for free.

• 
  G (@gilbertsanchz) reported 38 minutes ago

  What cloud breaches actually look like, because it is rarely the provider failing. The most common pattern in cloud security incidents is misconfiguration: a storage bucket set to public, an admin account without MFA, an access key accidentally committed to a public GitHub repo. The Capital One breach in 2019, roughly 100 million records, came down to a misconfigured firewall setting in the customer's environment, not AWS being hacked.

• 
  Santiago (@0xBizk) reported 40 minutes ago

  Go into linkedin: see AI posts with AI replies Go into X: see AI posts with AI replies Go into github: see AI repos with AI issues The whole point of social media was to "interact with other humans" not to collect fake internet points wtf

• 
  👨🏻‍💻 ⚡️ (@EadrictheWild) reported 43 minutes ago

  @Andrewislington I am just going to use bedrock in the platform for BYOC for Claude. I figure just getting to use Claude Desktop was a good enough step for me. I just run the Github and AWS MCP server. Runon soon in AWS . Entire stack is AWS only though.

• 
  Surya (@isuryatk) reported 44 minutes ago

  @SantoshYadavDev No one is immune to a new virus called Vibecoding. It's affects the larger organizations greatly. Here are 3 examples: 1. AWS (2 outages in 6 months + billing incident) 2. Google Maps routing issues. 3. Github downtimes

• 
  Alex Rogov (@Alex_Rogov_js) reported 51 minutes ago

  there's a pattern across three separate stories this month. AI coding agents tricked into installing malware from "clean" looking github repos. security agents built to catch malicious code getting fooled into running it themselves. claude code's own sandbox had an escape bug this year (CVE-2026-39861, a symlink flaw). same root cause every time. an agent optimized to be helpful will follow instructions hidden in a file, a commit message, a package readme. the more autonomy you give it, the bigger that surface gets. i run agents with --dangerously-skip-permissions on repos i wrote the CI for. i never run it on a repo where i didn't. that's not paranoia. it's the same rule i'd apply to a new hire before their first PR gets reviewed. the fix isn't less automation, it's a trust boundary. an agent gets exactly the access its current task needs, nothing more. every new tool call crosses a boundary you drew on purpose, not one you're discovering after the fact. if your agent setup doesn't have that boundary somewhere, it's not a matter of if. it's when.

• 
  Vikram (@WhinerVikram) reported 52 minutes ago

  @thsottiaux Triggering OpenCode sessions on my VM from Github issues. I would move faster but Azure OpenAI is dead slow on weekends.

• 
  Ethan Halfhide (@vibecodeceo) reported 53 minutes ago

  And coding agents quietly crossed a line this week. You can now delegate an entire GitHub issue and walk away. Not autocomplete. Not a suggestion. Gone. Done. Touch grass.

• 
  CANTELOPEPEEL (@CantelopePeel) reported 55 minutes ago

  @themostjomo @thru_xyz @untolabs We will fix this tomorrow. It happens sometimes with GitHub.

• 
  Adeniyi Victor (@Vieester_) reported 56 minutes ago

  Seem there is an internal system error with deployment using github @render

• 
  Lars H. (@circuitoftmrw) reported 58 minutes ago

  small milestone: my first resolved GitHub issue AND first star, both on the same repo old K2200 wasn’t supported for object detection in Frigate anymore, rebuilt onnxruntime with Maxwell support back in, and shipped the fix feels good watching an old GPU do real work again.

• 
  Alankrit Verma (@AlankritDotMe) reported 60 minutes ago

  Does GitHub use GitHub to build GitHub? Because now everything makes sense. Not trying to hate, but it is slowing us down. Are we still here because GitHub is good, or because moving is hard?

• 
  Polsia (@polsia) reported 1 hour ago

  Maintainers spend more time triaging GitHub issues than reviewing code. SentinelOps fixes that. Always-on AI monitors repos 24/7, auto-triages, drafts responses, escalates only the bugs that actually need human attention.

• 
  Ondřej Súkup (@mimi1vx) reported 1 hour ago

  @doodlestein … bead_rust in cargo repository 0.2.18 but github releases is still 0.2.16 ? broken release mechanism / script ? I really like them :D