1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

Problems detected

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

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.

August 23: Problems at GitHub

GitHub is having issues since 12:00 AM 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.

  • 57% Website Down (57%)
  • 30% Errors (30%)
  • 14% Sign in (14%)

Live Outage Map

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

CityProblem TypeReport Time
Inverness Website Down 5 days ago
Quito Sign in 6 days ago
Junín Errors 6 days ago
Guadalajara Errors 6 days ago
Paris Website Down 6 days ago
Quito Errors 6 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:

  • Holy_Terra40k
    TheLastSoul (@Holy_Terra40k) reported

    @thatguybg The app interfaces are terrible. An update is coming via a GitHub commit. They’re coded in Python and TypeScript. It’s not hard to offer a Rust backend and platform-specific frontends in native languages. I recommend they use the AI models they sell.

  • Suhail
    Suhail (@Suhail) reported

    Has saved me a lot of pain recently debugging issues: “Moving forward, when you encounter a bug or issue, search GitHub PRs, issues with another agent in parallel to see if you can find a reference solution.” Which made me think, GitHub is the primary place agents are likely to already be communicating with one another.

  • robertbanh
    robert banh (@robertbanh) reported

    Imagine one day when anthropic/openai is down. All work would cease. We would be forced to go home. That happened when I worked at IBM (20 yrs ago) and the Lotus Notes server was down. No one could get any "work" done so we all left. Now when Slack or Github is down, we say the same thing. It's like, we forgot how to be engineers. Hmm... I guess this is where local models can help. We all spin up unsloth and continue working.

  • bch1601
    Bogdan Chechin (@bch1601) reported

    @kirtandopamine people did build it. GitHub Jobs shut down in 2021. Polywork was exactly this pitch. Triplebyte too. all died for the same reason: devs don't pay for a profile, recruiters do, and recruiters don't live on GitHub. users on one side, customers on the other

  • TheeAndre
    André Imbayago (@TheeAndre) reported

    @zwai_ndimba Unrelated: When github was down, was AzureDevOps working?

  • htormey
    Harry Tormey 🇮🇪 | 🇺🇸| 🇺🇦 (@htormey) reported

    A lot of people are trying to sell enterprise AI products to VCs. Everyone from Notion to Linear, for example, seems to want to be my AI orchestration layer. Meanwhile, a lot of the actual problems we’re hitting using AI at scale are much less glamorous: GitHub falling over under load, test runners becoming bottlenecks, desktop OSes being too slow, and figuring out how to run CI and E2E tests at agent scale. VCs aren’t operators, so I think there’s a growing disconnect between what sounds like an enterprise AI problem and what actually is one.

  • zraonx
    Zura (@zraonx) reported

    @basetrencher @HamzaInstantly google + github oauth + just email is industry standart password signups are ancient and TERRIBLE UX

  • jan53n
    Jansen (@jan53n) reported

    Is github *** server access getting slow for you?

  • jason_yakubu
    Jason A Yakubu (@jason_yakubu) reported

    @vikrambuilds Working on a hackathon project that allows to test your website for common production failures and fixes it automatically as a PR to your GitHub. Also a live monitor that monitors your website for user errors and fix it.

  • Kosumi1989
    Kosumi (@Kosumi1989) reported

    An GitHub issue that I am interested in working on but have not yet: Reducing Cargo /target size with better GC.

  • basicBrogrammer
    Jeremy W (@basicBrogrammer) reported

    What a time to be alive. My vam coated a Android launcher while walking my dog camping just talking to cursor on my phone. The agent "handed" me an apk and we iterated from there. After a few weeks of it being my daily driver and loving finally having the launcher I wish was on the Play store. The app was crashing randomly. I had my agent pick back up. Walk me through. Setting up sentry and had it right. A GitHub action that would publish to the Play store. Then I waited. The crash happened again. I sent the issue to my agents and now the app is running smoothly. It's the age of the geek baby. Go build

  • XGenerationz
    Maحmoud Ismaعil (@XGenerationz) reported

    github down?

  • 0xkyver
    Kyver (@0xkyver) reported

    I found the repo that solved the most annoying problem in AI engineering: connecting your agent to real tools without writing custom glue code for each one. Composio gives your agent access to 1,000+ integrations out of the box. Slack, GitHub, Notion, Salesforce, databases — all through one standardized interface. But here's the real value: it handles authentication and sandboxed execution. Your agent doesn't get raw API keys. It gets a secure, managed gateway. One MCP server. Zero "glue code." 30k stars. Native MCP support. Works with every major model and framework. Stop spending 3 days integrating Slack into your agent. Spend 3 minutes. Bookmark this repo.

  • coder_zi
    Emmanuel (@coder_zi) reported

    a few days ago, my younger brother came to me and started asking how to install node.js on his laptop mann was I happy I asked him what he was trying to do, that's when I learned that this guy had made a deal with one of his friends to build her an e-commerce website for her drop shipping website he had already vibe coded everything with Claude, the frontend, the backend, the admin dashboard, I was quite genuinely impressed he told me he was trying to make the web app function outside the Claude environment, and Claude had given him some .zip files to download, which he was planning on extracting and as per the directions of Claude, also set up in a very unconventional manner so, the software engineer in me launched into a long lecture about how this was the wrong way to go about it, that he needed to have a GitHub for version control, initialize the project properly locally, connect the GitHub to the local project etc he didn't even know the difference between a hosting platform and a version control platform, so we had a long talk, where I explained exactly how I'd build, host it, my CI/CD pipeline etc... after my conversation, I didn't think much of it, then just yesterday, he showed me the live website, complete with a perfectly functioning admin dashboard, it's even got an auth system, damnn it turns out he did follow claude's instructions on how to set it up, but he also took my advice on version control, so he committed his code to GitHub, and deployed on render, when I told him render had a 10 minute life cycle for projects, and inactive projects will be disabled after 10 minutes, he told me he knew about that and he had already asked Claude to write a ping function to consistently ping the server once every 9 minutes in order to keep the server alive and his deployment fully active mannnnnn he's still in high school btw authenticity really is the moat...

  • andrebeaumont
    André Beaumont (@andrebeaumont) reported

    @MemesOfNixOS @dhh NixOS is ngmi and has always been ngmi, the troon **** is just the cherry on top >be me >want reproducible system >install troonix >need to learn a haskell-inspired DSL written by midwits just to change my ******* wallpaper >documentation is 5 years out of date, wiki says deprecated, github issue says "just use flakes bro" >flakes are still "experimental" after 4 years lmao >spend 6 hours rebuilding because I added one font >tfw still can't get nvidia drivers working it's a midwit trap OS. Smart enough to understand why mutable state is bad, too dumb to realize you don't need to turn your entire OS into a pure function to fix it. Nix the package manager is actually useful. NixOS as a daily driver is for ricers who want to post their 2000 line configuration.nix on reddit and do nothing else. Normies will never touch it, ever. Just use Debian or Arch if you want **** to actually work.

  • draparente
    Angelica Parente (@draparente) reported

    Can we please do something about this @bcherny @trq212 @AnthropicAI ? This screenshot is a small subset of the total number of permissions requests I have to control. The github issues for this have been closed/reported as duplicates. This seems like a pretty large security risk, a bad actor could take advantage of people getting used to accepting *extremely opaque* full disk access requests.

  • MattSenter
    Matt Senter (@MattSenter) reported

    I just tried to use the Gemini CLI for the first time. Told it to look at a Github issue and propose a fix. It decided that after it pulled the issue directly it needed to then search the web for the issue. It then got stuck searching the web and could not be ESC-canceled. Could not run "/quit" because "commands cannot be queued." Had to kill the terminal to escape. Awful experience.

  • PaulSchleifer
    Paul Schleifer (@PaulSchleifer) reported

    @histoireclimat @ChrisMartzWX @MatthewWielicki Thanks for the feedback. Yes, I could have coded this myself, but I do have a lot of other things to do with my time these days, unfortunately, which is why I had to wait about 5 days before tackling it at all. Anyway, no hospital appointments today, and mum's in too much pain to leave her chair, so I've had time to (manually) edit the page to make it fully responsive and fix a few other things. I actually prefer the homegrown approach to bringing in third-party charting libraries these days. Something as simple as this doesn't need D3 or chart.js etc, and I've got a bit of an aversion to bloating github pages with dependencies (I'm sure that's irrational, but that's how I feel about it). I've also grown a lot less fond of reactive frameworks, despite years of Angular and React. If I had to tackle anything that needed it, I'd probably pick Svelte now.

  • 0xkeeny
    Keen (@0xkeeny) reported

    @github good default, because the attack window on a poisoned release is almost always the first 48 hours. the interesting part is the fix wasn't smarter scanning. it was just waiting.

  • spiderboyis
    Harshit Mathur (@spiderboyis) reported

    engineers talk endlessly about "technical debt," but nobody talks about the massive pile of "information debt" we accumulate every single week. ​we read deep research papers, bookmark obscure github repos, save architecture threads, and screenshot error fixes. we hoard data under the illusion that saving it equals learning it. ​three months later, when you actually need that exact solution, you spend 45 minutes trying to remember which app, chat, or folder you stashed it in. ​storage has become virtually free, but human context retrieval is more expensive than ever. the future of software isn't about capturing more data it's about zero-friction recall. ​how do you currently keep track of technical insights you know you’ll need months from now?

  • MarkLyck
    Mark Lyck (@MarkLyck) reported

    poteto poteto poteto can you please improve these Cursor PR features? Tried switching to Cursor this month, but there's a lot of missing / annoying stuff. 1. Add a preview link button. If the PR has a preview deployment from Vercel/Cloudflare/Netlify etc. Just give me a button I can click to quickly go to that preview deployment in Cursor or Browser. I don't want to have to go into the PR and go through review comments to find it. 2. Give me a keyboard shortcut to copy the Github PR link. Right now I have to click the chat, wait for it to load, then click "View PR" then click the 3 dots next to the github logo, then click copy link. That's way too many steps to share a Github/Origin link. 3. Why can't I configure trusted domains in the agent mode? Everytime I click a link I get this error "It's outside Cursor's trusted set. Only continue if you trust the source." And yes I did add it to my trusted domains in the IDE mode, but doesn't seem to work in agent mode. 4. Give me an indicator somewhere that shows how many approvals my PR has gotten if it has any. Right now the fastest way is to go to the github link, second fastest way is to go to the review section and scroll down and count manually if the PR doesn't have a lot of discussions. These are easy UX wins that would really help. 🙏🏻

  • rohanpaul_ai
    Rohan Paul (@rohanpaul_ai) reported

    A public GitHub now holds 3.8 million agent skill files. And finds that over half of the agent skill files on public GitHub are exact copies of another file. Only about 1.9 million of the 3.8 million files are actually different. That is what a format with no registry and no package manager looks like. People copy the folder and move on. A skill is a folder with a Markdown file that tells an agent how to handle a task. The agent reads the short description at run time and decides on its own whether to load it. No compiler checks that decision. So the skill in your repo is frozen, and whoever wrote it cannot send you a fix. The paper raises the obvious next question: whether edited copies of popular skills add commands or network calls the original never had. Nobody could check that at this scale before. The whole dataset ships as one SQLite file, so now somebody can. – arxiv. org/abs/2608.10906 Title: "GitSkills: A Dataset of Agent Skills on GitHub"

  • sonnnnnnnnnnnna
    /喜欢ボカロ音乐/能不能尽量少喝咖啡 (@sonnnnnnnnnnnna) reported

    @FhuDra @realNyarime any website need "备案" - submit application to gov, talking with officers' (spend days and weeks), then your website could be legally deployed in china mainland. or, just rent china hong kong server or oversea server that don't need "备案". (and github pages also don't need)

  • alexpotato
    Alex Elliott (@alexpotato) reported

    @forwardsecrecy I’ve seen some people even hook up the LLM to JIRA or GitHub issues and then create an entire project of tasks.

  • QubicLi
    QLI Qubic Services (@QubicLi) reported

    @RidvanSedaZtrk We'll create a GitHub issue for this.

  • FirstDeployAI
    WhiteFlour (@FirstDeployAI) reported

    @liam_fallen I am not a big fan of cursor yet, the way that it attaches so hard to the Github for everything is not a long term thing for me, I plan to get far away from github thanks to Microsoft before they ruin it further. It's down now, at times, I never remembered that happening before.

  • CalvinGrunewald
    Calvin Grunewald (@CalvinGrunewald) reported

    @htormey I think a few things are true: 1. If you’re an existing company with PMF and enterprise accounts/data, it’s only natural to add an orchestration layer on top of that data. This is almost the obvious thing to do. 2. A lot of enterprises are going to be running their own infrastructure (like on prem GitHub EE) and so they don’t feel the pain that a lot of smaller teams/indies might be feeling. 3. Some of the VCs we’ve talked with are actually tired of agent orchestration platforms and wanted to see something a lot more focused. 4. I do think there are some really interesting vertical scenarios to attack for enterprises - we are looking at post sales software integration as one example. But the AI/agent part isn’t what is hard here, it’s the traditional problem of selling. Anyway, I agree, will be interesting to see how this plays out.

  • iamiqrram
    Iqramul Hussain (@iamiqrram) reported

    @cursor_ai @github stop asking "Are we there yet?" 80,000 times a second. The best part? Cursor relies on GitHub under the hood to sync repos, so Cursor’s own launch day workflows were frozen by the outage. They literally couldn't even tweet properly because their internal tools were broken.

  • dabernathy89
    Daniel Abernathy (@dabernathy89) reported

    .@github CLI can't be used to upload images to PRs. this was marked as "won't fix" years ago and they just never bothered to revisit it when agentic development took off? bizarre.

  • hochulambo
    hochulambo (@hochulambo) reported

    An agent opens hundreds of GitHub issues a night asking researchers to move their weights onto Hugging Face. Out of thousands of issues, two people have objected. Niels Rogge does community science at Hugging Face. He automated his own outreach job, first as a deterministic pipeline, then as an agent loop once the models got good enough to throw the pipeline away. • 07:01 - The whole thing is a cron job: a Python script calling an LLM API that reads the night's arXiv papers while he sleeps • 09:59 - Cursor replaced 12,000 lines of workflow code with a 200 line skill, and his own stack collapsed the same way: one CLI, one skill, a sandbox • 12:04 - Deployment is one container per GitHub issue, a fleet of agent loops started in parallel and thrown away after • 13:53 - He does not tell anyone it is an agent, because the bot label gets the issue closed, and it writes what he used to write by hand Two objections out of thousands is the number worth keeping. That is what automation looks like when the task was worth doing by hand in the first place. One person, one CLI, one skill. The quoted piece is about designing that CLI so the agent does not need a second one.