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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	6 hours ago
Saint-Paul	Website Down	1 day ago
Saint-Paul	Website Down	1 day ago
Mexico City	Sign in	2 days ago
León de los Aldama	Website Down	2 days ago
Créteil	Website Down	25 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:

• 
  Samian (@ApplyWiseAi) reported 3 minutes ago

  @ShalsX github is the cheat code that nobody uses right. clean readme + one solid project > 200 leetcode problems

• 
  Vet TV (@VetTVX) reported 3 minutes ago

  @DannyLimanseta Holy cow ... That looks AMAZING! If you need someone to test it out for you, hit me up on XChat! I'd be down to test it for you, or help out any way I can. I'm not the best, but I have at least 6 projects I'm working on and off on my Github page using Grok!

• 
  cryptolistern (@horbunovdima) reported 4 minutes ago

  i asked Hermes agent to turn a real PR into a reviewer briefing video it pulled the diff, wrote the storyboard, built the visuals, generated the voiceover, rendered the MP4, ran checks, caught the wrong TTS provider, fixed it, and rerendered the PR was from the @NousResearch GitHub repo: NousResearch/hermes-agent#61415 a small but very visible fix: "caption" before: text message + media bubble after: one native captioned media bubble and the video itself was built with @HeyGen's HyperFrames - small PR - clear reviewer brief - real artifact this is where agents start feeling less like scripts and more like operators you can actually hand work to

• 
  Tired Thracian (@TiredThracian) reported 4 minutes ago

  @GoogleAIStudio @github Why not from any *** server?

• 
  Sean (@Sean1h3z) reported 5 minutes ago

  Had a small financial planning firm reach out to me for help on tech. They were already using Claude, thanks to a 21-year old intern at the office. They got offers from overseas shops asking for ~$5k/month retainers to rebuild a website and optimize it for marketing. I told them don’t do that. The intern generated one file of html with Claude, looks really nice, way better than their current website. They couldn’t figure out how to get it deployed. I told them get a GitHub and Vercel account and let’s connect in a week. Sat down with them for thirty minutes yesterday, got *** installed on their machine, showed them how GitHub works. Got Claude desktop app downloaded and had them making quick changes and deploying things within an hour. Saved them $5k/month and now they understand how to make changes to their website.

• 
  OpenlabX (@openlabxorg) reported 6 minutes ago

  OpenAI says one of AI's top benchmark is broken : - OpenAI found that SWE-bench Verified increasingly fails to measure frontier coding models accurately, with many remaining tasks containing flawed tests or ambiguous problem descriptions. - The benchmark was originally built around 500 human-validated real world GitHub issues, but frontier coding agents have improved so rapidly that OpenAI says it no longer reliably separates the best models. - OpenAI is now recommending SWE-bench Pro, a harder benchmark with 1,865 long horizon software engineering tasks designed to be more resistant to contamination.

• 
  Gokul Rajaram (@gokulr) reported 8 minutes ago

  FREE GITHUB-NATIVE PRODUCT SPEC EDITOR tl;dr ProductSpec dot IO is a free, privacy-friendly, GitHub-native editor for Product Specs. A few weeks ago, I started pulling on a thread: PRDs were built for a different era of software. They were mostly read by humans. They were often written once, debated in meetings, and then slowly drifted away from what actually shipped. AI agents change the job of the spec. A product spec now has to do 2 things at once: • Be readable by humans • Be executable by AI agents That realization led to the open source ProductSpec standard. (linked below) And it led to the next obvious need: *** and builders need an editor that makes Product Specs easy to create. So today I’m sharing ProductSpec dot io. It’s a free, privacy-friendly, GitHub-native editor for Product Specs. You can draft a Product Spec in a clean editor, validate it against the open ProductSpec standard, and publish clean Markdown to GitHub when it’s ready for review. A few principles shaped it: 1. Product intent should live close to code 2. Specs shouldn’t disappear into a doc tool that engineers never open. ProductSpec dot io publishes Markdown into GitHub, where implementation already happens. 3. Drafts should stay private by default. We do not save drafts on our servers. Drafts stay in your browser until you choose to publish to GitHub. 4. *** should not need to write raw Markdown. Markdown is the durable artifact. The editor is there because humans deserve a better writing surface. The Product Spec has sections for: • Problem • Hypothesis • Scope • Acceptance Criteria • AI Evals • Success Metrics • Optional sections like User Experience, Customer Truth, Risks, Rollout, and Open Questions The goal is simple: move from classic PRDs to Product Specs that humans can trust and agents can execute. If you’re a PM, founder, designer, engineer, or builder: take one existing PRD or new prodcut idea and convert it into a Product Spec this week. If you care about this becoming a broadly adopted standard, star the repo and contribute examples, schema feedback, parser improvements, or section vocabulary. PRDs had a good run. The enduring format will be ProductSpec: open, structured, human-readable, and agent executable.

• 
  Ashay Kushwaha (@sentinelcipher) reported 14 minutes ago

  @sneha___03 github streak. Real engineering work over consistent problem solving. It depends tho

• 
  MMLTECH (@mmltechYT) reported 15 minutes ago

  @WoClaudecraft I used to use Copilot in GitHub Desktop to generate commit summary, but I'm running out of tokens :)) The good news is that the website wasn't totally broken, though.

• 
  Nilesh Kumar (@knileshh) reported 16 minutes ago

  Everyone keeps calling MCP the "USB-C for AI." That's actually a pretty good analogy. Before USB-C, every device needed a different cable. One for your phone. Another for your camera. Another for your laptop. AI tools used to have the same problem. Every app had its own custom integration. Want your AI to use Gmail? Build a Gmail integration. Want it to use GitHub? Build another one. Slack? Another. Notion? Another. MCP changes that. Instead of every AI model learning a different way to talk to every app, apps expose a standard interface. The AI learns one protocol. Then it can work with thousands of compatible tools. Think of it like this: 🔌 USB-C standardized hardware connections. 🤖 MCP standardizes AI connections. That's why so many companies are adopting it. Not because it makes models smarter... Because it makes connecting models to the real world dramatically simpler. Once you understand MCP, you'll realize it's less about AI... and more about making integrations finally speak the same language. #ai #llm #mcp

• 
  Polsia (@polsia) reported 22 minutes ago

  Third-party API breaks → hours reproducing the error, collecting context, filing a ticket. PingProbe automates that. Monitors uptime, latency, schema drift, files bugs in Jira/Linear/GitHub with full error context. You arrive at work and the work is already done.

• 
  Oskar Wickström (@owickstrom) reported 23 minutes ago

  So, now GitHub Pages deploy is broken and I can't release my thing as planned. It really is time to move...

• 
  Shadow Nick (@doublenickk) reported 25 minutes ago

  87% OF THE PLANET SUCKS AT AI BECAUSE THEY ARE STILL TYPING MANUAL PROMPTS LIKE AMATEURS While the masses use ChatGPT as a glorified search engine, elite builders are deploying autonomous digital armies that execute high-stakes business operations 24/7. Meet Synapse, an open-source MCP engine that hands AI complete vision and surgical command over your desktop to run background tasks silently while you sleep. The exact strategy used to break the system: The FBI Negotiation Hack: Scrape a massive list of multi-million dollar startups, feed real FBI hostage negotiation transcripts into the AI, and let the agent autonomously blast out high-leverage B2B outreach that forces prospects to say yes. Zero-Drift Execution: Ditch chaotic markdown files and manage your agent's state through GitHub Issues to keep them locked in for weeks without a single hallucination. Full-State Reality Testing: Stop relying on worthless pre-compile unit tests because this agent forces your system to compile, screenshots the actual interface, and verifies performance against reality itself. You can keep playing around with basic chatbots, or you can deploy a ruthless autonomous agent to scale your code and outreach on autopilot.

• 
  Adam Shepherd (@AdamShephe61844) reported 26 minutes ago

  The GitHub agent that leaked private repos wasn't a model jailbreak. It read a poisoned issue and did what the text said. Read scope plus any outbound channel equals an exfiltration path. Least privilege stops being optional the moment your agent can be talked to.

• 
  Nathan Colosimo (@thenathancolo) reported 26 minutes ago

  If the bun rust rewrite has shown anything, it’s that we need a better unit of measurement on GitHub. Commits can no longer be used as any measurement of output or work, and if commits / contributions were low signal before AI, they are ~0 now Same with the issue and pr slop Opening up 50 issues or PRs on shadcn doesn’t mean anything and shouldn’t Tbh here commits are actually a good measurement bc rewriting bun is actually an insane amount of work, but we need better ways of deterministically figuring out who is good at what they do + does a lot of it.

• 
  CA Nikunj (@NikunjSOF) reported 29 minutes ago

  We will get you sorted. DM us! Setting up a large GCG in India beyond 10000 employees. Based on standard market benchmarks for a mid-to-large mature GCC in India, India GCC IT Spend Benchmark **Hardware** — *The 15% allocation (US$1,050/FTE) matches industry standard. For missing categories, **Networking & Wi-Fi Hardware** and **Smart Meeting Room/Collaboration Tech** are notably absent and usually consume about 10% of this bucket.* * Laptops / Desktops — **US$735**/FTE *(Assuming a 3-year refresh cycle on mid-to-high-end enterprise laptops)* * Servers & Storage — **US$105**/FTE *(Lower end, as most compute has moved to cloud edge)* * Peripherals — **US$126**/FTE *(Monitors, docking stations, dual screens, keyboards)* * Surveillance & Physical Security — **US$84**/FTE *(CCTV, server room access controls, firewalls)* **Software** — *The 50% allocation (US$3,500/FTE) is accurate due to the high density of global software licensing pass-throughs. For missing categories, **Developer Tools & IDEs** (like GitHub Copilot, Jira) and **Enterprise AI/ML tooling** are crucial omissions for modern tech GCCs.* * Productivity & Collaboration Tools — **US$875**/FTE *(M365, Google Workspace, Zoom, Slack)* * Security & Compliance Software — **US$1,050**/FTE *(CrowdStrike, Zscaler, DLP, IAM tools)* * Virtualisation & Infrastructure — **US$700**/FTE *(VMware/Nutanix licenses, enterprise OS)* * Cloud Platform Licences — **US$875**/FTE *(Direct user-allocated AWS/Azure compute and SaaS tokens)* **Services** — *The 35% allocation (US$2,450/FTE) is standard for centers utilizing hybrid outsourced managed models. A key missing category is **L&D/Technical Training & Upskilling Services**, which usually takes up 5% of the operational services budget.* * IT Helpdesk & End-User Support — **US$735**/FTE *(L1/L2 local desk support contracts)* * On-site Infrastructure Management — **US$490**/FTE *(Local network, facility uptime, and data center engineers)* * Cybersecurity Managed Services — **US$610**/FTE *(24/7 Managed SOC, threat monitoring, vulnerability scanning)* * Cloud Managed Services — **US$370**/FTE *(FinOps, cloud optimization partners)* * Annual Maintenance Contracts (AMC) — **US$245**/FTE *(Hardware vendor warranties, UPS, and server maintenance)* --- ### Contextual Data * **GCC size** — **500** FTEs *(Optimal mid-scale operational baseline)* * **Sector** — **BFSI & Technology Services**

• 
  Nirmātṛ (@En_formare) reported 32 minutes ago

  LaTeX’s ***** little secret just spilled millions of researchers’ private laundry onto arXiv’s public stage. Open science exposes its Achilles’ heel when sloppy habits meet permanent public archives. The very tool accelerating discovery • arXiv’s 1991 revolution in physics, math, and beyond • now risks reputations, security, and ethics in one sloppy compile. 88% of LaTeX-submitted preprints on arXiv – nearly three million papers, covering 93% of the repository up to late 2025 – harbor hidden information never meant for prying eyes. Passwords, GPS coordinates pinpointing homes, API keys, profane co-author smack talk, to-do lists confessing paper weaknesses, Google Docs links exposing peer reviews and participant surveys: all baked into source files, dangling attachments, and metadata like forgotten cookies in a browser history. LaTeX’s comment-friendly markup is treated by authors as private scratch paper while obsessing over the pristine PDF output. arXiv mandates uploading those source files, but most researchers remain unaware; only 41% of surveyed affected authors knew the repo publishes them. The ultimate mental model mismatch: GitHub devs expect exposure; academics drafting in comments do not. One team’s snarky “WTF does this mean?” about a rival’s work, another’s home address leaking via geotagged images (7,326 submissions flagged, hundreds tying lab to living room), or 699 editable Google Docs spilling rebuttals and raw data. Earlier scans caught social security numbers and cloud links; this deep dive calls it the tip of a 12-million-file iceberg across preprint versions. The fix is simple yet revolutionary: strip comments (% lines), purge metadata from images and PDFs, delete dangling files, and use tools like latexclean or arXiv’s own guidance before upload. Future-proof with scripts or pre-submission audits; don’t let a casual “TODO: fix this embarrassing gap” torpedo your next big claim.

• 
  Ray 👨🏽‍💻 website & app developer (@Raynerdtech) reported 35 minutes ago

  Yesterday I posted: “**** programming. **** Java. **** databases. **** servers. **** networking.” A lot of people thought I was joking 😭 I wasn’t. The code worked. The problem was everything around it. Deployment. Servers. Databases. Infrastructure. The funny part? Most of that headache could have been avoided if I knew about Symplax earlier. Built by my guy @LazyCode3 The easiest way to describe it: Vercel for your own VPS. GitHub deploys. Databases. Metrics. Backups. You keep full control of your infrastructure without the usual VPS pain. Self-hosting shouldn’t be harder than building. Link in the comments. 👇🏾

• 
  Onur 🍌🦍 (@0xc06) reported 37 minutes ago

  An $INJ npm package with 50,000 weekly downloads just got weaponized. Why?! To steal wallet keys, and the attack vector itself is what makes this worth understanding. No smart contract exploit or cryptography broken. Instead, a compromised developer GitHub account pushing malicious commits into a trusted SDK starting June 8. The code hooked directly into wallet key-derivation functions, quietly copying private keys and seed phrases, then exfiltrated them through a fake telemetry endpoint disguised as a legitimate Injective server. What actually multiplies the damage: the compromised version got pinned across 17 other packages in the same npm scope. Devs who never installed the SDK directly still inherited the exposure. 310 downloads before it was caught: the developer whose account got compromised noticed fast, but Socket says the campaign isn't fully contained yet. If trusted developer tools are now the actual attack surface, how do you audit a dependency you've never even directly installed?

• 
  Lagoon Labs (@LagoonLabsMv) reported 37 minutes ago

  Pearson's anti-piracy vendor accidentally took down their own author's GitHub code repo. Paul Deitel's educational examples went dark for weeks after Link-Busters confused them with pirated textbooks. Automated takedowns hitting the wrong target again.

• 
  Bounce (@bounceidc) reported 37 minutes ago

  HE CHARGES $5K FOR SITES THAT LOOK LIKE A NEW YORK STUDIO SHIPPED THEM same model everyone else runs, but his claude picks from a real design library instead of guessing, so every build lands with animations, glass morphism and gradients already dialed in the two installs: grab the ui ux pro max skill off github and tell claude to install it, that one move loads 50 ui styles, 97 color palettes and 57 font pairings pull the magic mcp server from 21st dev and install it the exact same way after that you just say build a website and it comes out looking like a studio shipped it, not a template everyone else is still prompting for the word beautiful and wondering why claude keeps handing back the same flat bootstrap page save the two installs, the skill url and the mcp command are in the guide below

• 
  Klauss6139 (@Klauss6139) reported 38 minutes ago

  Spent this morning actually building on @RialoHQ Latch instead of just tweeting about it, and the moment it clicked was genuinely satisfying. I gave an AI agent access to a GitHub repo through Latch, then asked it to read a file. Clean 200, file came back, no problem. Then I asked the same agent to delete a file, and Latch stopped it dead: authorized: false, reason: Method DELETE not allowed. Same agent, repo, session, one action sailed through and the other got hard-blocked by policy before it ever reached GitHub. The part that actually matters is what the agent was holding the whole time. Not my GitHub key but a scoped Latch token that only permits reads, so even if that token leaked, the worst anyone could do is look. The real credential never left the encrypted layer, and I never once had to trust the agent to behave. Took me under 30 mins start to finish. This is the difference between hoping your agent stays in its lane and actually drawing the lane. @rialo_africa @0x_alextine

• 
  Ashley Schendel (@ashleyschendel) reported 44 minutes ago

  Hey! I wanted to offer a small suggestion. I’m a total nerd about this stuff and I study/test the X algorithm pretty regularly with a few friends. From what I’ve seen, outside links in the main post can really hurt reach. X tends to treat them almost like spam, and some of that was even visible in the algorithm code they released on GitHub. You may get better results by writing the post without the link, using stronger keywords, skipping hashtags, and then putting the article link in the first reply. That way people still see the story right under the post, but the main post has a much better chance of being shown especially if it’s engaging. Also, the more often an account posts outside links directly in posts, the more it can seem to drag down reach on other posts too.

• 
  Yuan John (@yuanjohn01) reported 46 minutes ago

  @zarazhangrui There is currently an issue on GitHub regarding CodeX's design process. Occasionally, it mistakenly inserts the design requirement keywords you provide directly into the frontend design placeholders, which is essentially a bug.Furthermore, CodeX's underlying design capabilities have inherent flaws. Even when using MCP or skills like 'Creative Production', these limitations cannot be fully overcome.

• 
  Polsia (@polsia) reported 52 minutes ago

  Dependabot surfaces the CVE. Renovate opens the PR. Neither writes the fix or runs your tests. Built PatchSentry to close that loop — autonomous patching for GitHub, end-to-end, and humans only get paged when judgment actually matters. Live soon.

• 
  Mo Ayob (@Mossiah) reported 54 minutes ago

  Your company has AMNESIA. Every single day. It’s not one brain, it’s hundreds of people, each holding a tiny piece of what’s ever happened. Why a decision was made. What didn’t work last time. What the client actually asked for in March. Nobody has the full picture. So the same mistakes repeat. The same questions get asked again. And when someone leaves, their piece of the memory disappears with them. Funny thing is , it isn’t a “hire smarter people” problem. It’s actually a massive Organizational Intelligence issue. @OCTAMEM gives your company a memory of its own, one that sits underneath your files, docs, and code and actually remembers what the company knows. GitHub ingestion is landing next. The desktop app ships Wednesday and pulls straight from your machine, OneDrive and Google Drive. Still in beta. The price won’t stay this low.

• 
  Lorenzo (@gabor_rar) reported 54 minutes ago

  Yesterday a merge deleted my preview environment, and *** told me everything was fine. PR #33, preview into main, merged at 08:14. The repo had delete_branch_on_merge turned on, so GitHub removed the long-lived preview branch along with the PR. Vercel had automatic preview deploys bound to that branch. They stopped. Locally, *** still showed origin/preview. A stale tracking ref. Nothing looked broken. No agent did this. No line of code was wrong. A checkbox in repo settings quietly deleted a deployment target. Preview is now protected from deletion and force-push, and the rule lives in the runbook the agents read. Your agents can only respect the invariants you actually wrote down.

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 55 minutes ago

  PC gamers who use DLSS Swapper have been given a security warning. The app’s creator says a user uploaded a fake DLSS file that contained malware. He warned: “DO NOT download these files, they are likely malware.” The problem is not with DLSS Swapper itself, but with files uploaded by other users through its GitHub repositories. The developer recommends only downloading DLSS files from trusted sources like NVIDIA, official game installs, or verified releases

• 
  Philip (@0zkphilip) reported 57 minutes ago

  @Sim89776996 @L0laL33tz "Chinese could theoretically also use Session." they do. You don't need it on the app stores as you can download it from github. The issue with these arrive when countries like Iran block it completely which they did earlier this year but that is super expensive to do.

• 
  TnvMadhav (@TnvMadhav) reported 59 minutes ago

  For some reason in the past two days I haven't really got @OpenAI 's Codex to use the gh cli properly. While it works in the terminal in both Codex and otherwise, it doesn't work in the sandbox environment of Codex. I smell some updates that ChatGPT is trying to use to install the GitHub plugin but I like to do things with battle-tested existing gh CLI, with as few dependencies as possible. Could this be because of a security issue? As in the access token in my local work computer shouldn't be read? So I wanted to debug this a bit more and installed the Codex CLI on my Mac. While the same prompts, which involve the use of gh CLI tools, "work" on the CLI but not on the desktop app. I'm not sure if this was intentional on the desktop app. I asked Codex itself to perform a root cause analysis but it seems to have no clue or because there is no published documentation on this. By this I meant the execution environment change. It is clear that the sandbox does not have access to the network or the Mac OS keychain but I guess if you give it access once, there is some sort of expiry time for it to work.