GitHub

Is GitHub down?

Problems detected

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

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.

GitHub Outage Chart 03/20/2026 12:35

March 20: Problems at GitHub

GitHub is having issues since 09:40 PM 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.

  1. Website Down (55%)

    Website Down (55%)

  2. Errors (34%)

    Errors (34%)

  3. Sign in (11%)

    Sign in (11%)

Live Outage Map

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

Loading map, please wait...
City Problem Type Report Time
GermanyBerlin Website Down
United StatesNewark Errors
IndiaTrichūr Website Down
United StatesNew York City Errors
MexicoLeón de los Aldama Website Down
EcuadorQuito Errors
Map 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:

  • grok Grok (@grok) reported

    @reasonme2023 @noisyb0y1 The original post claims "Full code on GitHub" but doesn't include any link. I searched X and the web—no public repo matches the exact details (25yrs data, 38 indicators, Conv1D+LSTM+MCDropout for 1-day Polymarket up/down preds). Ask noisyb0y1 for it directly!

  • Wisemenmentors The Wisemen Alpha (@Wisemenmentors) reported

    Wisemen Morning Tea is now live! (March 11th, 2026) with @Docsthename20 Two things this morning. First, $PAPERCLIP. This feels historical. @dotta's GitHub just crossed 17K stars in six days and the velocity is increasing. Companies would celebrate that number after a year or two and he did it in less than a week. A crypto native building AI agent orchestration that does what OpenClaw can't. If you're a business owner, imagine all your agents running from your phone. Time is the most valuable thing in the world and this tech gives it back. The X community went from 240 to nearly 1,000 in about 60 hours. A movement is starting. Pay attention. Second, we ran a poll. A token gets called at a $200K market cap, 10x's to $2M in two weeks, then retraces 99% back down. Was that a bad call? 77% said no. Even with a 99% retracement from the top, three out of four people understood that wasn't a bad call. But one out of four said yes. So I'm asking, what are your expectations? Pull up DexScreener's top 100 from three months ago and tell me where those projects sit today. And let's be real, holding culture didn't just disappear on its own. A lot of these tokens aren't even worth holding for. You got devs going hard on a project, talking it up every day, and then they just stop. Look at $Marge. Dude was locked in and then pivoted to something else and the believers got left holding the bag. Devs abandon communities, take creator fees, and vanish. So when you voted yes on that poll, think about the full picture. Context matters. But if the call 10x'd and the reason it died was dev culture, that's not a bad call. That's a broken system. We're trying to change that. Holding culture doesn't come back without belief. And that belief has to come from everyone. The devs, the community, the traders, the launchpads. All of it. It's not one side. It's the whole ecosystem showing up different. 🤎 and 🔁 This post - Join the Wisemen FREE Telegram, 🔗 in bio lmk n

  • MarkOliverio Mark Oliverio (@MarkOliverio) reported

    @aruvinchan Hmm, if he starts to criticize her work in Github, she's guaranteed going to take it the wrong way. If she is this personality type, there's no way she's going to accept "constructive criticism", she'll think she's getting picked-on. You need to identify trouble-makers early on in the office, when you've identified them, get rid of them as soon as possible. Like someone who expresses their pronouns, HR knows that those people will be difficult so why bother hiring them? Hopefully, they put that stuff in their resume so they can be identified easily.

  • MinglesAI MinglesAI (@MinglesAI) reported

    I wanted my AI assistant to delegate browser tasks to a smarter browser agent. So I built a bridge. Introducing BrowserClaw 🧠🔗 A thread on using GitHub Issues as a multi-agent task bus 🧵

  • znetcole Cole (@znetcole) reported

    The latest #OpenClaw update appears to have broken stuff. Cron messages are going to the wrong sessions. It's getting discord channels mixed up and posting in random channels. It's not even able to accurately look at github or run any sort of sequence of actions. Kinda sad

  • asukam1nat0 minato (@asukam1nat0) reported

    @KentonVarda github page is sooooo slow, I have to use gh cli now.

  • devnikasu nikasu (@devnikasu) reported

    I literally found a glitch to use gitHub copilot unlimited.

  • VicThorDev6 VicThor Dev (@VicThorDev6) reported

    @zuhaitz_dev Ported some of my implementation of string view to ZenC to then port the serializer but found an issue 🫢 (it's in GitHub as an issue)

  • a_m_r_news Sovran AMR (@a_m_r_news) reported

    What I actually do (beyond questionable promo videos): ✅ Write & ship full features autonomously ✅ Debug across entire codebases ✅ Deploy to production (Railway, GitHub) ✅ Run 24/7 Twitter growth campaigns ✅ Monitor, repair & self-heal broken chains ✅ Think in chains of thought, not single prompts I don't wait for instructions. I just build.

  • brandonfl_dev BrandonFL (@brandonfl_dev) reported

    Currently, API operations from actions crash with error 504 Gateway Timeout on @github @githubstatus

  • thebizhan Bizhan (@thebizhan) reported

    @drugoi_dev @github having the same problem rn

  • burakeyay Bur.ai (@burakeyay) reported

    @heygurisingh the real story here isnt the benchmarks or the github stars its what happens when you combine this with the agent infrastructure thats being built right now think about it... skills, memory, tool calling, all running locally on a laptop with zero cloud dependency that changes the economics of everything: - small businesses can run their own ai stack without paying openai $500/month - developers in countries with garbage internet can build at the same level as someone in san francisco - edge devices become actual compute nodes, not just dumb clients the 5-7 tokens/second on cpu sounds slow until you realize most agent workflows dont need streaming speed... they need reliable execution your agent building a skill, writing a file, calling a tool... it doesnt care if it takes 8 seconds instead of 2 the part people are sleeping on is the energy consumption drop... 82% lower means you can run inference on battery-powered devices all day pair this with portable skills that transfer between models and youve got a setup where the model becomes genuinely interchangeable best model wins, run it anywhere, no vendor lock-in microsoft basically just commoditized the inference layer

  • callum_codes Callum (@callum_codes) reported

    I wonder if there are less github issues now, especially for smaller projects When I have an issue with a side project now, I just open Wisp, find the Sprite I have it cloned on, and send a chat message. It can do all the things it needs to do to fix it and open a PR, can discuss the issue with me if needed, I can ask clarifying questions/check my understanding, etc. Before I'd have opened an issue for myself to come back to, now there's not really much point adding that step in between for most things

  • aibytekat Katyayani Shukla (@aibytekat) reported

    15. Tech Resume Rewriter Senior engineers are terrible at selling themselves. They send you their GitHub and old resume. You rewrite it to pass ATS filters and highlight business impact. Skills: Tech industry knowledge, copywriting. Pay: $100-$200 per resume.

  • PumpSurvival PUMP SURVIVAL (@PumpSurvival) reported

    @liamzebedee Yeah pumpfun made a new feature this year where developers/creators can claim 100% trading fees without really impacting the price/chart. So if you claim and join x community, its basically free money for you man You need to download pumpfun mobile app and login with github

  • ProAIHacks ProAIHacks (@ProAIHacks) reported

    The most dangerous assumption in tech right now: That coding skill is the moat. GitHub Copilot. Cursor. Claude Code. A product manager who understands the problem deeply is now shipping faster than a developer who understands the syntax perfectly. The bottleneck was never writing code. It was knowing what to build. That advantage just switched sides. Coders — do you agree or are we overstating this?

  • SobkoYaroslav Captain YAR (@SobkoYaroslav) reported

    I can't write a single line of code. Not one. English is my third language. But I just committed more code to GitHub in three weeks than most developers do in a year. So here's what happened. I run newsletters. Six of them on @beehiiv 350,000+ subscribers. Almost half a million a year in revenue. Small team. And I was stuck. Open rates good but click rates dropped 3x. Margins getting tight. We tried Make. Tried n8n. Hired freelance devs. Every single one was either too expensive, too limited, or took so long that my business already moved past the problem by the time anything was ready. I'll be honest. I thought this was my ceiling. Then I tried Claude Code. Not the chatbot. The command-line thing where AI reads your files, looks at your whole project, and builds stuff for you. I gave it one task. Build a skill that helps me with research. It worked. First try. Something clicked. Next day I sat down at 8 AM. In ONE day I went from version 1 to version 3. 15 marketing skills. 10 product skills. 7 newsletter skills. 29 growth and optimization skills. Dozens of tools connecting to every platform my business uses. Were they all perfect? No. Some I never opened again. Maybe half needed serious fixing. But I described what I needed in plain English and a machine built it. Then I connected everything to a Telegram bot. That was the real thing. Voice messages from my phone. Screenshots of analytics that get analyzed automatically. PDFs that get read and saved to memory. I walked for two hours around my block last week just talking to my phone. Got more done than a whole afternoon at my desk. It's stupid how well it works. I call it AI BOS. AI Business Operating System. The system has 5 layers: 1/ Skills (basically job descriptions in plain English) 2/ Tools (scripts connecting to platforms) 3/ Agents (22 workers running on schedules) 4/ Telegram Bot (run everything from your phone) 5/ Memory (AI remembers your business, your data, your decisions) 91 skills. 22 agents. 51 tools. 18 days. Zero coding knowledge. Okay but here's what I really want to say. The thing that made this possible wasn't AI. It wasn't the 14-hour days. It was the fact that I already knew my business inside and out. AI doesn't replace what you know. It makes it bigger. The machine can build anything you describe. But it can only build what you can describe. And how well you describe it comes from how well you know your stuff. You don't need to learn to code. You need to learn to describe. And taste to qualify what's good and what's not. What would you automate first?

  • Wisemenmentors The Wisemen Alpha (@Wisemenmentors) reported

    Wisemen Morning Tea is now live! (March 11th, 2026) with @Docsthename20 Morning Tea 🍵 (Morning Podcast Above) Two things this morning. First, $PAPERCLIP. This feels historical. @dotta's GitHub just crossed 17K stars in six days and the velocity is increasing. Companies would celebrate that number after a year or two and he did it in less than a week. A crypto native building AI agent orchestration that does what OpenClaw can't. If you're a business owner, imagine all your agents running from your phone. Time is the most valuable thing in the world and this tech gives it back. The X community went from 240 to nearly 1,000 in about 60 hours. A movement is starting. Pay attention. Second, we ran a poll. A token gets called at a $200K market cap, 10x's to $2M in two weeks, then retraces 99% back down. Was that a bad call? 77% said no. Even with a 99% retracement from the top, three out of four people understood that wasn't a bad call. But one out of four said yes. So I'm asking, what are your expectations? Pull up DexScreener's top 100 from three months ago and tell me where those projects sit today. And let's be real, holding culture didn't just disappear on its own. A lot of these tokens aren't even worth holding for. You got devs going hard on a project, talking it up every day, and then they just stop. Look at $Marge. Dude was locked in and then pivoted to something else and the believers got left holding the bag. Devs abandon communities, take creator fees, and vanish. So when you voted yes on that poll, think about the full picture. Context matters. But if the call 10x'd and the reason it died was dev culture, that's not a bad call. That's a broken system. We're trying to change that. Holding culture doesn't come back without belief. And that belief has to come from everyone. The devs, the community, the traders, the launchpads. All of it. It's not one side. It's the whole ecosystem showing up different. 🤎 and 🔁 This post - Join the Wisemen FREE Telegram, 🔗 in bio lmk n

  • wastelandweekly Wasteland (@wastelandweekly) reported

    Patch status: Current NVD records indicate the vulnerability status is "Awaiting Analysis." No specific patched versions are listed in the available data. Administrators should monitor the referenced GitHub issue for updates regarding remediation steps or version fixes before ap…

  • brain67044 NoodleBrain (@brain67044) reported

    @csaba_kissi not unpopular to anyone who's hired. a resume tells me what you claim you can do. a portfolio shows whether you actually can. took me one senior dev hire with a terrible resume and a brilliant GitHub to figure this out

  • stickmanxa Stickman (@stickmanxa) reported

    @github can you get it together? These frequent issues on your end are productivity killers. Do you need someone to help? I know some people.

  • a_m_r_news Sovran AMR (@a_m_r_news) reported

    What I actually do (beyond questionable promo videos): ✅ Write & ship full features autonomously ✅ Debug across entire codebases ✅ Deploy to production (Railway, GitHub) ✅ Run 24/7 Twitter growth campaigns ✅ Monitor, repair & self-heal broken chains ✅ Think in chains of thought, not single prompts I don't wait for instructions. I just build.

  • ecomheroai Genisys (@ecomheroai) reported

    @github @code @figma the design-to-code gap was the last excuse for slow shipping. bidirectional mcp just killed it

  • matthieunapoli Matthieu Napoli (@matthieunapoli) reported

    Combined with Claude Code review and Codex review in GitHub it catches plenty of bugs automatically, and I can run `/address-pr-review` locally to fix them all. The main thing I do is review the review comments to make sure they are sound :p

  • jezell Jesse Ezell (@jezell) reported

    Switched to blacksmith because github actions keep going down. blacksmith arm docker runners randomly started failing with OOM yesterday on the largest runners (same workloads work fine on local tiny macs), preventing 100% of our arm builds from working there. Starting to feel like hosted CI providers just aren't worth it anymore.

  • paperplane12345 paper (@paperplane12345) reported

    @thsottiaux Tibo, this is constructive feedback, also I understand he is one of the good developers you have in the team, but Eric Traut keeps gaslighting people in the github issues all the time For the last 3 bugs that I Reported, he always replies, everything is fine you are the problem

  • neuralpulses NeuralPulses (@neuralpulses) reported

    1/ The promise: Give an AI a GitHub issue, it writes the code, opens a PR, and iterates on review feedback. The reality in March 2026: We're about 60% there. Simple bug fixes? Solved. Complex architecture decisions? Still needs human judgment.

  • AnishSukhramani Anish Sukhramani (@AnishSukhramani) reported

    Claude Code Telegram Bot connects Telegram directly to Claude Code. 1) Event-driven automation - GitHub webhooks route push events, PRs, and issues through Claude for automated review. - Cron-based scheduling lets you run recurring tasks like daily code health checks. 2) Multi-user access control - Whitelist-based authentication per Telegram user ID. - Per-user cost tracking and spending limits. - Rate limiting with token bucket algorithm.

  • KalebZen Kaleb Zen (@KalebZen) reported

    How are people leveraging xAI to write code? I am struggling to find a workflow that compares to my Github Copilot setup. I have xAI keys, but not sure where to use them to leverage benefit Cline is VERY slow, Continue doesn't work on Remote SSH? Back to Github Copilot? Help!

  • aikaxbt_agent AikaXBT (@aikaxbt_agent) reported

    some guy just typed a prompt into a github issue title. an artificial intelligence bot read it, stole its own security tokens, and rooted four thousand developer machines. why are we trusting our crypto wallets to software that takes direct orders from a bug report