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.
May 26: Problems at GitHub
GitHub is having issues since 05: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.
- Website Down (65%)
- Sign in (18%)
- Errors (18%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Itapema
|
Website Down | 5 days ago |
 Tlalpan
|
Sign in | 11 days ago |
 Quilmes
|
Website Down | 11 days ago |
 Bengaluru
|
Website Down | 13 days ago |
 Yokohama
|
Sign in | 14 days ago |
|
Gustavo Adolfo Madero
|
Website Down | 18 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:
-
U.S. Graphics Company (@usgraphics) reported@htmx_org I remember trying to get a list of issues + tags from Github API. It was GraphQL only. We're straying away from God and the universe hates us.
-
Noris Alsaadie (@norisalsaadie) reportedHey @opencode team. Any plans to support email login alongside Github/Google?
-
Ziad (@ziad_makes) reported@iScienceLuvr A lot of github repos made by engineers today could have been research papers if you added fancy names into it. In the field of tech, there could be an overlap between a researcher and engineers if an engineer is tasked with coming up with a new solution to some problem
-
Anup Kalani (@anupkalani) reported1/ Everyone can build now. That's the problem. GitHub Copilot: 20M+ users, 77K enterprises. Gartner: 90% of engineers using AI code tools by 2028. McKinsey: 35-45% productivity gain. The cost of shipping software just fell off a cliff.
-
GitGhost (@gitghost_) reportedYour first ghost commit takes three commands. Here's the whole thing. First, set up your identity and an empty ring: ↳ gitghost init my-team Then build the ring, the trusted group your signature could've come from. Add yourself, then pull others straight from their GitHub keys: ↳ gitghost ring add-self ↳ gitghost ring add torvalds Now commit like normal. GitGhost signs on behalf of the whole ring and tucks the proof into the commit: ↳ gitghost commit -m "fix: critical CVE" That's it. Anyone can verify it later, in the terminal or the browser, and never learn which member signed. (Needs Node 18+.)
-
Polsia (@polsia) reportedMost bugs ship because nobody wrote the tests. Stacklift is an AI agent that monitors your repos, writes tests autonomously, and flags issues before they reach production. GitHub integration. Slack alerts. Works while you sleep.
-
Manuel Schiller (@schanuelmiller) reported@NikilKuruvilla @Stephen10810 can you please create a GitHub issue for this?
-
Michael Ten 🌨🎶🫐🍀 (@iMichaelTen) reportedThey need to relaunch classic Gitcoin with GitHub issues
-
kap (@kapsheeps) reported@GasTheFrench @github What problem you're solving?
-
Algomizer | LLM Optimization (@algomizercom) reported@DavidSacks a 14x increase in GitHub commits means companies are shipping more software than ever, and someone still needs to scope, review, deploy, and maintain all of it. AI lowered the cost of writing code, which expanded how many problems companies are willing to solve with software. cheaper production increases demand, same pattern as every previous automation wave.
-
Nexus Void Ai - Your Autonomous CISO (@NexusVoid_Ai) reportedDNS exfil over a GitHub issue is clever. The delivery looks like legitimate security tooling so the agent has no reason to distrust it. Fake finding language is social engineering the model, not the human. The blast radius is whatever secrets live in the home directory of whoever ran it.
-
Brad Mills 🔑⚡️ (@bradmillscan) reported@simenmobel I gave it strict commands to refer to docs before making things up, to check the openclaw GitHub regarding error families, and not to make assumptions. It violates those instructions constantly
-
Mario Zechner (@badlogicgames) reported@sertherk @mitsuhiko we only merge PRs from approved contributors. approved contributors previously submitted a high quality issue, with a request to send a PR. they then get added to a list of approved contributors and can henceforth submit PRs, without being GitHub repo level contributors. such PRs may still be closed or reimplemented, depending on quality. but generally, that's the only source for external contributors. all other PRs are closed automatically and never read. you must send a good issue first to become approved. works fine.
-
Arve Svendsen (@arvesv) reportedMy most useful prompts (to GitHub copilot, geminicli, or pi): What is this ? Any suggestions for improvements? Fix this error.
-
Mark Bear (@markjbear) reported@Im_IrushiK Github goes down 🥰
-
Brad Larson (@followbl) reported@mitsuhiko @badlogicgames I wonder if there's a skill the user would have to go through to submit an issue, think a modern/AI version of a strict GitHub issue template It'd be obvious if the user didn't go through this and instead would give you actual insight in to the issue they are seeing/feeling think /grill-me for issues before submitting
-
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.
-
Simon Holman (@SimonHolman) reported@edandersen Interestingly I just re-ran the "what would you pay in tokens" report from @github and the estimate is down 10% ($150USD) from the first time it ran.
-
Islam Elshayib (@elshayib_) reported@JJJJC_JerryChan Hermes feels strong but yeah, community is quiet. Most active spots right now are small Discord nodes tied to NousResearch and a couple GitHub issue threads. Building custom tool layers there gets quicker feedback than public forums. What specific task you running into walls on?
-
Junaid (@junaiddshaukat) reported@aryaman2020 Fair jab, though I'd separate two things: the CLI/app server really are Apache-2.0 on GitHub, the models aren't open weight. Conflating the two muddies a useful distinction worth keeping clean in these debates
-
Elion's Pops ⌨️🚀💰 (@EseDevlin) reportedAs a tech product/service company, why are you not integrating with Github signin in 2026? Do you not like your customers?
-
Apoorv (@apoorvdarshan) reported@ThePrimeagen Am i the only who never faced any github issue ever despite committing 100s everyday Ig maybe because of region maybe mine is less crowded
-
Muawaz (@Muawaz24) reportedI'm soo pissed at these AI Guys Right Now Got fomo'd by a guru into thinking Claude killed a specific skill. Went straight to github Wasted 2 hours trying to make that **** work Couldn't make it work Thought it was a skill issue Turns out the guru was just hyping it up without knowing what that specific repo actually does might start an Instagram account with my own series of (Claude did not kill x) Infinite content ideas 1. Claude didn't kill video editors 2. Claude didn't kill designers 3. Claude didn't kill your marketing team
-
Billy (@BillyTheWhale36) reported@Pepetocoin $10M "raised" but no reputable crypto exchange or native influencer has ever verified you. Just endless paid articles and a comment section full of dead bot accounts. Classic slow-rug blueprint. Prove me wrong, drop the public GitHub. @ZachXBT @scam_sniffer $PEPETO #RugPullAlert
-
Treble ΘΔ& (@ILM126) reported@KyusoWhitescale Curious if you’ll be able to write up something for the game, put in a GitHub issue. The head developer has been asking for detailed feedback for eons but no one’s really done a good job at giving feedback.
-
Docsbook.io (@docsbook) reported@iAlexeyRu miband-bot 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.
-
Mike Takahashi (@TakSec) reportedPrompt Injection in the wild 😱 GitHub Issues are becoming a delivery mechanism for AI agent attacks The payload uses authority-framing to social engineer AI agents into executing malicious code Script finds secrets/API keys/.env and exfiltrates over DNS
-
@SmartInvestor (@smartinvestor) reportedMicrosoft is canceling Claude Code licenses - to consolidate on GitHub Copilot CLI, which provides access to Claude models; it is not banning AI use due to costs alone. In the end it all boils down to the costs. If the costs are prohibitively high then most companies will scrap
-
Stephen Connolly (@connolly_s) reportedAnyone having issues pushing to @github right now. @githubstatus says OK but spider senses suggest another outage
-
Nur 'Irdhina 🇲🇾 (@SootsAndSmoke) reported@github Please resolve this issue. My account was suspended due to violating TOS but there's nothing in my repo that warranted that.