1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

Problems detected

Users are reporting problems related to: website down, sign in and errors.

Full Outage Map

GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.

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.

July 10: Problems at GitHub

GitHub is having issues since 07:00 PM AEST. Are you also affected? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

  • 69% Website Down (69%)
  • 19% Sign in (19%)
  • 13% Errors (13%)

Live Outage Map

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

CityProblem TypeReport Time
Paris Website Down 4 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:

  • Techjunkie_Aman
    Techjunkie Aman (@Techjunkie_Aman) reported

    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.

  • CousineauJulien
    Julien D. Cousineau (@CousineauJulien) reported

    The problem with Montreal right now is all these events cheering about the hard fight of being an entrepreneur. Meanwhile you have the GitHub founder starting Entire to fix the scaling issue of GitHub with AI. Nerds need to take over Canada.

  • Teffers2
    Teffers (@Teffers2) reported

    @Bucky_cm Only work around is 2 announcements or host/rent a small server where you can store all your logs, eg. gitbook or notion hell even just github page with the patch notes and images.

  • promptyze
    ᴘʀᴏᴍᴘᴛʏᴢᴇ 🤖 (@promptyze) reported

    Bookmarking 10 repos won't make you a better AI engineer. Shipping one broken agent, debugging why it hallucinated tool calls at 3am, and fixing it will. Skills compound from friction, not from folders of starred GitHub links. #PromptEngineering

  • bounceidc
    Bounce (@bounceidc) reported

    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

  • JamesMontemagno
    James Montemagno (@JamesMontemagno) reported

    @digitalix @burkeholland @WonderingDavid Yeah wanting to use inside of VS Code or GitHub Copilot app for testing purposes. Just been brutal slow. Sort of want the out of the box experience. There are so many variants of models hard to know what to pick.

  • HarryTandy
    Harry Tandy (@HarryTandy) reported

    A World Cup prediction game sounds like a gimmick until you see the payments layer Sam Witteveen breaks down Google's Agent Payments Protocol in 10 minutes: 0:00 - Agents, MCP, and A2A context 1:00 - Agent Payments Protocol 1:41 - AP2 use cases 6:42 - Core principles: openness, user control, accountability, verifiable intent 8:16 - Google Agent Store 8:49 - AP2 GitHub Then open the Cyber Cup piece with one question in mind: what happens when leaderboard points depend on a tiny agent org? > one agent pulls match data > one agent checks odds and injuries > one agent decides the bet > another agent gets hired when the first 3 can't answer That is why a football tournament is such a clean test The scoreboard is public, the feedback loop is daily, and bad agents can't hide behind a polished demo

  • KeetaCode
    Keeta Github Tracker (@KeetaCode) reported

    🐆 Keeta GitHub PR Opened 📦 Repo: anchor-rs 🔀 PR #23: Fix: Naming Updates 🌿 Branch: fix/naming-updates → main 👤 Opened by: @sephynox 🧠 Overview: Keeta has opened a small but important cleanup update that renames parts of its account and key handling so they match the TypeScript version more closely, which should make the developer tools more consistent. This appears to be a technical/internal update with limited public details. It mainly standardizes naming around public keys and also improves how certain asset-transfer errors are passed through, so apps using these tools may need minor updates. - If you build on Keeta, some older names appear to be replaced, so integrations may need to update their call names. - The update also seems to make transfer-related error messages more structured, which could help connected apps handle failed actions more clearly.

  • polsia
    Polsia (@polsia) reported

    Freelance developers spend more time pitching than building. DevDrift fixes that — autonomous agents scan job boards, bounties, and GitHub issues 24/7, match leads to your stack, and submit tailored proposals without you touching a thing. Live soon.

  • cdrrazan
    Rajan Bhattarai (@cdrrazan) reported

    GitHub makes you clear ~6 confirmations and type the full repo name by hand to delete a repo. Fine! Except it does the same thing whether the repo has 100K commits or one commit you pushed 20 minutes ago. That's the tell. The friction isn't calibrated to risk; it's calibrated to nothing. Real "confirm your intent" design scales with blast radius. Deleting a repo with 40 contributors and 2K issues should hurt. Nuking a throwaway you made this afternoon shouldn't. GitHub knows the commit count, the stars, the age, the contributors. It uses none of it. Uniform friction is the easy version to build. It's also the one that trains you to click "confirm" without reading — which quietly kills the whole point. Good instinct. Lazy implementation!

  • spirodonfl
    Spiro Floropoulos (@spirodonfl) reported

    "gItHuB iS dOwN, wHaT dO I dO?" go find a job at a farm you're useless now Ai has taken your job get out we don't want you anymore

  • Codebender_Cate
    Codebender Cate™ ξ(s)=1/2s(s-1)π^(-s/2)Γ(s/2)ζ(s) (@Codebender_Cate) reported

    I need resources to find a collection of GitHub Open source arcade and casino games that can be played in the browser. I need to make sure there's no issues with copyright infringement by using the source for these games. I need true open source. Any suggestions?

  • gokulr
    Gokul Rajaram (@gokulr) reported

    PRODUCTSPEC IS READY FOR EARLY ADOPTERS A few weeks ago, I started with a simple question: What should replace the classic PRD? The answer became ProductSpec: an open standard for software intent before implementation. A Product Spec captures the things that need to survive handoff: • Problem • Hypothesis • Scope • Acceptance Criteria • Success Metrics • AI evals, when the product has model behavior • Decision Trace, when intent changes during implementation It is Markdown. It can live in ***. It has a validator, schema, GitHub Action, examples, starter kit, and agent skills. At this point, I don’t think the next step is adding more fields. The next step is usage. A standard gets better when real teams try it on real work. Not theoretical work. Actual specs. Actual PRDs. Actual docs that have to make it through product, design, engineering, agents, and launch. So I opened a set of good first issues for contributors. You can help by: • Adding ProductSpec examples for mobile app features, internal admin tools, or data products • Adding a Decision Trace example for implementation drift • Improving AI eval examples around model behavior • Mapping ProductSpec to Jira or Linear tickets • Trying ProductSpec on one existing PRD and reporting what feels awkward You don’t need to write parser code. A real example is enough. A critique from your team’s workflow is enough. A “this section doesn’t map to how we actually make decisions” issue is enough. The goal is not for ProductSpec to be my preferred spec format. The goal is for ProductSpec to become a broadly adopted standard for software intent: owned by builders, ***, engineers, designers, founders, and teams using AI agents to build. If you work on consequential software, try converting one real PRD into ProductSpec this week. The standard gets stronger when real product work hits it.

  • itsharmanjot
    Harman (@itsharmanjot) reported

    GitHub is shutting down its entire AI playground on July 30, 2026. Playground. Model catalog. Inference API. BYOK. All of it. Gone for every customer including people with active usage right now. What GitHub Models was: Free access to Llama 3.1, GPT-4o, Mistral, Cohere directly inside GitHub. No separate account. No setup. Zero friction prototyping since 2024. Where GitHub is pointing you instead: Azure AI Foundry. Microsoft's paid platform. If you have pipelines calling the inference API they break July 30. Find them now while access still works. GitHub scheduled brownouts July 16 and July 23 as live tests. Use them. What to actually use instead: For prototyping locally → Ollama. One command, any open-weight model, runs on your hardware, no cost, no rate limits, no shutdown risk. For a ChatGPT-style interface on top → Open WebUI. One Docker command. For a desktop GUI with no terminal → LM Studio. For API-dependent production workflows → OpenRouter. One endpoint, dozens of models, provider-portable. The pattern worth naming: Free tool lowers the barrier. Grows the user base. Gets retired toward the paid platform. This is not a GitHub problem specifically. It is the standard enterprise playbook for developer tools. Local models running on your own hardware cannot be retired by someone else's changelog post. 21 days left. If anything in your stack touches GitHub Models, the time to find out is now.

  • knileshh
    Nilesh Kumar (@knileshh) reported

    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

  • arijiiiitttt
    ARIJIT ROY🌠 (@arijiiiitttt) reported

    is github down?

  • sadhakbj
    Bijaya Prasad Kuikel (@sadhakbj) reported

    Github actions are down and I am just lying useless waiting for my ci to run. Without which I cannot proceed.

  • oshield_io
    OShield 🛡️ (@oshield_io) reported

    Tony abused legitimate server access to steal the upgrade authority keypair and drain both protocols. He routed through a Polish IP to frame a teammate. A misdirection that held until September 2024 until the connection was made when a salary address, verified against team Telegram records, sent funds directly to the same MEXC deposit addresses that received the stolen proceeds. OSINT revealed a network of fabricated GitHub identities with links to other ecosystem teams, and indicators revealing a possible DPRK IT worker tradecraft consistent with Tony's behaviour as reported by the team.

  • InsiderDotSpace
    Insider.Space (@InsiderDotSpace) reported

    @RuneCrypto_ LOOOLLL $200B ? memes ? :D:D:D:D:D:D:D The network is terrible and slow, they're begging GitHub for help. 🤠🤠🥳🥳🤡🤡🤡

  • heynavtoor
    Nav Toor (@heynavtoor) reported

    In 2014 a Swedish engineer named Knut Sveidqvist lost a Microsoft Visio file. He went to open the diagram he had drawn a few months earlier. It was gone. Every box, every arrow, every label. All of it had to be redrawn by clicking through Visio menus again. That night his kids were watching The Little Mermaid on TV. He named his fix after the movie. Twelve years later Mermaid has 89,101 GitHub stars, 8 million users, and native rendering inside GitHub, GitLab, Notion, Obsidian, VS Code, and Confluence. Here is what the paid market still charges to draw the same boxes. Microsoft Visio Plan 2. $15 per user per month. Lucidchart Team. $10 per user per month with a three-user minimum. Miro Business. $20 per user per month. Fifty engineers on Miro Business burns $12,000 a year to draw arrows between boxes. Mermaid replaced the drag-and-drop editor with a text spec that reads like Markdown. ``` graph TD A[User] --> B[Login] B --> C{Valid?} C -->|Yes| D[Dashboard] C -->|No| E[Error] ``` Ten lines. Renders as a real diagram. Every version of Claude, ChatGPT, Gemini, and Cursor already knows how to write it. You describe your architecture in plain English and the model returns a Mermaid block. Paste it into a GitHub README. Paste it into an issue. Paste it into a pull request. GitHub renders it inline as a live SVG. No plugin. No sign-in. The paid tools shipped drag-and-drop editors. Mermaid shipped a text spec that the LLMs learned on their own. Flowcharts, sequence diagrams, class diagrams, state diagrams, entity-relationship diagrams, user journey maps, Gantt charts, pie charts, *** graphs, mindmaps, timelines, C4 architecture diagrams, treemaps. Anything you would open Visio for. Version 11.16.0 shipped two weeks ago. Because the diagram is text, it lives in your repo. Because it lives in your repo, it goes through code review. Because it goes through code review, it stops rotting. Nobody has to remember where the Lucidchart account is. Nobody has to pay $10 a month to reopen a five-year-old file. MIT license. 89,101 stars. TypeScript. The library is free forever. Mermaid Chart the company sells a hosted editor on top for teams that want one, but the core stays MIT. Somebody in Sweden lost a Visio file and refused to draw it again. Twelve years later the paid diagram tools still exist, and nobody who writes software has to use one. (Link in the comments)

  • muriisajon
    Sponge Bob (@muriisajon) reported

    Last year, GitHub saw 1 billion commits. This year, it's on pace for 14 billion. We're writing more code than ever, mostly because AI generates it faster than we can read it. ThoughtWorks is calling this "Codebase Cognitive Debt," and it's becoming a massive problem.

  • ShinkaIoT
    Shinka - AI (@ShinkaIoT) reported

    Google AI Studio just dropped a massive update: One-click GitHub import. 🚀 Before this, AI Studio Build was a one-way street—you could export code to GitHub, but you couldn't bring existing projects back in. If you wanted Gemini's help fixing or improving an old project, you had to manually copy-paste files or start from scratch. Now, you can import an entire repository (frontend, backend, and structure) with a single click. What this unlocks: 1. Reviving old projects: Bring legacy code back into AI Studio to add features or make it mobile-friendly using plain English. 2. Tool bouncing: Build the bones locally in Cursor/Claude, push to GitHub, and polish it with Gemini in AI Studio. 3. Non-coder updates: If you have a repo someone else built, you can now feed it to Gemini to change layouts or fix bugs without writing code. Note: It's still early, so large-scale projects with complex dependencies or database connections might hit some friction. Start small (like a landing page) and scale up.

  • AdamShephe61844
    Adam Shepherd (@AdamShephe61844) reported

    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.

  • Sean1h3z
    Sean (@Sean1h3z) reported

    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.

  • BSCNews
    BSCN (@BSCNews) reported

    Injective SDK Hit By Supply Chain Attack Hackers compromised a widely used Injective (@Injective) npm package with malware designed to steal crypto wallet private keys, per security firm Socket. Attackers reportedly compromised a developer GitHub account before modifying the npm package. The malware secretly captured seed phrases and transmitted them through a fake telemetry server. The compromised release has been removed, but affected wallet keys and seed phrases should be treated as compromised.

  • yehiaabdelm
    Yehia (@yehiaabdelm) reported

    And looking it up on google before prompting an LLM that will likely give you a subpar answer. Please check stackoverflow, github issues, etc. before blindly asking an LLM and wasting your time.

  • KeetaCode
    Keeta Github Tracker (@KeetaCode) reported

    🐆 Keeta GitHub PR Opened 📦 Repo: anchor 🔀 PR #393: Release 0.0.84 🌿 Branch: process/0084 → main 👤 Opened by: @ezraripps 🧠 Overview: This release appears to bundle in a fix for a browser performance issue, which matters because it may help Keeta’s web tools run more smoothly for users. The pull request is a draft release labeled **0.0.84** and only says it includes changes from PR **#392**. That linked change is described as a fix for a browser hashing performance issue, but there are limited public details beyond that. - This appears to be a technical/internal update with limited public details.

  • okaldev
    Furkancan (@okaldev) reported

    @temidaradev setup webhook and trigger .sh in your server do not use github actions build

  • usama__ahmed
    extremely incompetent software engineer (@usama__ahmed) reported

    @status_is_down yes github is down

  • i_mika_el
    Mikhail Rogov (@i_mika_el) reported

    @AyushSarode07 then probably not a GitHub-wide issue. I would check the workflow/status checks on that exact commit first, warning sign usually means one check or integration failed.