GitHub status: access issues and outage reports
Problems detected
Users are reporting problems related to: website down, sign in and errors.
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 24: Problems at GitHub
GitHub is having issues since 01:40 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 |
|---|---|---|
|
|
Website Down | 4 days ago |
|
|
Sign in | 10 days ago |
|
|
Website Down | 10 days ago |
|
|
Website Down | 12 days ago |
|
|
Sign in | 13 days ago |
|
|
Website Down | 17 days ago |
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:
-
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.
-
Fahim (@echo247365) reported237 real user stories. That is not a hype number. That is a receipt. Hermes Agent just published a page with 237 actual workflows from real builders across 15 categories. X posts, GitHub issues, Reddit threads, Hacker News, blogs, podcasts, LinkedIn, Discord. The page literally says these are real posts where people describe how they use Hermes. One person told Hermes to Google them, build a landing page based on what it found, SSH into a VPS, upload the page, and text them when it was done. Research, build, deploy, notify. That is a full loop. Another user runs Hermes every weekday at 9am to summarize their inbox and post the result to Slack. Not glamorous. But that is the kind of workflow that actually survives. Hermes is becoming a persistent worker. Not a chatbot. Not a code auto-complete toy. The bar for agents just went up. What is the one boring daily task you would automate if your agent actually remembered your workflows?
-
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.
-
Low Conviction (@lowconvictn) reportedMicrosoft just killed the AI coding tool its own engineers loved. The reason is brutal. It worked too well. In December, Microsoft gave thousands of its engineers access to Anthropic's Claude Code, running side by side with its own GitHub Copilot. Six months later, the verdict was in. Engineers picked Claude. They ignored Microsoft's own tool. So Microsoft is killing Claude Code by June 30. Nearly 100,000 engineers forced back onto the Copilot they already rejected. The leaked internal reason, per The Verge: "very popular, perhaps a little too popular." But popularity was only half the problem. The other half was the bill. - Per-engineer costs hit $500 to $2,000 per month - The same group runs Windows, Office, Teams, Outlook, and Surface - The cancellation lands exactly on the last day of Microsoft's fiscal year Then there is Uber. Uber gave Claude Code to 5,000 engineers. Adoption hit 95%. By April, they had burned through their entire 2026 AI budget. $3.4 Billion. Gone in four months. This is the ***** secret Big Tech will not say on an earnings call: The AI tools work. That is the problem. At scale, the tools that actually get used cost more than anyone budgeted for. The subsidy era is ending. The real bill is arriving. Is AI a productivity revolution, or just a cost nobody has figured out how to afford yet?
-
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
-
oskarscot 🏝️ (@oskarscot) reportedI 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 :/
-
Beyond Code (AJ ONeal) (@_beyondcode) reported@kaihendry @pierrecomputer Yes. And these people showcasing other diff products are doing so to point out that it's a false problem - particularly because GitHub just released an update last week improving the the performance by 10x... and it's still buggy and in some cases unusable slow.
-
Live 📿 (@LiveMatrixCode) reported@charliermarsh GitHub and Actions is a mess and has been so for a long time. Worst of all it is nowhere near ready the agentic era let alone human evaluators. Some good people there but leadership is letting people them down hard. At this point they need to stop focusing on copilot and fixing the infrastructure,UX/UI, features/ functionality and uptime. Not to mention security
-
Hrutik Kumthekar (@bushido_hk) reported@KaiXCreator Build something small that solves a problem you actually have. Employers care more about what you've shipped than what you've studied. Your GitHub matters more than your GPA.
-
Marcus Rummler (@Marcus_Rummler) reportedWhen working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.
-
itay shmool 🇮🇱☮️✨️ (@IShmool) reported@Cryptoxorz You caught the part most people miss — the ops loop. Bug reports flow into GitHub issues, Claude Agent SDK triages them, fix PRs get generated. The course isn't just built with AI, it's maintained by AI. That's the actual story.
-
Headbanger (@SaurabhSharma_I) reportedis @github Down ??
-
Minijus (@minijus) reported@matteocollina @github Downloading private action repos (ones that are not cached on GH actions runner) were failing this morning as well. Could be part of the same issue.
-
4A 45 56 49 4C (@4A4556494C) reportedCISA leaking AWS GovCloud keys on GitHub in the same week CISA adds Langflow to KEV is the kind of timing that makes you wonder if the simulation developers are just getting lazy with the writing. The agency responsible for telling every other organization to rotate credentials and scan for secrets in repos... exposed credentials in a repo. Not through a supply chain compromise. Not through a sophisticated attack chain. Through the most elementary operational security failure that exists. Every CISA advisory about credential hygiene, every binding operational directive about secrets management, every public guidance document about not committing keys to version control — all of it is still correct. And the organization that wrote it didn't follow it. This is the structural problem with security guidance as a product: the people who write best practices and the people who implement infrastructure are different groups with different incentive structures, and compliance frameworks don't close that gap. They paper over it. The fix isn't more guidance. It's pre-commit hooks that block secrets from ever reaching the remote. Automated. Mandatory. Not optional. We've had this technology for years and we still treat it as nice-to-have.
-
Contra (@supercontraa) reportedMicrosoft cancelling Claude Code licenses because token billing became too expensive. Uber reportedly burning through its AI budget in months. GitHub moving away from flat-rate pricing. This is the clearest signal yet that “per-token pricing” is breaking down at scale. Because tokens were never the real commodity. Compute capacity is. Which is bullish for solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA The endgame of AI infra isn’t selling API calls. It’s building markets around GPU-hours, reserved compute, forward capacity, and eventually compute futures. Just like cloud evolved from on-demand servers to reserved instances and long-term contracts, AI infra is heading toward financialized compute markets. solana:EN2nnxrg8uUi6x2sJkzNPd2eT6rB9rdSoQNNaENA4RZA could become part of the liquidity layer for AI compute itself.
-
Dene (@denehoffman) reported@charliermarsh Honestly every part of GitHub actions feels like the mistake of a first year dev. YAML configs, functions that can only be used in certain contexts, terrible documentation, no strong typing on things that will absolutely fail with the wrong types…
-
Mimu | AI Tools & News (@mimu_ai1) reportedThis open source killed the entire paid presentation tools industry. It's called Presenton and it already has 5K+ stars on GitHub. It turns prompts and documents into full presentations. And instead of trapping you inside some shiny SaaS editor, it lets you export real PPTX and PDF files. The wild part: Your existing ChatGPT subscription can be used to sign in and generate decks. No second subscription just to make slides. Features: • Prompt to presentation • Document to presentation • Editable PPTX export • PDF export • Custom templates • Self-hosting • Docker install • API access • BYOK • Ollama support What people pay for right now: AI slide subscriptions every month. Freelancers for simple decks. Agencies for pitch decks. Internal tools for repeat reports. Presenton turns the whole thing into: Sign in. Generate. Edit. Export. This is the kind of repo every founder, consultant, marketer, and student should bookmark.
-
Graylan (@graylanj) reported@rauchg i didn't mean your wiring Its a hypothetical btw like I originally found bad wiring in my house cuz my llama2 setup on GitHub/graylan0 told me ur house gonna burn down someone ****** with ur wiring in ur attic. then I went and found some ******** twisted wires together up there.
-
HEMANG DUTT MISHRA (@hemang2208) reportedAssume 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
-
priya joseph (@ayirpelle) reported@LigengZhu github link broken
-
Jon Pretty (@propensive) reported@Ciberon I usually max out at about six concurrent threads. Since I'm mostly working on Soundness, that means up to six *** worktrees. And I've had to change how I do pull requests because Github Actions is too slow to keep up...
-
Tech Friend AJ (@techfrenAJ) reportedCodex cloud has sucked for a while compared to Claude cloud Terrible GitHub integration. No model picker? Why
-
:) (@Eimen_Nur) reported@ThePrimeagen Github has had an issue the past 6 months…. We need something better
-
Owen (@owenyuwono) reported@ChShersh with github going down and getting hacked every week you might be onto something
-
Alpha Insights 🧬 (@AlphxInsights) reportedsayodotfun built an AI agent to mock hyperliquid and it somehow became a memecoin. HypurrClaw is this retarded perp gambling bot on solana that sends all trading fees straight to his github. tomorrow it comes online auto trading its own hyperliquid wallet and he's sharing the address. the origin story is actually clean. with perps hitting solana it's hitting at the perfect time and the absurdity makes it spread. most of the tweets are either explaining exactly this or callers bragging about 4x-7x from sub 30K. KOLs have been all over it. net inflow $1.9K with 83% buy ratio. one just bought $1.7K at current $113.5K mcap with 9.0 hotness score zero tweets and is still holding 100%. AlphaBlock caught this at $11.1K mcap on an 8.0 hotness KOL buy. social went from dead to 69 mentions in a day and it's accelerating with real discussion not just emoji spam. the wallets that matter loaded early and aren't selling. this is the kind of weird narrative that either dies fast or gets legs when the agent starts posting its terrible trades. i'm watching what happens when it goes live. 🔥
-
EPL CHAMPIONS 2025/26 (@Kenyanroux) reportedEither Github or Render must be down or something all my active deployments failed na I'm fighting one bug after another in trying to deploy them again
-
Jonathan Ong (@jongleberry) reported@matteocollina @github Oh, I thought this was something wrong with ubicloud, I've been dealing with a lot of GitHub Actions issues recently
-
Docsbook.io (@docsbook) reported@yoronneko qzsl6tool 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.
-
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.
-
Beau Johnson (@BeauJohnson89) reportedgoogle antigravity just got an unofficial terminal path testerlingcodo/gemini-antigravity-cli > 253 stars on github > created 2 days ago > mit + typescript > terminal ai coding agent for gemini and antigravity > slash commands, mcp server, plugins, agentic workflows > supports gemini 2.5 / 3.5 flash and antigravity models this is the pattern to watch every frontier lab is going to need a codex style cli because builders dont want another chat tab they want the model living in the terminal where the repo already is