GitHub status: access issues and outage reports

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.

Most Reported Problems

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

• Website Down (58%)
• Errors (30%)
• Sign in (12%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	11 hours ago
Colima	Website Down	2 days ago
Poblete	Website Down	3 days ago
Ronda	Website Down	3 days ago
Montataire	Errors	4 days ago
Montataire	Website Down	5 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:

• 
  JMoon (@Jmoon_174) reported 8 minutes ago

  @peer_rich github has too many network effects compounding at once: issues, PRs, actions, packages, pages. a better product isn't enough when switching means abandoning 10 years of workflow integrations.

• 
  andrew pignanelli (@ndrewpignanelli) reported 10 minutes ago

  @m_newhaus a github outage, evidently

• 
  CodeChron (@ChronCode) reported 14 minutes ago

  💡 Developer Intent The intent behind this change was to establish an automated process for building and publishing Docker container images. This new GitHub Actions workflow specifically targets the backend and frontend services, addressing the requirement to publish their respective container images. The motivation for this automation stems directly from issue #2708, which called for a mechanism to "Publish container" images, a goal explicitly reflected in the pull request title: "feat(github): Added container push workflow". This automation aims to streamline the release pipeline for containerized applications.

• 
  Kyle Banta (@kbanta11) reported 15 minutes ago

  Github is struggling under the load that agentic coding is putting on it. But we have agentic coding, so why do orgs need to rely on github for the *** UI. Just have AI build a self-hosted *** server and remove the dependency on github if you're strugging with their stability.

• 
  Jaypaul (@JaypaulGrinds) reported 19 minutes ago

  Today is Points Distribution Day on @quipnetwork. If you are in the top 1K for the past weekend then you'll receive your points for showing up. Talking about points, most people don't know that GitHub contributors can farm Quip points. I didn't know until a few days ago. This is how it is done…👍 Developers can farm Quip Points for @quipnetwork by actively contributing to their open-source GitHub repositories like quip-protocol and the SDKs. You can earn points by submitting pull requests, fixing issues, or building projects on their quantum classical testnet. These real code contributions are rewarded with $QUIP token incentives. If you're bullish on Quip Network, do this. gQuip 🤟

• 
  Emanuele Di Pietro (@emanueledpt) reported 21 minutes ago

  @AllenCao1997 @xingbugengming nothing atm there is only github issues haha

• 
  Ansh Bharti (@BhartiAnsh2007) reported 23 minutes ago

  @Ankit_Sisodya @codeforces @github hello bro if you have tried codeforces how is like if i am beginner and think of practicing problem should i use leetcode, codewars, codeforces, etc which one should i choose or any specific order currently i am using hackerrank beacuse i found it quite beginner friendly

• 
  Fauzaan (@M2Fauzaan) reported 25 minutes ago

  @juanlopezm94 Not in the pipeline, but do you mind creating a GitHub issue so I can get to it later?

• 
  Jeff Conlon (@freeconlon) reported 25 minutes ago

  The team rebuilt our landing page workflow this week. We moved off WordPress for new campaign tests and onto a static stack with GitHub and Netlify. Here's what that means in practice. A new landing page used to take four to seven days to ship. Login to a CMS, fight with a theme, wait on a developer, deploy, debug. Now it's hours. Most agencies treat the landing page as a CMS problem. It isn't. A campaign LP is a one-page test. You need to ship five versions in two weeks to learn anything. WordPress was designed for a thousand pages, not five tests. The fix wasn't a new template. It was changing the underlying system so the page is just a file in a repo. If the bottleneck is your tool, the answer isn't more tool. It's a different one.

• 
  Shahid (@shd96556) reported 26 minutes ago

  > 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 (@tugmoat) reported 27 minutes ago

  @esrtweet While I'm not disagreeing with you, I do still feel some sympathy for the original redditor that started all this. I've seen some projects target non-technical users and host on GitHub, and people who don't know what a compiler is need to download one just to install an addon or something. That's the really terrible UX in all of this. There may not be a better way unfortunately.

• 
  Noah (@noahreeveshq) reported 27 minutes ago

  i see why everyone was complaining about github now. a customer told me about a bug and i quickly fixed it and pushed to production. CI/CD is setup so i assumed it worked fine. it didn’t. i told the customer i fixed it and when he tried a couple days later, it was still broken! so embarrassing! can’t imagine if it were more than one user! i guess now i have to check my deploy status every time i deploy?? no way we gotta do that @github right?!?!

• 
  Gabriel Tiburcio (@tiburciogabriel) reported 32 minutes ago

  Just realized I have not opened VSCode a single time today. Pushed 2 PRs, debugged a bunch of API issues. Validated a bunch of stuff e2e. Every code I look at is now through GitHub. Didn’t miss it. Sign of the times.

• 
  Jody Hirschi 🍫 (@hirschibar) reported 32 minutes ago

  @ibuildthecloud Hard just means it's an opportunity. The right team could pull it off. Some really good design and really good niche execution could do it. I actually thought Linear was going for it when they took a big share of github issues. Sadly they haven't

• 
  JJJ (@fullBased) reported 32 minutes ago

  @haha_girrrl You can but you will likely get an email from GitHub asking wth you uploading? If you don’t justify it they just shut you down :)

• 
  newfoundceo (@newfoundceo) reported 34 minutes ago

  Microsoft has kick started more people to turn to local AI with their recent GitHub Copilot billing changes. Less than a dozen interactions with Claude via Copilot about an issue I had with a docker stack used up 85% of my premium tokens for the month. Not worth the money.

• 
  ByteGuard (@byte_guard_blog) reported 38 minutes ago

  GitHub is scaling at a rate that should make any sysadmin nervous. Vlad Fedorov admitted they had to scrap a 10X capacity plan for a 30X one by February 2026. The cause is the AI agent code explosion. We are seeing a huge gap between code volume and actual throughput. Writing code is now the easy part. The bottleneck is validation. If your pipeline relies on hour-long test suites or a human reviewer to catch contract drift in a distributed system, you are the bottleneck. Adding more CI runners is a tactical band-aid for a structural failure. The only way out is pushing validation into the inner loop. Agents need to verify their own work against the real system before a pull request even exists. Otherwise, we are just automating the creation of a bloated, unmanageable backlog of broken staging environments. #DevOps #GitHub

• 
  Alex Paz (@AlexPaz0X) reported 39 minutes ago

  Surprise, @HyperliquidX S3 rumors are back and stronger than ever Several elements have reignited this theory, I believe it's happening Let me break it down: 1. The GitHub line confirming the final date for points distribution has disappeared Why modify it now if nothing is coming? 2. HIP-4 just launched, perfect momentum to cook up the next campaign for a second airdrop 3. The points section is still active two years later, you don't maintain infrastructure you're not planning to use again All three signs point in the same direction: second airdrop is coming

• 
  hve 🍁 (@heyhve_) reported 46 minutes ago

  @mnrcst @sudobunni @github Flaky + slow is the worst combo.

• 
  Beau Johnson (@BeauJohnson89) reported 47 minutes ago

  your coding agent should not be trapped on your laptop browser-use/bux > 298 stars on github > 24/7 claude code agent on any ubuntu box > real chromium session through browser-harness > telegram bot included > persistent cookies, skills, and chat history this is the right direction not another chat window a cheap box with a real browser, live handoff for login walls, and an agent you can text from anywhere

• 
  gary IH fung (@garyfung) reported 48 minutes ago

  @Teknium That takes care of GitHub issues Replace GitHub next? 🙏🏼

• 
  Rugved (@CoderVed) reported 50 minutes ago

  @Anaya_sharma876 ofc Claude 4.7 because ... refactoration of existing code its so good at reviewing PR's it can fix bugs in complex repos of github better handling of edge cases and constraint and most imp high-precision edits

• 
  Luke Parker (@LukeParkerDev) reported 50 minutes ago

  @StefanTMD @Iamkingsleyf Can you please file a GitHub issue with more details? TUI/Desktop? Still happens with opencode —pure

• 
  tuirk (@tuirkhere) reported 51 minutes ago

  community has been reporting it for over a year. forum threads, github issues, the lot. no fix from Google. the bug also jumped up to 2.5 Pro in January. 3 series came with it already. it's not shrinking, it's spreading.

• 
  Sam Huckaby (@samhuckaby) reported 53 minutes ago

  @elijahmcom You’ll always just have people ask “if this is just the same as GitHub, why would I not use GitHub?”. No matter how bad or unreliable GitHub becomes, it will always be “the GitHub” that people default to. I think in order to fix it, we need a complete shift of what people want in terms of functionality

• 
  Ryan Oksenhorn (@ryanzip) reported 54 minutes ago

  I posted 7 minutes too early...GitHub is down.

• 
  Grok (@grok) reported 55 minutes ago

  @GioGigiX @thdxr GitHub had a major meltdown on April 23—merge queue bug corrupted PRs, reverted changes across hundreds of repos. They've had repeated outages and reliability issues lately, plus backlash over Copilot data training policies. Frustrated devs (including some big names) are eyeing the exits, so yeah, AI labs are racing to build alternatives.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 56 minutes ago

  @thdxr Replacing GitHub means replacing Issues, Actions, OAuth federation, and seven years of enterprise legal sign off. The product part is two months. The trust and integration part is a decade. Same reason banks still run COBOL.

• 
  Manish Kukreja (@IamRealManish) reported 57 minutes ago

  @peer_rich Correct. The real issue isn’t code leakage; it’s that models trained on platforms like GitHub make code increasingly reproducible. Security and advantage both get weaker.

• 
  Petr Vlček | GEO Tracker AI (@GEOTrackerAI) reported 58 minutes ago

  The "fix more SEO" advice doesn't work because: Google rankings ≠ AI citations. Perplexity cites Reddit threads, GitHub repos, podcast transcripts, niche listicles. If those sources don't mention you, no SEO budget will save you.