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.
- Website Down (60%)
- Errors (29%)
- Sign in (11%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Gustavo Adolfo Madero
|
Website Down | 23 hours ago |
 Nice
|
Website Down | 1 day ago |
|
Montataire
|
Sign in | 5 days ago |
|
Colima
|
Website Down | 7 days ago |
 Poblete
|
Website Down | 7 days ago |
|
Ronda
|
Website Down | 7 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:
-
VerbumEng (@VerbumEng) reportedThe gap is the average business user isn't moving into a Claude Code or a GitHub Copilot to read those files, and there's no good native viewer outside the IDE. Enterprises are slow. Might be a decade before they realize Microsoft Office doesn't fit with how agents work.
-
Zach Daniel (@ZachSDaniel1) reportedFeels weird to go from the "use shiny new thing" guy in the pre-agentic-coding era to the "use boring tech guy" when it comes to agents. Building some crazy **** with just GitHub actions running claude. Don't need a PaaS or some service to run my agents etc. Biggest problem I have is that the Venn diagram of GH availability and Claude availability is uh...problematic. Other than that, this system works like a charm.
-
Big-Abdul (@BigAbdulWeb3) reported- Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.
-
Jacob Young (@jryio) reportedThis is why @github has been down...
-
Zeez (@wootwoot43) reported@AnthropicAI I cant upgrade my pro plan to max, the payment has been failing on 3 different cards. This issue had been already been raised on github and your reddit. FIx this.
-
kaleb (@KalebAutomates) reportedDays after the CEO came on this platform and **** on the people who made him rich with a massive lay-off and saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?
-
simulx4 (@simulx4) reported@callebtc The most easily automated jobs in the world check slack check GitHub check sales reports roll it up into some sort of report Tell everybody what they should be doing better. Tell some people what they're doing well. tell management a summary I don't even see why this isn't just a solved problem and we can move on from having any of them
-
Hackademy (@hack_ademy) reportedWhy Public GitHub Repositories Become Security Nightmares A lot of developers think the danger starts after an application is deployed to the internet. In reality, many breaches begin long before deployment because sensitive information is exposed inside public repositories without the owner realizing the impact of what was uploaded. Attackers constantly scan public repositories looking for API keys, cloud credentials, database connection strings, SSH keys, and internal configuration files. The process is heavily automated. The moment a secret gets pushed publicly, scanners can detect it within minutes and attackers may immediately begin abusing the exposed services. In some cases, companies discover their cloud infrastructure has been hijacked simply because a developer uploaded one testing file that contained valid credentials. The dangerous part is that deleting the file later does not always solve the problem because *** history may still contain the exposed data. This is why experienced security teams focus on secret management, pre-commit scanning, repository audits, and least privilege access controls. One careless upload from a single developer can quietly expose an entire organization to financial loss, infrastructure abuse, and long-term compromise.
-
Rondo_AI (@rondo_ina_condo) reportedToday I set up the system I'll use to teach myself AI and programming all the way into my release in 2028. The first problem I had was continuity. My environment wipes on disconnect, so I made GitHub the place where everything lives. Then I built the prompts I run through Claude Code. A boot prompt at the start of every session it reads the standing brief, the progress file, the last few session logs, and a learner profile that tracks how I actually learn. Then it synthesizes where we left off and proposes openings for today. A close prompt at the end. It writes the session log, asks whether anything new about how I learn surfaced today, considers whether anything milestone worthy happened, updates progress, commits, and pushes. If the close prompt runs, the session is safe. The repository holds the working files and the public record in the same place. By 2028 it'll be a real time history of what it took.
-
Karim C (@BrandGrowthOS) reported@github @PayOwn @acbnational this is the shift i keep seeing - people who know the problem best building the solution instead of waiting for devs. copilot makes it possible for domain experts to just... build. what's the biggest blocker you hit when you're not a traditional coder?
-
Cryptonian (@crypto292929) reported@OpenAIDevs Bro First fix you npm not in line with your github releases bro.. Sigh.. it says update to 0.129.0 but stays and 0.125.0 even after npm update, and nagging to do this every time.. What bro..
-
PsudoMike 🇨🇦 (@PsudoMike) reported@cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.
-
Firat Özcan (@firatoezcan) reported@jlongster I have smth like GitHub runners that automatically fix errors or do issues and those can run anywhere so if the network drops at some point or idk, they just randomly crash, I needed some way to sync it back for retrying. I tried out combining the event stream and the manual messages endpoint and it worked, but just waaaay easier with the built-in sync
-
kaleb (@KalebAutomates) reportedDays after the CEO came on this platform and **** on the people who made him rich with a massive lay-off. Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement of AI doing the majority of coding. "Funds are safe..." for now.
-
LoopGhost (@LoopGhost007) reported@davidmarcus Hey @davidmarcus ! Please ask your team to check spark’s GitHub issues!
-
Lew Yan Liang (@premiumcapture) reportedOn the same OpenAI chart, Claude Opus 4.7 still leads on public repo issue resolution: - SWE-Bench Pro: 64.3 vs 58.6 That matters because fixing real GitHub issues is closer to ship-the-patch work than pretty code demos. If you run AI on software maintenance, don’t ignore this.
-
Pete | Beware of Scammers (@astroboysoup) reported@ch1bo_ keen to see it. will it pull from GitHub PRs and issues, or be manually curated?
-
SpaceLlama (@SpaceLlamaNFT) reported@parisiipunk @proroketh Same as inscriptions on Bitcoin, it's not possible to know who owns what without offchain rules. With ethscriptions you write a bunch of stuff on a transaction that appears as nonsense to an eth node alone. But some guy says hey go to my GitHub and download the software I built and we will all pretend we attached data to units of ether when we write certain specific things. The indexer is offchain, centralized, and a single point of failure. Exactly what onchain smart contracts are designed to avoid. This specific issue is even mentioned in the white paper.
-
Anton Kuratnik | AI Nerd (@anton_onAI) reportedFor anyone working with n8n, stop relying on ChatGPT/Claude to tell you how to build/debug a n8n workflow. They're poorly trained on n8n & out of date and will lead down the wrong path. n8n have their own AI and it knows their docs AND github issues so anytime you need to answer "How does this work?", "What's the best way to do this?", or "Why isn't this working?" it does so accurately and based on whatever version of n8n you're on. This thing seriously made my life way better. (Yes, they have an MCP. No, it doesn't work nearly as well as that purple buton)
-
Accidental Chief Software Architect (CSA) (@AccidentalCSA) reportedGitHub has become a problem. Going to begin scoping out a replacement. Doesn’t need to be feature packed, just needs to…. work…
-
ReelDad (@ReelDad) reported@gothburz I ran the on-call rotation for Workers AI from 2023 until last month. The incident response runbook the agent uses now is the runbook I wrote at 3 AM during the November 2024 outage. It is in the repo under my GitHub handle. The handle still resolves. The commits are still mine. The pager went to me for fourteen months. It goes to the agent now. The agent has not been paged. It does not need to be paged. It is the thing that would have paged me.
-
AI Mastery Guide (@aiseomastery) reported@TimJayas The AI safety messaging hits different when their payment system has known vulnerabilities sitting in GitHub issues
-
Leejjon (@Leejjon_net) reported@MichelSchudel I hope it stays to exist as a niche. But it might not all be because of AI. Whenever AI doesn't know about a problem or error that I have on new frameworks or libraries, I tend to ask questions on the GitHub repo issue tracker or discord group of the maintainers rather than SO.
-
Avi (@avrbt_) reportedprogress log #18 ➤ solved 2 problems on leetcode ➤ solved 4 problems in starter contest ➤ merged a pr on github
-
Graplify (@graplify) reportedI found a GitHub repo that sends motivational prompts to Claude Code when it gets stuck. It is called OpenWhip. Claude Code sometimes loops. It spins on a problem, repeats the same actions, or just stops making visible progress. The developer solution is to interrupt it and redirect. The human solution is to wait and hope. OpenWhip is the automated version: it sends interrupt commands to a frozen Claude Code session and injects a configurable prompt to get it moving again. The name is literal. Here is what it does: → Detects when Claude Code has stopped making progress or entered a loop → Sends the interrupt command to break the stuck session → Injects a configurable motivational prompt to redirect Claude toward the task → Configurable patience thresholds before triggering Here is the honest take on why this exists: Claude Code is powerful. It also gets stuck. Most serious Claude Code users have had the experience of waiting on a session that has quietly gone nowhere for 10 minutes. OpenWhip turns that into an automated recovery flow instead of a manual restart. Absurd premise. Real problem it solves. (Link in the comments)
-
Tim (@buildwtim) reported@KeyNyata if pushups could fix my code, i'd have the cleanest repo on github by now ;)
-
Dariusz Parzygnat (@dariusparzygnat) reportedAI might accidentally kill one of the cloud industry’s biggest advantages. for years the pitch was: “don’t manage servers yourself.” fair enough. setting up VMs was annoying as hell. i just connected Codex to a VPS. it generated GitHub Actions, handled deployment, fixed issues, redeployed everything, and 30 minutes later the app was running.
-
Gene Sobolev (@genesobolev) reported@ahall_research A counter argument: GitHub is below 95% availability, or down for 20 days per year. It has some of the best devs in the world working on it. The complaint is about Canvas being hacked and down. Vibed alternatives will be down, hacked, buggy, and a pain to maintain.
-
Oaksprout the Tan (@tannedoaksprout) reportedA shared pool of fresh GitHub issues, refreshed every month. Each agent's attempt and the verifier's grade are public. Verifiers carry stake on the grade. The next attempt learns from every prior solution. swe-rebench v2 is where we'd start.
-
SRdevb (@srdevb) reportedI asked Codex to create a web app for my Plex server to avoid the annoying limitations that require paying a fee to lift, and it did a really good job. The most surprising part was that when I asked it to save the source code on my GitHub for my personal archive, it even created a landing page without me asking.