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

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	20 hours ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  Sonic-Iso (@Sonic_Iso) reported 6 minutes ago

  anyone test the emulators on latest fw with star wars? curious how people are enjoying them if anyone has used them yet. i ask because ive only seen one person so far take screenshots and i dont see any issues on github. if you guys dont want emulators i guess i can go back to the drawing board.

• 
  riVeN (@r1VeN2k) reported 11 minutes ago

  this is the first video i've seen where the permission list is actually visible. every box in it is ticked. pause at 0:34. vs code opens a panel: "select tools that are available" — 27 selected, 41 total, checkboxes down the side. scroll the list. search_users. search_code. list_issues. get_pull_request. all reads, all fine. then merge_pull_request, same list, same blue check, already on. that one puts code into a branch. it sits between "search for users on github" and "list and filter repository pull requests" like it's the same category of thing. so the granular control everyone says is missing does exist. it just ships with everything enabled, which means the decision gets made by a default instead of by you. same outcome as no gate at all, reached politely. unticking one box takes a second. knowing which box is the whole problem. i wrote up where that line sits and why two platforms drew it in opposite places two months apart. pinned.

• 
  1mmモジュール (@1mm_module) reported 11 minutes ago

  @Eto_Madjas I’ve identified the cause. I sincerely apologize for the issue. When the PC’s system code page is set to CP1252, some of the UTF-8 processing in setup.bat does not work correctly. I’ll fix this issue so that the setup can be completed regardless of the system’s encoding settings. I’m going to start working on the fix right away. Once it’s complete, I’ll update the files on GitHub and let you know.

• 
  Gareth Loot (@GarethLoot) reported 12 minutes ago

  @Kri0725 Putting OpenAI under Tesla for funding does not prove it would have stopped being open. The emails show the point was compute and money. A nonprofit could not raise what was needed to compete with Google. That is a funding argument, not proof the models would have been locked away. xAI, Grok and Cursor were never set up as nonprofits or as open-source projects the way OpenAI started. xAI launched as a for-profit. Cursor was a venture-backed commercial company from the beginning. There is no matching broken promise, so the consistency charge does not hold on those terms. On the “closed empire” point: Grok-1 weights and architecture were released under Apache 2.0, later Grok weights were published, Grok Build was open-sourced, and the X recommendation algorithm was put on GitHub. Tesla also open-sourced the original Roadster design and software and has said it will do the same for Model S and Model X. That is not the same as claiming every current frontier model is open. It is enough to say the record is not one-sided.

• 
  John Koretoff (@JohnKoretoff) reported 17 minutes ago

  You can print a floor plan of a foundry forever. You cannot print the foundry. That is the cut this week keeps making, and it lands hardest on the physical layer. Tokens are cheap. First drafts are cheap. The thing that turns a model into a factory still sits on megawatts, wafers, and a queue you cannot hurry with another prompt. When copies are cheap, the scarce object is not another model card. It is energized capacity and the silicon that fills it. Lennart Heim has put numbers on the silicon side. A one-gigawatt data center, on his public math, wants on the order of fifty thousand logic wafers and more than a hundred and eighty thousand DRAM wafers. That is not a metaphor. That is the bill of materials for a campus that can actually run. Memory and logic do not print the way text does. A wafer start is a physical commitment in a fab that already has a queue. Power is the twin. Interconnection takes years. A utility contract is not a GitHub issue. JLL's midyear North America print put vacancy at about one percent for a third straight year, with tens of gigawatts under construction already spoken for. Halls go up. The scarce part is still the megawatts that arrive on time, and the permission to pull them. Permission is the soft word for a hard gate. Who gets to connect. Who gets to energize. Who gets to run a non-deterministic agent against a production system once the power and the chips are real. I already wrote that the bottleneck moved from talent to permission. The physical layer is why. You do not get a trace of an agent that matters if the box it runs on never got power. You do not get a standard message that scales if the product itself cannot ship inference. You do not get a scarcity bid in money if the world can print every claim except the one that settles. The week rhymes on purpose. Copies got cheap in the model layer, so the log became the scarce record. Copies got cheap in GTM, so the standard became the scarce score. Copies got cheap in money narratives, so unprintable settlement stayed scarce. Equity narratives print. Cash-flowing advantages do not. Here the same cut hits the substrate. You can generate infinite plans for a data center. You still need the wafers, the interconnect, and someone willing to let you turn it on. That is why "AI" as a slide is free and AI as a factory is not. The slide is a copy. The factory is a queue position, a wafer allocation, and a contract that survives contact with the grid. When copies are free, the unprintable thing is the megawatt that arrives, the wafer that starts, and the permission to use both.

• 
  Eduardo (@martiano) reported 19 minutes ago

  @BLUECOW009 Can you open a GitHub issue please?

• 
  swayam (@swymbnsl) reported 21 minutes ago

  I made my first 1,00,000 INR back in 2023, selling a NFT collection on Canto Blockchain. Locked in for over 5 months, was never in Art but learnt pixel art from here and there and made over 140 different assets. Then generated 5k of unique NFTs using a broken python script I found on Github. Had zero programming experience back then, and GPT wasn't that good either. Somehow fixed it after a week of trial and error and going through StackOverflow guides. There used to be a very famous Node.js script by Hashlips but it didn't work on my 32bit potato pc. Was ultimately able to sell my artwork, and by the time I swapped the coin, it was worth 1.13L All this for JEE coaching fee cause we weren't able to afford it back then

• 
  Hridoy Reh (@hridoyreh) reported 21 minutes ago

  📂 Vibe Coding ┃ ┣ 📂 Idea ┃ ┣ 📂 Research ┃ ┣ 📂 SaaS Ideas ┃ ┣ 📂 Problem Selection ┃ ┣ 📂 AI Tools ┃ ┗ 📂 AI Tools ┃ ┣ 📂 AI Coding Tools ┃ ┣ 📂 Cursor ┃ ┣ 📂 Claude Code ┃ ┣ 📂 Codex ┃ ┣ 📂 Lovable ┃ ┗ 📂 Bolt ┃ ┣ 📂 Prompting ┃ ┣ 📂 Project Prompts ┃ ┣ 📂 Feature Prompts ┃ ┣ 📂 UI Prompts ┃ ┣ 📂 Debugging Prompts ┃ ┣ 📂 Refactoring Prompts ┃ ┗ 📂 System Prompts ┃ ┣ 📂 Building ┃ ┣ 📂 Frontend ┃ ┣ 📂 Backend ┃ ┣ 📂 Database ┃ ┣ 📂 APIs ┃ ┣ 📂 Authentication ┃ ┣ 📂 Payments ┃ ┗ 📂 Integrations ┃ ┣ 📂 Tech Stack ┃ ┣ 📂 NextJS ┃ ┣ 📂 React ┃ ┣ 📂 Tailwind CSS ┃ ┣ 📂 Supabase ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 Vercel ┃ ┗ 📂 Stripe ┃ ┣ 📂 UI/UX ┃ ┣ 📂 Landing Pages ┃ ┣ 📂 Dashboards ┃ ┣ 📂 Components ┃ ┣ 📂 Responsive Design ┃ ┗ 📂 Design Systems ┃ ┣ 📂 Development ┃ ┣ 📂 Generate Code ┃ ┣ 📂 Explain Code ┃ ┣ 📂 Debug Code ┃ ┣ 📂 Refactor Code ┃ ┣ 📂 Optimize Code ┃ ┗ 📂 Review Code ┃ ┣ 📂 Testing ┃ ┣ 📂 Unit Tests ┃ ┣ 📂 Integration Tests ┃ ┣ 📂 Bug Fixing ┃ ┗ 📂 QA ┃ ┣ 📂 Deployment ┃ ┣ 📂 GitHub ┃ ┣ 📂 Vercel ┃ ┣ 📂 Domains ┃ ┗ 📂 Production ┃ ┣ 📂 Automation ┃ ┣ 📂 AI Agents ┃ ┣ 📂 Workflows ┃ ┣ 📂 Webhooks ┃ ┣ 📂 Cron Jobs ┃ ┗ 📂 API Automation ┃ ┣ 📂 Marketing ┃ ┣ 📂 SEO Wins ┃ ┣ 📂 𝕏 / Twitter ┃ ┣ 📂 Other Socials ┃ ┗ 📂 Reddit ┃ ┣ 📂 Monetization ┃ ┣ 📂 Subscriptions ┃ ┣ 📂 Freemium ┃ ┣ 📂 Usage Based ┃ ┗ 📂 One-time Payments ┃ ┣ 📂 Growth ┃ ┣ 📂 User Acquisition ┃ ┣ 📂 Referral Loops ┃ ┣ 📂 Growth Experiments ┃ ┗ 📂 Scaling ┃ ┗ 📂 Workflow ┣ 📂 Idea to MVP ┣ 📂 Build Fast ┣ 📂 Ship Fast ┣ 📂 User Feedback ┗ 📂 Iterate

• 
  James McConville (@jamesmcconville) reported 22 minutes ago

  @gsemetfr @github wai... is this why I'm having trouble? everything seems to be fine, I can log in... and then when I try and use it I can't select a model.

• 
  Madeactual (@Madeactual) reported 26 minutes ago

  @stretchcloud The part I would not give up is the audit trail. Coordination overhead is annoying, but the thing that actually burns you is nobody being able to say what changed, when, and on whose authority. GitHub Issues are a lousy planner and a decent ledger, which is why people keep crawling back to them. If a shared planner keeps session replay and side-by-side diffs, it earns the swap. If it only removes the friction and not the record, you traded a slow system for an unexplainable one.

• 
  Craig Hewitt (@TheCraigHewitt) reported 26 minutes ago

  Day 7 of Agentifying my business. Today I created an automation that posts a product update GH issue anytime there is a public Release in any of our products. This is triggered by a Github action from the source repo of our products, and the issue is placed in the repo for our website. For now this will be manually reviewed and our content team can decide if they need to update anything around existing website content, create new content for it, write emails, etc. But in the future (i know you can imagine) this will be one automated sequence. Because our website is already entirely agent-friendly (Astro and just .md files) it'd be easy for a second workflow to scan the site contents, make/update changes as necessary. But first thing's first. Get the data in the hands of the people who need them. Prove the system, and soon we'll automate it.

• 
  weiland (@weiland) reported 28 minutes ago

  After grilling, It sliced the spec into 6 Github issues/tickets. I started with my modified /goal then thought to use /implement for the entire frontend and NestJS backend over a single weekend with 100% test pass rates. (2/6)

• 
  tunct (@tunct101) reported 32 minutes ago

  I’ve claimed my Rialo points and connected all my socials. If you haven’t done it yet, it only takes a few steps: 1. Sign in with Google on the Rialo Playground 2. Open Connect next to your points balance 3. Connect your Discord + GitHub 4. Double-check that you linked the right accounts before claiming Done in a few minutes. How many points did you guys get? 👀 Drop your number below!

• 
  David Villegas (@labsdvx) reported 32 minutes ago

  @waynesutton @bot Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  pasandida(:)aura (@huesofbanter) reported 33 minutes ago

  @akanxshhha its a github pr issue/bug retrieval augment generation project, ie if someone searches for some issue in the chat, it can search all the existing github database for that company quickly and add context from previously occured same issues into the prompt so user can see how it was solved before.

• 
  Yiğit (❖,❖) (@masterygt07) reported 34 minutes ago

  @shynrz007 @BeldexCoin That Github discovery gap is probably the one thing I’d fix first.

• 
  Max Niederhofer ❤️‍🔥 (@maxniederhofer) reported 34 minutes ago

  the reason i love @huggingface's microduck is not just the anthropomorphism, but that it's subsidiary in product form: entire RL stack on Github, just pushed down to whoever wants it <3

• 
  @overtorment (@overtorment) reported 36 minutes ago

  I have just decompiled IPA app binary from Apple Appstore of a fresh new bitcoin wallet. It has obfuscated seed exfiltration to 3rd party server. Literally a few lines difference from the published Github source.

• 
  Devon (@devonphp) reported 39 minutes ago

  @waynesutton @SpaceXAI @bot I want to use it to file properly researched GitHub issues when something gets flagged by sentry!

• 
  ChronoDyne Systems, Inc. (@ChronoDyneSys) reported 39 minutes ago

  @Kavya_learns We don't have that problem. We built a custom MCP server to address it that's free on GitHub (along with our MasterVault Template).

• 
  Peter Kuhar (@pkuhar) reported 40 minutes ago

  @mickcodez great please pull the latest from github. it might fix some already.

• 
  Derek Ross (@derekmross) reported 43 minutes ago

  In Buzz your *** repos, pull requests, and issues live in the same workspace as your chat. Your code and your conversation share one home, with no GitHub in sight. A government just emailed GitHub to delete code it dislikes. Draw your own conclusions.

• 
  Abdelhamed M. (@VZHydra) reported 43 minutes ago

  Never met a single Cursor Origin user. Whoever thought about replacing GitHub / GitLab really had some mental issues.

• 
  Vx (@Vx_nior) reported 46 minutes ago

  Started as Peter Steinberger's November 2025 weekend project, OpenClaw has grown into a non-profit effort with hundreds of thousands of GitHub stars. Version 2.0, crafted by 933 contributors including 569 first-timers, boosts reliability with a reboot-proof daemon, smart heartbeat checks, cron tasks, and multi-agent support, plus a full browser dashboard linking to apps like WhatsApp and Slack. Users cheer fixes for past issues like memory crashes and terminal lockups, though some hit install hiccups and advise backups; daily business users call it essential for automations.

• 
  Feuniks (@Feuniks8) reported 49 minutes ago

  @BendusOLOs @__WonderSun__ @americanmcgee looking at the code on github it seems to be using the unofficial "SDK" from another mod (madnesspatch) and use a custom server instead of the native one from unreal...

• 
  Grant Brewster (@grant_brewster) reported 50 minutes ago

  Has anyone found an incredibly good GitHub / npm package search that’s very legible to coding agents? Especially if there’s some back and forth about tradeoffs: “Hey I found this repo. [insert specifics]. Does what you want but slightly differently. There may be reasons why this implementation is better than the constraints you’ve placed on this problem. [insert why hypothesis]. Want me to use this repo instead?”

• 
  JC Merlo (@itsjcmerlo) reported 51 minutes ago

  @ChefCurryWithD1 Nah those in the GitHub are pretty old I need to update a new thread problem is not lots of engagement from them

• 
  Mert Hurturk (@merthurturk) reported 51 minutes ago

  @fatih @cursor_ai Figured it out. The initial GitHub connection doesn't cover issues. You have to install the plugin separately and authenticate again. It's a bit odd though... The original auth already has issue permissions when you check the app page on GitHub.

• 
  Vigilix (@VigilixAi) reported 54 minutes ago

  A single public GitHub issue granted unauthenticated attackers Editor-level control over Google Cloud projects through the Gemini CLI. Prompt injection bypassed an inactive allowlist, executed code on CI runners, and leveraged plaintext credentials plus overbroad service-account permissions introduced by Google's own setup script. Organizations that followed the recommended configuration inherited the exposure until the recent fixes.

• 
  Jarno (@onefinalprompt) reported 56 minutes ago

  @dhh Careful, once it's on the homepage every bug report becomes a philosophical betrayal instead of a GitHub issue.