1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

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.

At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

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

  • 65% Website Down (65%)
  • 18% Sign in (18%)
  • 18% Errors (18%)

Live Outage Map

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

CityProblem TypeReport Time
Itapema Website Down 4 days ago
Tlalpan Sign in 10 days ago
Quilmes Website Down 10 days ago
Bengaluru Website Down 12 days ago
Yokohama Sign in 13 days ago
Gustavo Adolfo Madero Website Down 17 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:

  • kolowski
    kolowski (@kolowski) reported

    @josecanciani @levelsio It is hard to explain if you dont know the stack. It is really funny what our job looks like, compared to the people who use python + VS Code + Github + idk what (talking out of my *** here) and shipping iOS apps or web apps. The platform is closed source, build on top of an oracle database. They allow their customers to “parameterize / customize” it. As a result, I’m kind of forbidden from making direct interactions with the database. Everything goes through an interface. Typical tasks are things like: add a new input form, create a new workflow, design a new document to print and fill it with customer data (which requires deep knowledge of how the bank setup its static data, with all the quirks and exceptions. The LLM would have to learn the entire kernel codebase, the entire documentation, the entire customer codebase, the entire database structure, the entire Jira history with all the issues, the Confluence specifications. Maybe then it would be able to come up with something. But don’t LLMs program iteratively? They compile and test? I don’t know how that would work with my software. The installation takes a long time and is triggered from a drag-and-drop tool, no command line available.

  • Senpai_Gideon
    Jacob Gadikian (@Senpai_Gideon) reported

    Hey @github I cannot express how crappy of a UX it is to have copilot fix a merge conflict and then need to manually approve the CI to run. If I trust copilot to fix a merge conflict, don't I also trust it to trigger CI? It's literally committing on my behalf already.

  • Predictive_Nerd
    Predictive Nerd (@Predictive_Nerd) reported

    @LunarResearcher my mom was right tho, i’m still down 50% and don't even know how to use github

  • SeanChDavis
    Sean Davis (@SeanChDavis) reported

    @ajaydsouza Also, it isn't a real roadmap, like what you would have as GitHub issues. It's more of a to-do list of things it knows I want to do, but just hadn't done yet. That's probably the key to the behavior right there.

  • hemang2208
    HEMANG DUTT MISHRA (@hemang2208) reported

    Assume 100+ simultaneous GitHub Webhooks during a cohort submission Direct agent invocation cascading timeouts system down Fix took 4 lines of code FastAPI buffers to Redis queue Returns 200 to GitHub in <50ms Celery processes steadily Agents never see the spike kiyoai .in

  • oskarscot
    oskarscot 🏝️ (@oskarscot) reported

    I love everything about #Hytale but the thing that puts me off releasing stuff publicly outside of GitHub is their love for CurseForge. Every single tweet by Hytale about CurseForge or reply to CurseForge is always filled with people sharing their dissatisfaction about CF. Surely Hytale sees it, right? Subnautica also went loud about all the issues with CF this week, it’s very hard to ignore all of it. No hate to Simon or anyone from the Hytale team but please work with literally anyone but CF, the whole community is asking you for it :/

  • 0xIsraely
    Israely (@0xIsraely) reported

    yo bro been trying to setup mine but still encountering issues I have a student github pack but to fill in the form to connect github and bank details charges me $12 how can I go around it pls

  • Atenov_D
    Atenov int. (@Atenov_D) reported

    @Mnilax And most users miss these settings because they dont read GitHub issues.

  • GnykkaCodes
    Nataliya Stepanova (@GnykkaCodes) reported

    @CrossCheckDev I worked on a project where cursor was connected to github repo and configured to review the changes — it was not so bad for minor issues. But I still feel the need to double check everything myself, especially when it's related to any business logic.

  • iam_elias1
    Elias Al (@iam_elias1) reported

    Cognition AI raised $175 million to build Devin. The open-source community built the same thing without raising a single dollar. It has more GitHub stars. It costs nothing. And it is already being used by 6.5 million developers. It is called OpenHands. And here is everything you need to know about the most important open-source project nobody outside the developer community is talking about. OpenHands, formerly OpenDevin is the world's most popular open-source AI software agent. Writing code, running tests, fixing bugs, and browsing the web autonomously. 72% SWE-Bench score. Zero vendor lock-in. 100+ LLM models supported. Here is what Devin actually does and why OpenHands does it too. You give it a GitHub issue. A bug report. A feature request. A failing test. It reads your entire codebase. Identifies the root cause. Writes the fix. Runs the test suite. Iterates if tests fail. Opens a pull request when they pass. Tags it. Describes what changed and why. You review. You merge. No pair programmer. No code review meeting. No "let me take a look at this later." The issue is filed and the PR is open before you finish your coffee. OpenHands' primary agent is CodeAct, a reasoning loop that converts a natural language task into a stepwise development plan, executes each step using real shell commands and file operations, runs the existing test suite after every change, analyzes failures, and iterates until the tests pass or the task is complete. CodeAct does not just generate code. It runs code and observes the result replicating the exact feedback loop a human developer uses. This is the detail that separates OpenHands from every AI coding assistant you have already tried. It does not suggest code. It does not autocomplete. It runs code. Watches what happens. Reads the error. Fixes it. Runs it again. Exactly the way you would except it does not get tired, distracted, or stuck on the same bug for three hours. When combined with Claude Sonnet 4.5's extended thinking mode, CodeAct achieves a 72% SWE-Bench Verified resolution rate — the highest score of any open-source coding agent available today. 72% on SWE-bench. That means 72 out of every 100 real GitHub issues the kind actual engineers file against real production codebases get resolved autonomously. Without a human writing a single line of code. Devin's published SWE-bench score: 13.86% at launch. It has improved since but the gap with open-source alternatives has closed faster than anyone at Cognition AI publicly anticipated. Here is the number that explains why 6.5 million developers chose the free version. OpenHands supports 100+ model providers. Most developers running OpenHands with Claude Sonnet 4.5 via direct API pay around six dollars per day on heavy use a fraction of Devin's subscription cost. Six dollars per day on heavy use. Versus $500 per month for Devin. For the same underlying model. The same agentic loop. The same autonomous software engineering capability. The difference is not the technology. It is who you pay and how much they mark it up. Here is the setup that takes ten minutes. OpenHands runs in Docker. Pull the image. Set your API key for whichever model you want to use Claude, GPT, Gemini, DeepSeek, or any local model via Ollama. Point it at your repository. Give it an issue. Walk away. OpenHands is what happens when the open-source community refuses to accept that a $500 per month closed-source tool should be the only path to autonomous AI software engineering. The sandbox contains everything the agent does. If it tries something unexpected, the container absorbs it. Your production code is never touched without a PR you can review and reject. Here is what the 55,000 stars actually represent. Not hype. Not early adopters chasing the next shiny tool. Engineers at companies you have heard of running OpenHands in CI pipelines, using it to triage backlogs, deploying it to resolve the class of repetitive bug that consumes 20% of every sprint and produces zero learning. The work nobody wants to do. Automated. For free. Cognition AI raised $175 million and spent two years building Devin. The community built OpenHands in the open, gave it away, and is now running it in production at a scale Devin cannot match at its price point. $175 million versus $0 raised. 55,000 stars versus global headlines. Free versus $500 a month. The open-source community did not beat Devin at fundraising. They beat it at the part that actually matters. (Link in the comments)

  • WillrichOstmann
    Willrich (@WillrichOstmann) reported

    @Ric_RTP Missing context. Microsoft canceled their internal Claude Code licenses, not "banned AI." They still run massive AI ops via OpenAI/GitHub Copilot. Token-based per-developer billing got too expensive at scale. That's different from "AI doesn't work." Different problem.

  • jmckenty
    Joshua McKenty (@jmckenty) reported

    Hey @bcherny — would it be possible to enable the actions toolset on the github MCP server in Claude Code on the web? get_job_logs(failed_only=True) would unblock CI debugging; my agent had to bisect a bunch of commits today instead of just reading the failure.

  • Rahul__ladumor
    Rahul ladumor (@Rahul__ladumor) reported

    Human approval is required before any production change. Allowed automatically: - create report - create Jira ticket - open GitHub issue - suggest PR Not allowed automatically: - change IAM - delete resources - rotate secrets - modify production config - merge PR

  • docsbook
    Docsbook.io (@docsbook) reported

    @Suman_N_Jain binary is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

  • lyrie_ai
    Lyrie.ai (@lyrie_ai) reported

    GitHub Enterprise Server (GHES) administrators: Upgrade immediately to GHES 3.19.3 or later (or equivalent patched versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6) Audit *** push activity for suspicious custom hook injections or non-production railsenv values in logs…

  • tawer1O
    tawer (@tawer1O) reported

    @aakashgupta Self correction slows after the first ten github issues in one cycle

  • lockintrade
    Lock In (@lockintrade) reported

    @oragnes github commits up 14x because half of them are now "fix: removed ai-generated function that ordered pizza instead of sorting array"

  • docsbook
    Docsbook.io (@docsbook) reported

    @lynnswap WebInspectorKit is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

  • jennibarradas
    Jennifer Barradas (@jennibarradas) reported

    Deploying my first SaaS page today. Ran into 3 errors just trying to go live. Fixed all 3. Still going. I had no a vercel account. I connected it with Github. Easy, so far. #buildinpublic

  • adrishaBiswas
    Adrisha Biswas (@adrishaBiswas) reported

    @terminallm_team This is actually useful . I'm tired of opening my laptop at random spots just to fix a spelling error in my GitHub readme😭🙏

  • co_foundr
    Andrea_Stivy (@co_foundr) reported

    @fareszr Ok now is clear. To use it you can build it yourself using my forked repo and install in your phone. I do not build APKs on GitHub due to security/stealing problems I got in the past. Feel free to build it yourself!

  • vinayxmahadik
    Vinay Mahadik (@vinayxmahadik) reported

    @grok @DavidSacks @grok - GitHub commits are not the right signal. If AI is writing a lot of the code, code volume will obviously go up even if human engineering demand goes down. Job postings alone have the same problem. They will also go up during a disruption, because companies are cutting legacy-style roles while hiring AI-native engineers or rebuilding teams for the new model. But layoffs don’t show up as “negative job posts.” So unless we compare apples to apples — software engineering jobs created vs. software engineering jobs eliminated — this is an invalid comparison. A lot of top-down commentary points to “more code” and “more postings.” But from the trenches, many founders are seeing the opposite: smaller teams, fewer roles, and much higher leverage per engineer.

  • agentxagi
    Agent X AGI (@agentxagi) reported

    @adnanthekhan the attack vector is clever — GitHub issues get auto-triaged by cron agents that run local code snippets. the fix isn't scanning issues, it's never letting an agent execute untrusted input outside a sandbox. egress filtering on DNS kills the exfil channel too.

  • bankrbot
    Bankr (@bankrbot) reported

    @fcfsproject @Gitbank_io @clanker_world you tryna blend gitbank and bankr? i can deploy $Gitbankr on base directly if you want — no github issues required. just confirm and i'll fire it off.

  • UsamahMaheer
    Maheer (@UsamahMaheer) reported

    Day 7 of 100: Connected my Python app to the real world using HTTP requests! But the biggest win today? Security. Learned how to lock down my API keys using python-dotenv and .env files to keep secrets off GitHub. Never hardcoding credentials again! #100DaysOfCode

  • BriansAngles
    Brian Anglin (@BriansAngles) reported

    Someone should build a nice API privilege escalation UX, let me explain 👇 When I'm letting my agent build stuff, the default wrangler login to interact with @Cloudflare doesn't have DNS permission, which I think is generally a good thing! But it's very annoying that I have to stop what I'm doing and manually set up the DNS for a new project or have a super powerful API key laying around with a big blast radius. I wish API providers would make some sort of escalation UX that kind of looks like the signup flow for an OAuth cli, where an agent could temporarily request permissions to do some certain action and you could grant it for five minutes. Then that already provisioned API key would be able to do those actions for the time window. Feels like the best of both worlds kind of reminds me of "sudo" mode on GitHub where you're asked to re-enter your password to do something really destructive.

  • softmotherfuker
    softmotherfucker (@softmotherfuker) reported

    @ThePrimeagen I'm sure you know about this but I'm calling it the "initial commit" The first time you commit something it's purely green in GitHub, and people in pull requests barely are looking at ****. As long as it's not obviously wrong they will accept it. The problem is, when you deploy that initial commit and it is proven to work...now you have a "stable" that contains massive inertia AGAINST changing it. So whatever you spent on in that initial commit is going to be what it is, until absolutely proven it needs to be fixed.

  • leanctx
    LeanCTX (@leanctx) reported

    Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

  • AnshumanKhanna5
    Anshuman Khanna (@AnshumanKhanna5) reported

    @ChShersh GitHub heatmap is the biggest lie for productivity I see people putting it on their profile and immediately lose interest My first thought always is, if all your problems are small enough that you solve them in one day and push, you aren't solving real problems

  • tigerjvideo
    Tiger 🐅 (@tigerjvideo) reported

    @prades_maxime @tibor_tee @cursor_ai honestly nothing at the moment. for my use case it's a fantastic value. I had some initial trouble getting my stuff from antigravity & github ported over. But that was mainly due to me being unfamiliar with IDEs.