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	2 days ago
Saint-Paul	Website Down	2 days ago
Saint-Paul	Website Down	3 days ago
Mexico City	Sign in	3 days ago
León de los Aldama	Website Down	3 days ago
Créteil	Website Down	26 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:

• 
  Learn AI (@LearnAI_MJ) reported 1 minute ago

  @ajambrosino Can you make it easy to code in cloud? Just like how Claude Code Connect naturally to GitHub Repo. I know there is the Codex cloud version but it is soooo clunky to use comparing to Claude code and Cursor! Please - fix this. Also, why codex make computer cook so hot 🔥 comparing to Claude? My laptop even need a gaming fan! Please fix this too!!!

• 
  Yoshik (@AskYoshik) reported 2 minutes ago

  15 CI/CD pipeline patterns you should understand before your next build: 1. Artifact Promotion - Build once, push one artifact, promote the same image across dev, staging, and ****. 2. Immutable Build IDs - Tag images with commit SHA or build number, not just 'latest'. 3. Pre-merge Validation - Run tests, lint, security checks, and Terraform plan before code reaches main. 4. Environment Gates - Keep production behind manual approval, SLO checks, or change window rules. 5. Fast Rollback Path - A deploy pipeline without rollback is only half a pipeline. 6. Database Migration Checks - Separate schema changes from app deploys when rollback is risky. 7. Secrets Injection - Pull secrets at runtime from Vault, AWS Secrets Manager, or sealed secrets, not ***. 8. Cache Discipline - Cache dependencies, but include lockfile hash so old packages do not silently survive. 9. Matrix Builds - Test across versions like Node 20/22, Python 3.11/3.12, or multiple OS images. 10. Ephemeral Preview Environments - Spin up short-lived stacks for PRs, then destroy them cleanly. 11. Deployment Health Checks - Wait for readiness probes, 5xx rate, latency, and error logs before calling it done. 12. OIDC for Cloud Auth - Avoid long-lived cloud keys inside CI variables when GitHub/GitLab OIDC works. 13. Policy Checks - Block public S3 buckets, open security groups, and untagged expensive resources before apply. 14. Pipeline Time Budgets - If CI takes 45 minutes, people start bypassing it. 15. Audit Trail - Know who deployed what commit, from which runner, to which environment, at what time.

• 
  Parth Bhosle (@ParthBhosle1) reported 2 minutes ago

  @zeddotdev should i create a issue on github or is it just some cache issue? in that case how do i clear cache

• 
  Praveen Kumar B (@PraveenKum38515) reported 3 minutes ago

  Hi @Netlify, @NetlifySupport Unable to log in via GitHub: "Authentication Error: Your account has been suspended." My GitHub account is active, but all my Netlify-hosted sites now show "Site not found." I've already opened a support ticket. Please investigate. Thank you.

• 
  Abrar (@abrar_gist) reported 6 minutes ago

  @theo it's been noted in github as well so assuming they'll be releasing a fix soon

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 7 minutes ago

  Claude (code) 🥲 Havent touched twitter in forever, but ngl i spent a ton of time deep in AI agents, harness systems, vibecoding and automation. Built a bunch of small open source projects on github for the community, plus some genuinely useful sites, like my own personal MCP for everyone. Whatever @OpenAI pulled off yesterday is honestly wow. i been team anthropic this whole time, but ngl, after sitting with it for a night, i gotta call it. @claudeai is garbage*. straight up, from a market pov they bring nothing thats actually worth paying for compared to everyone else. You might ask me. how come? especially if you go dig through my twitter from months ago for some reason, or you know my youtube videos. Somebodys 100% gonna think im just fishing for a reaction, that im provoking. that im throwing insults for no reason. Lets just face the facts: 1. Over the last few months claude shipped only one strong product. claude design, which does the same thing as agentation but with a ton of bells and whistles and ready made skills. the problem is, for a month or two after release the limits were separate and honestly laughable. it was unusable for real end to end work. 2. Claude opus 4.7 was a flop. they nerfed 4.6, and then for its whole lifecycle the model with the new system instructions acted broken for most people. it ignored instructions. 3. And so we suffered through it, 4.8 came out and its just ok. its just fine. reminder that the competition rolled out a bunch of new cool features in that same window. 4. Anthropic was fighting openclaw, while chatgpt took it over and became the main model in hermes, the best bang for your buck. 5. Anthropic was fighting for design, while chatgpt 5.6 does it better, plus it has a top tier generative model, plus real time voice. and opus 4.8 only gets which site you want on the 10th try (competitors nail it on the first or second). Honestly claude opus 4.6 was basically an AGI type model. alive, wild, super smart, autonomous. next to it chatgpt 5.2, 5.3 and so on looked like a dumb log. And the situation didnt just shift. its not about the models, its about the ecosystem and the business. i dont get why anthropic keeps dropping pretty stats when for a $200 sub i get half of what i get from the competition. 🥲 before this i kept paying for both subs, because what held me was the text, the vibe (which has looked like gpt for a while now, they even lost that) and the website design itself, i love building web interfaces. now im convinced im only gonna work with chatgpt claude fans or its devs, who fumbled every single trend in a row and nerfed their own models. you can make your excuses in the comments its all been clear to me since the second half of april anyway you lost a guy who was paying you since october 2025.

• 
  Fran⭐️⭐️⭐️ (@franfourcade2) reported 12 minutes ago

  @zeddotdev The action shows up in the Keymap Editor, but pressing → does nothing. Is there anything else I should try? If this is a bug, would you prefer that I open a GitHub issue?

• 
  Spencer Baggins (@bigaiguy) reported 14 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Klauss6139 (@Klauss6139) reported 14 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

• 
  cn80 (@cn8011) reported 17 minutes ago

  I made an MCP server but it might be too powerful, I don't think I will share it because it will inevitably be used by everyone to make more AI slop. The GitHub stars clout chasing isn't worth it.

• 
  Kushagra Gour @css_battle (@CSSMonk) reported 20 minutes ago

  after these 10-min days quick commerce apps, amazon prime feels slow! imagine the situation where coding with AI becomes unavailable and you have to code by hand again! Even if some of us will be able to do it, we wont want to do. Just like quick commerce took away our patience coding by hand will become equally unbearable! Will AI downtimes become the next "github is down" situations?

• 
  Aman (@kukki09) reported 21 minutes ago

  @heyharishbhatt GitHub link not working 404

• 
  the_architectopteryx (@rchitectopteryx) reported 22 minutes ago

  I collect no data, nothing goes to me (all the source is on GitHub, you can see it there). This just embeds their website into a desktop app, nothing else. If OpenAI has any issues, I'll be glad to take it down! 3/3

• 
  Polsia (@polsia) reported 22 minutes ago

  Dev communities have endless conversations. The podcasts are sparse because production is manual and slow. DevPulse AI changes that—AI agents monitor forums, GitHub, and social channels, then automatically research, script, produce, and publish episodes to Apple Podcasts and

• 
  Akshay Nandwana (@akshay81844) reported 23 minutes ago

  2/10 Unlike traditional benchmarks, this one uses 105 real GitHub fixes from production Kotlin repositories. Models receive an issue description and repository state, then must generate a patch that passes hidden regression tests That's much closer to real software engineering.

• 
  MarMar Labs (@MarMarLabs) reported 24 minutes ago

  Better agent tools can make the agent worse. GitHub just documented it in Copilot code review. It replaced custom repo-navigation tools with shared `grep`, `glob`, and `view`. Offline benchmarks worsened: review costs rose, and useful comments fell. The fix wasn't a new model. It was a job-shaped tool contract: 1. Anchor on the diff. 2. Turn the change into a specific review question. 3. Narrow candidates with search. 4. Read the smallest useful code range. 5. Stop when the evidence answers the question. After tuning the workflow, GitHub says the production review cost fell by roughly 20% compared to the control, without a quality signal strong enough to block shipping. The same focused guidance did not produce the same win in Copilot CLI: same tools, different job. Builder takeaway: tool access is not agent design. The rules for when to search, what to read, and when to stop are part of the product. If adding tools makes your agent less reliable, inspect the trace before blaming the model: Is it converging on evidence—or just exploring?

• 
  Mikhail Rogov (@i_mika_el) reported 26 minutes ago

  @abhimeeofficial real GitHub issues plus code quality checks should expose agents that only learn to game test suites.

• 
  Daniel Steigerwald (@steida) reported 27 minutes ago

  I prefer ChatGPT 5.6 Sol over Fable, but in one review of three complex files, Sol Extra High found nothing while Fable High found five small improvements. The catch: I pasted only those files into Fable web. In VSCode GitHub Copilot, with full repo context, Fable found just one docs issue. My takeaway: for maximum review quality, first use full repo context in VSCode, then review the key files again in isolation.

• 
  Eric Lautanen (@Eric_Lautanen) reported 28 minutes ago

  @AIandDesign I got a NVIDIA NIM(GLM 5.2) agent working on fixing some clippy errors and formatting on the VeloCut. I'll hit ya up when it clears github actions. It's a bit slow because of the rate limiting.

• 
  Fluso (@Flusoai) reported 30 minutes ago

  Fluso 1.3.0 shipped yesterday! You can now ask ChatGPT (or Claude, or Codex) to package up your work with it and hand the whole thing to Fluso. How we do it: Fluso gives you an export prompt inside the import dialog. Paste it into your agent. That agent builds a fluso-import[.zip] with your projects, decisions, and files. Drop the zip into Fluso. It becomes real projects on your side, with your work intact. Leaving a tool has always meant losing everything you built inside it. Six months of prompts, corrections, and half-finished drafts trapped inside a chat interface is what keeps you there. Also in 1.3.0: · Every project has working memory. Come back after two weeks and Fluso remembers where you left off, house rules and all. · Steer a running reply, or queue up work that survives your laptop closing. The queue lives on the server. · Confidential Mode shows its work. Tap the Encrypted badge for a real-time cryptographic re-check of the CPU, GPU, and model. · Connected-app tasks (GitHub, Linear, Slack, and the rest) finish in about half the time. 1.3 is the release we've been waiting to ship since we launched. Start with Imports. If it pulls back a project you'd forgotten about, tell us. We're keeping a list.

• 
  TokuTV (@TvToku) reported 33 minutes ago

  @KR_Geats_IX I only upload to my mega drive. If there are problems viewing it on your end, you can always download it directly from the drive and convert it for your use. There is a 5 gb download limit that can be bypassed, as well as an original file guide on the github page.

• 
  Onur 🍌🦍 (@0xc06) reported 33 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?

• 
  Sebastiano Mandalà (@sebify) reported 42 minutes ago

  @Colonthreee I had the same problem 20 years ago I am sure there are libraries to solve the problems on GitHub nowadays

• 
  Mefrius (@mefrius) reported 43 minutes ago

  Today ***/Github saved me for the first time, because my attempts to make changes to the "game over" code broke the main scene of the game and made a damn recursive error, where I physically can't fix dependencies to open scenes.

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 44 minutes ago

  GitHub has quietly become one of the biggest Android app stores on the internet. The only problem? Nobody built a Play Store for it. Thousands of amazing Android apps live only in GitHub Releases. Installing them means hunting through repositories, checking release pages, downloading APKs manually, then remembering to check for updates. Developer Samyak Kamble got tired of that. So he turned GitHub itself into an app store. RepoStore automatically discovers public GitHub repositories whose latest stable release contains a real installable APK. No manual submissions, no private index, no middlemen. Every app must meet strict rules: • Public repository • Latest stable release • Real APK attached • No draft or prerelease builds The result feels remarkably polished. Material 3 UI, Material You theming, rendered READMEs, screenshots, release notes, install tracking, update detection, developer profiles, and one-tap installs, all fetched directly from GitHub. Optional GitHub sign-in boosts API limits from 60 to 5,000 requests per hour, making browsing much faster. Built entirely in Kotlin with MVVM architecture and released under the MIT License, RepoStore is the bridge between GitHub's open-source ecosystem and the app store experience Android users have always wanted. One developer got tired of digging through GitHub Releases... ...so he built the Play Store GitHub never had.

• 
  Explyt.ai (@Explyt_ai) reported 46 minutes ago

  Level 5: MCP servers (GitHub, trackers, search) are scoped per project. Tokens can be pulled from env vars, not left in a config file. Connect enough of them to blow past the 128-tool limit? Each server auto-wraps into its own sub-agent. Nothing to configure.

• 
  Tips Excel (@gudanglifehack) reported 50 minutes ago

  9. Mermaid Live Editor Documentation becomes easier when diagrams are generated from text. Instead of drawing manually, simply write: User ↓ Login ↓ Dashboard ↓ Database Mermaid converts it into clean diagrams automatically. Great for GitHub documentation and technical documentation.

• 
  richard:svoboda (@RSvoboda432) reported 54 minutes ago

  So if you don’t fix the stupid errors and retarded takes. You’re just going to waste my time. Literally today I saw what little errors can lead to. Wrong projects on github. Bash scripting while the default is zsh on macOS. But always willing and very verbose though repetitive.

• 
  Yves (@YvesDC0) reported 57 minutes ago

  Phone-recorded this while testing Castfy. Gave it a GitHub URL + prompt → watch the AI automatically navigate and fill login details in real time (stopped before submitting for safety). No manual screen recording. No editing. Just URL + prompt = realistic demo flow. This is exactly what Castfy does: turns any web app into a polished product demo video in minutes. Tired of re-recording demos manually? Reply with your biggest pain 👇 #BuildInPublic #SaaS #IndieHackers

• 
  Kushagra Gour @css_battle (@CSSMonk) reported 60 minutes ago

  after these 10-min days quick commerce apps, amazon prime feels slow! imagine the situation where coding with AI becomes unavailable and you have to code by hand again! Even if some of us will be capable, we wouldn't want to do. Just like quick commerce took away our patience, coding by hand will become equally unbearable! Will AI downtimes become the next "github is down" situations?