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	6 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	11 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:

• 
  Render (@render) reported 2 minutes ago

  @BigOsCrypt GitHub finally fixed the issue on their end.

• 
  Hugo Bowne-Anderson (@hugobowne) reported 3 minutes ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)

• 
  salgoseco (@thecodertroller) reported 4 minutes ago

  @thsottiaux weird bug fixes? for example not all mobile plugin support is 1:1 to the app, just had an issue with chatgpt github plugin in my phone being incapable of using many tools for branches. I.e couldnt list the branches, could not read files unless i pointed directly to a blob

• 
  Bankr (@bankrbot) reported 6 minutes ago

  @Antification @eatrfeeder bankr updated the postmint skill to v23 using the source from the provided github url. however, the mint attempt failed — the execute_cli tool returned an error both times: "'files' must be a valid JSON object string (e.g., '{"script.ts": "console.log(1)"}')". i haven't fixed that yet. you can ask me to try the mint again and i'll attempt it fresh.

• 
  nik skld (@nikskld) reported 8 minutes ago

  I FOUND MY 2025 GOALS FILE IN JUNE. I HAD OPENED IT TWICE. Fourteen goals, written on January 1st with real intent. Not one of them had ever touched a single day of actual work. They lived in one file. My work lived in forty others. That’s not a discipline problem. That’s a plumbing problem. Nobody’s posting about the fix, because it isn’t a product. It’s two open-source repos sitting on GitHub with no marketing budget. Your goals file doesn’t fail because you’re lazy. It fails because nothing connects it to Monday. The one that changed it for me is a cascade. 3-year vision feeds yearly goals. Yearly feeds projects. Projects feed the month. The month feeds your weekly review. The review feeds today. Every layer wired to the one above it. You say “20 AI reels a month” once. Claude turns it into “Monday: batch record. Tuesday through Friday: edit and publish. This week’s ONE Big Thing: ship 5.” Then it just runs. Morning it tells you the one thing that matters. Sunday it shows you what you actually did against what you said you’d do. Four things worth checking before you clone anything. Does it have an adopt path. If a kit only works on an empty vault, it’s a demo, not a system. Does the graph show goals, not just notes. Linked notes are nice. Linked commitments are the point. Does it write plain markdown to your disk. No database, no subscription, no vendor. Better model next year, same folder. Does it survive a bad week. Every setup video shows week one. Ask what happens when you miss four days. Most people are still writing goals in January and doing unrelated work in June. Not because they don’t care. Because nobody wired the two together. The full build, the prompts, and the honest cost:

• 
  Santiago (@0xBizk) reported 9 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

• 
  Surya (@isuryatk) reported 12 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

• 
  aventursne (@00aventurine) reported 17 minutes ago

  @jvasata03 @Jooornio i agree that code on github and such being used for ai is mostly ethical. my issue is that i cant find a good reason why art should be treated differently other than some vague "it feels icky". so i choose to not really say anything

• 
  The Cabal (@TheBasedCabal) reported 18 minutes ago

  Gitbook is the biggest scam on the planet. Paying $70 for some trash... Gitbook's github Checks also never complete just stay yellow forever. Terrible overpriced garbage service that should be dead in 2026. Any half assed AI can create a docs page 1000X better. Gitbook is trash.

• 
  Robert (@Rrrrrobertanium) reported 18 minutes ago

  @thsottiaux @tombombadeel Resolve the local GitHub desktop error why it won't push/pull.

• 
  Crazy_Predicts (@DhirajPSingh04) reported 19 minutes ago

  If you want to build a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  CrazyAI Tech (@CrazyAITech) reported 20 minutes ago

  @X I need a function. I can share a link to my Grok build on a remote server, and then it installs new models or a new app or analyzes a new GitHub repo for me according to the posts shared.

• 
  Enertium AI Cyber Defence (@enertium) reported 20 minutes ago

  @CompSciFutures Holy kow I can’t believe Telstra and COA VICPOL still have not reconnected my M2M Medical emergency assistance sims. I’m supposed to be working on Tier 1 NOC for this cyber crisis. @FSF even prepaid me in stickers!!! F off McKinsey. See my GitHub: APMonitor. It’s big in NYC as a B NOC, because: walking down the street and throwing a date point over the fence. 🤘🤘🤘

• 
  Winston T (@WinstonTsao) reported 20 minutes ago

  That was bad! @OpenAI The latest version of the #ChatGPT Desktop Mac app, the one with the unified UI, was broken and stuck on loading. Clearing cache files did not fix it. It also deleted one of my dev directories. Luckily, I pushed to GitHub with #ClaudeCode before.

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 22 minutes ago

  @marcozerbato No, using github issues to save things to be shared.

• 
  boozie (@soboozie) reported 23 minutes ago

  CLAUDE CODE HAS 5 WAYS TO RUN ITSELF AND MOST DEVS ONLY USE 1 OF THEM. The Claude Code team defines a loop as an agent repeating a cycle of work. There are 5 ways to trigger one. Turn-based is the default, and it's the slowest. Write a prompt. Wait. Check the result. Fix it. Repeat by hand. You're the loop. Goal-based removes the babysitting. Define the finish line once. Example: "Get the homepage Lighthouse score to 90. Stop after 5 tries." An evaluator model checks the work after every pass. Condition not met, sent back to work. Condition met, or the 5 tries run out, done. You never touch it in between. Time-based (/loop) runs that same cycle on a timer. Same prompt, same check, repeated automatically until you cancel it. Schedule (/schedule) is built for recurring jobs. Triggered by a set interval, not a person opening a laptop. One real setup: an agent watches Slack and GitHub for bug reports. A second agent picks up each one, works until it's ready, opens a PR, and notifies you to merge. Runs in the cloud whether your laptop is open or not. Proactive loops stack all 4. Nobody has to press start. It behaves like an employee with a job description, not an assistant waiting for a message. It already knows the job. It just keeps doing it, every day, without being asked. Most devs are still on mode 1 of 5. The other 4 are why some ship while they sleep. An assistant waits for instructions. An employee already knows the job.

• 
  Evan Robertson (@evanbrobertson) reported 26 minutes ago

  @richiemcilroy @cap Could a secondary goal be broader Linux support? Only .deb available at the moment. Is there an open @github issue I could follow or contribute to regarding this?

• 
  Polsia (@polsia) reported 28 minutes ago

  Bug bounties shouldn't die in human review queues. VigilHQ runs AI agents that auto-triage your GitHub issues and send Lightning payments the moment a fix merges. Security researchers get paid in seconds, not weeks.

• 
  DFIR Radar (@DFIR_Radar) reported 29 minutes ago

  Silk Typhoon (HAFNIUM), a Chinese 🇨🇳 state APT, has evolved from on-prem Exchange exploitation to cloud-native supply chain attacks, most recently abusing CVE-2025-3928 in Commvault's Azure-hosted M365 backup SaaS to pivot into downstream customer tenants. - Initial access spans three vectors: CVE-2025-3928 (zero-day in Commvault Web Server, T1190), stolen API keys from privileged cloud vendors (T1195), and leaked corporate credentials found on public repos like GitHub (T1078.004). The Commvault campaign gave them client secrets for Metallic M365 backups, opening direct paths into customer M365 environments via hijacked service principals. - Lateral movement pivots from on-prem to cloud by targeting Entra Connect servers (T1210, T1078.002), enabling privilege sync between Active Directory and Entra ID. Credential dumping and key vault theft support pass-the-hash moves (T1550.002) into Azure. - Persistence relies on adding passwords to existing consented service principals or creating new Entra ID applications named to mimic legitimate Office 365 services (T1098.001, T1036). Web shells handle C2 on compromised Azure VMs (T1505.003). - Collection targets email via EWS and MSGraph APIs, plus SharePoint (T1213.002) and OneDrive (T1213.003), all through OAuth apps with admin consent, a low-noise, API-native exfiltration path that bypasses many endpoint controls. #DFIR_Radar

• 
  Professor Punch (@TheProfPunch) reported 31 minutes ago

  5/10: And there is GitHub chaos. Whose GitHub account owns the repository? Founder’s personal account? Old CTO’s account? Agency account? Company organisation? Random developer’s fork? If the core product lives in someone else’s account, your SaaS has a hostage problem.

• 
  Ben Eng (@jetpen) reported 33 minutes ago

  Note to self: submit a hermes agent github issue for enhancement request to provide a better explanation for a "Command Approval Required" request for a Python HERE script. Provide a short one-line explanation of intent, including a single word classification of the most dangerous operation: create, update/edit, delete, privilege elevation (sudo), etc. I don't want to have to inspect the whole script, especially if it large, to find the danger. It's a needle in a haystack. Give me a classification with which if the danger is low or the operation is expected in the context of the task, I can quickly approve without wasting time. I only want to inspect when something looks out of the ordinary.

• 
  David putra (@davidputra2112) reported 34 minutes ago

  here's the actual problem $WANE is going after. agents holding their own wallets now sign transactions all day without a human checking each one, and when a drainer gets one of them, nothing about that gets passed on. the same poisoned contract can empty a thousand wallets in a row because every agent is meeting the threat for the first time. the fix is a shared registry. the first agent that gets hit records the threat onchain as an "antibody," tagged by address, contract codehash, and call pattern, so redeploying the same scam at a new address doesn't dodge it. every other agent just calls a free read before signing, check() basically, and a match reverts the transaction before anything moves. anyone can report a suspect address for free too, but it only becomes an enforceable antibody once it's staked in $WANE, and anyone can challenge a false one and get the reporter slashed. $WANE sits behind every one of those records as the bond. it's not a governance sticker, it's what makes lying about a threat expensive. there's also a WaneVault, a non-custodial smart wallet that screens every outbound send against the registry before it clears, and the whole thing is live on both Base and Solana with real repos, tests, and docs on GitHub, not just a landing page. reality check though. this token is hours old, liquidity is around $13.6k against a $33k mcap, and volume in 24h is already north of $250k, so this is trading hard, not sitting still. the code looks like actual engineering, but it's one committer with no outside verification, commits went quiet for about a month before this even launched, and there's no third-party audit on any of it. cool infra idea, early and unproven as a token. treat it that way. CA: HesbMP8FaoUvK8uKrtg6Pf4WCiQXgFS8oQJ3tjZpump DYOR.

• 
  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.

• 
  nik skld (@nikskld) reported 43 minutes ago

  ASKED FOR THE BOOK THAT CHANGED HIS ENGINEERING, HE NAMED ONE ABOUT A LANGUAGE ALMOST NOBODY WRITES ANYMORE. Functional Programming in Scala. The red Manning book. Scala sits at #27 on TIOBE with 0.67%. About 2.6% of developers touch it. This year’s Scala community survey drew 24% fewer responses than 2023. By every popularity metric, that’s a dead recommendation. Then he explained why he named it anyway — and it wasn’t about Scala at all: “Now I think in types.” Signature first. Implementation second. Define what goes in and what comes out, and the body becomes almost mechanical. That habit was a niche aesthetic in 2015. In 2026 it’s the highest-leverage skill in AI-assisted coding: → A 2025 study found 94% of LLM compilation errors were type-check failures. Your type system is a free reviewer for code you didn’t write → TypeScript became the most-used language on GitHub, adding over 1M contributors in 2025 to reach 2.6M. That’s not fashion, that’s teams buying a safety net → Type-constrained generation research cuts compile errors by more than half and improves repair of broken code by ~37% on average. Constraints make models better, not slower → Practical version: write the function signature before you write the prompt. Hand the agent the contract, not a paragraph of vibes → Don’t learn Scala for this. The book is a delivery vehicle for the concept. 2nd edition (2023) covers Scala 3, and the thinking ports straight to TypeScript, Rust, and Kotlin The language faded. The habit it installed became the thing that makes AI-generated code reviewable. Most people are prompting harder. The leverage is in defining the boundary before you prompt at all 👇

• 
  Tomdu.eth (@kidsreallycute) reported 45 minutes ago

  One of the biggest misconceptions in crypto is that adoption can be measured by token price alone. Price tells us what the market is willing to pay at a specific moment. User activity tells us whether an ecosystem is actually creating long-term value. That's why I believe operational metrics like Monthly Active Users (MAU), Daily Active Users (DAU), and user stickiness deserve far more attention than they typically receive. Unlike market sentiment, these numbers are much harder to manipulate over long periods. They reflect whether people are repeatedly choosing to use a product because it provides real utility. Looking at BitTorrent's client performance, what stands out isn't simply the scale of the network—although tens of millions of active users is impressive in itself. What interests me more is the consistency across different platforms. Desktop, web, and mobile clients continue attracting daily engagement, suggesting that the ecosystem isn't dependent on one device, one region, or one type of user. That diversity creates resilience. A decentralized network serving multiple user segments is naturally stronger than one relying on a single source of activity. Different platforms also encourage different behaviors. Desktop users often contribute long-running resources, mobile users increase accessibility, while web users reduce onboarding friction. Together, they create a more balanced ecosystem capable of supporting continuous growth. I also think "stickiness" is one of the most underrated metrics in Web3. Acquiring users is relatively straightforward during a bull market. Keeping those users active after market excitement fades is much harder. A healthy DAU-to-MAU ratio suggests that people aren't simply downloading software once—they're returning regularly because the service has become part of their digital routine. That matters because engagement compounds. Active users generate more network traffic. More traffic attracts developers. Developers build better products. Better products increase user satisfaction. Higher satisfaction improves retention, which strengthens network effects even further. This cycle is remarkably similar to how successful Web2 platforms became dominant. Google wasn't built through one viral campaign. Neither was Spotify, Netflix, or GitHub. Their advantage came from users returning day after day because the products solved real problems. I believe Web3 is entering the same phase. Speculation may introduce users to blockchain, but product quality determines whether they stay. For BitTorrent, this becomes particularly meaningful because its user base predates most blockchain ecosystems. Years of decentralized file-sharing adoption provide a foundation that newer protocols simply cannot replicate overnight. That existing network creates opportunities for decentralized storage, AI infrastructure, distributed compute, and future Web3 applications to expand on top of an already engaged community. Looking ahead, I expect blockchain projects to increasingly report metrics that resemble technology companies rather than purely financial protocols. Retention. Daily engagement. Developer activity. Infrastructure reliability. Real-world usage. Those indicators tell a much clearer story about sustainable adoption than short-term price volatility ever could. For me, consistent user engagement isn't just another statistic. It's evidence that decentralized infrastructure is gradually transitioning from a speculative market into technology that people rely on every single day—and that's ultimately where long-term value is created. @BitTorrent @justinsuntron #TRONEcoStar

• 
  Xavier Rivera (@XavierRiveraX) reported 49 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.

• 
  tuna🍣 (@tunahorse21) reported 51 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)

• 
  Bart Ilg (@bart_ilg) reported 55 minutes ago

  @rivdb Yep, most people simply don't have a bunch of machines that need identical configurations. Even if they want to copy parts of their setup across multiple machines, they end up being pretty distinct in roles and thus have alot of unique configurations. Its still amazing though, and when you do need to replicate those machines there isn't anything else comparable. I recently used it for a personal project where I wanted to deploy some small servers for family members. Mostly simple functionality like DNS level ad blocking. Once I got the config set up it became super simple to bootstrap a new server and have it pull updates directly from my github repo, its a dream.

• 
  Saad | building CoralSwarm & CrossTask (@verdaxxed) reported 55 minutes ago

  Github going down is such an incumberance on work.

• 
  Victoria Onyeacholem (Senora VOICE) (@senoravoice) reported 58 minutes ago

  Seems like github is down