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 (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	11 days ago
Tlalpan	Sign in	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 days ago
Gustavo Adolfo Madero	Website Down	23 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:

• 
  Nic Watson (@jnwatson) reported 24 seconds ago

  My Gemini morning review informed me of a crash reported on one of my projects. On a plane, on my phone, had Claude Code investigate. Arch specific. I don't have one. No problem, GitHub Actions does. Upstream bug? glibc bug?! Newp. I'm holding it wrong. PR is ready before I land.

• 
  AI Theory (@AItheoryx) reported 30 seconds ago

  Microsoft is building a super app that combines all of its Copilot tools into one place. GitHub Copilot. Copilot chat. Copilot Cowork. And a new agentic workflow tool internally called Autopilot. One interface. One destination. One login. The internal slogan is Delivering one Copilot. Here is why this is happening and why it matters. Less than 4.5% of Microsoft 365's 450 million customers pay for Copilot features. That is one of the worst conversion rates for a major enterprise AI product. The reason according to sources is simple. Customers hate switching between different Copilot tools. The fragmentation is costing Microsoft money. GitHub Copilot has 4.7 million paid subscribers at $10 a month minimum. But it is losing ground fast to Cursor and Claude Code. Microsoft's consumer Copilot chatbot is significantly behind ChatGPT and Gemini in active users. Microsoft was the first major tech company to make a serious AI bet. $13 billion into OpenAI in 2023. They had a two year head start on almost everyone. They spent that head start launching multiple versions of Copilot that confused customers, splitting their teams between consumer and enterprise, and relying heavily on OpenAI models while competitors built their own. The super app is the attempt to fix all of that in one move. Launch is targeted for end of summer 2026. Some elements may surface at Microsoft Build next week in San Francisco. The app itself will not be shown yet. Satya Nadella promoted Jacob Andreou in March specifically to unify the Copilot product line. This super app is Andreou's primary assignment. Microsoft still has 450 million Microsoft 365 customers. If the super app moves conversion from 4.5% to even 10% that is tens of billions in new recurring revenue. The lead is gone. The distribution is not.

• 
  Greg (Autism Mode) (@greg5figs5inch) reported 2 minutes ago

  @_machi47 So it can interact directly with GitHub and all that with no problem. But since I "rawdog" it on the VPS I dont even need a github repo

• 
  Kephen Rai (@kephen20936) reported 3 minutes ago

  Phase Building a Windows Vibe-Coded EXE SITREP: "I’m going to rebuild the Phase 1 repo package into a safer Windows-compatible baseline instead of patching line-by-line. The new version will keep the GitHub Actions compile flow, remove the template/math compile issue, and use a simpler native Win32 UI that matches the player/EQ/playlist direction from your screenshot without installing anything or touching system settings." - OpenAI ChatGPT 5.5-Extended Thinking It's a lot longer than building webpages, and as usual as it was 26-years ago or so, the compiler errors are frustrating as I remember, only this time, AI is fixing things. Going to see what a Rebuild of the prior broken app I pictured previously of the broken app that was a "I want this" and ChatGPT says, "Okay..." [Beep-beep-boop], "I've completed... here's your app."

• 
  Deus (@deuslexic) reported 5 minutes ago

  Does anyone solve the issue with AI agents coordination in the same chat group? I did a lot of tinkering, but coordinating multiple agents remains hard. Any good articles or GitHub repos?

• 
  rohan (@rohandevs) reported 5 minutes ago

  overheard in sf: is the wifi cooked or is github down?

• 
  Aries Spring (@AriesSpring__) reported 6 minutes ago

  @nicklaunches @launch_llama Github auth not working, when authing with x, it gets stuck in a loop of email verification -> sends you code on email -> you submit -> you get that prompt to verify email again -> repeat

• 
  Dave Barnwell (@dave_barnwell_) reported 7 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  Zr1Trader (@ZR1Trader) reported 17 minutes ago

  @jhansman @MisterCommodity I had some issues with it loading the other day, sometimes it'll do that intermittently. Some of the cloud servers were offline or something when I went and read on the github page. It's mostly worked great 99% the time for me though.

• 
  Devesh Shukla (@Devesh143) reported 18 minutes ago

  @kimmonismus A "super app" won't solve a product-market fit problem. Microsoft keeps building interfaces when they should be building utility. You don't fix a 4.5% adoption rate by adding another layer of UI bloat — you fix it by making the AI actually do the work. Even GitHub Copilot is losing its edge because Cursor and Claude Code prioritize the EXPERIENCE over the ecosystem. 20 million users isn't a success story for a company with half a billion seats. It is the Clippy era all over again, just with a larger GPU budget.

• 
  Deepak (@triorDeep) reported 19 minutes ago

  Most junior devs don't get hired because of skills. They don't get hired because of how they present skills Your GitHub README is your first interview Your commit messages are your communication style Your project descriptions are your pitch Fix these before applying anywhere

• 
  Matt Cowley (@MattIPv4) reported 20 minutes ago

  @danielhayesmith @dok2001 Cloudflare have confirmed in the GitHub issue that it is a legitimate dependency. However, not sure they’ve fully understood the risk is still there as this employee could later use this as a backdrop by publishing a new version, say if they were to be laid off…

• 
  vish (@vishctx) reported 20 minutes ago

  @OfirPress There’s a massive blind spot in the benchmarks. By the time an issue makes it to GitHub with a reproducible state, 80% of the hardest engineering work is already done. Current benchmarks hand models extremely precise problem statements. But in the real world, like when debugging the Linux kernel, you rarely start knowing what the problem actually is. All a user will report is “the app is OOMing, and increasing memory doesn’t help.” Digging into that requires intuition built from past issues. The root cause could be memory leaks, memory fragmentation, or a race condition where threads acquire memory and never release it leading to starvation. We desperately need benchmarks with highly ambiguous starting conditions to test if a model can navigate a state with multiple distinct root-cause scenarios. Right now, models like Opus easily get stuck in loops during open ended investigations. They rarely move forward unless I ask it to check for hypotheses A, B, or C. The next frontier for SWE evals should also include cases where the model is trying to figure out what's actually broken in the first place.

• 
  Nirav Parekh (@Niravsays_) reported 23 minutes ago

  1/ I just published ContextSchema on GitHub. It’s a small Python framework for one of the most under-discussed problems in production AI. Beyond the typical pitfalls; agents fail often because they act on context that is stale, incomplete, or weakly sourced.

• 
  Gitforge (@GitForge_io) reported 25 minutes ago

  GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

• 
  Chaitanya Shetty | Tech Partner For Your Products (@thechaicoder) reported 26 minutes ago

  TLDR -> Plan with Opus + MoSCoW -> Skip slow design loops, build in Lovable -> Build 70-80% there, then move deeper work to Cursor -> Run security scans before GitHub sync -> Connect tools via MCP (especially Supabase) -> Use Supabase for backend + auth + realtime -> Run AI review + launch checklist -> Deploy on Vercel -> Outcome: faster Product validation on lean budget This is how we ship 50+ Products. Build smarter. Build faster. Stay structured.

• 
  Dave Augustus (@davetweetlive) reported 27 minutes ago

  Yesterday, I found that an organisation was trying to gather information about me using OSINT. They tracked down everything, from my GitHub to my Instagram as well as every single place I have ever visited.

• 
  geekopedia (@geekopediax) reported 28 minutes ago

  @DenisKursakov That 3.3% conversion proves forced bundling cannot fake organic demand. Microsoft's paid AI market share slid 39% in six months. Ironically, GitHub Copilot still holds 42% of the dev market. Splintering apps is a loss; they must fix core utility before churn accelerates.

• 
  Hasif (@hasifdev) reported 35 minutes ago

  @github China is going down!???

• 
  Ned Malki (@ned_malki) reported 35 minutes ago

  @YaronElharar @thsottiaux nice. try submitting an issue on GitHub. Just tell the agent to do it

• 
  Naija Street CTO (@iamowiin) reported 35 minutes ago

  @EmanAbio How e dey possible @SuiCommunity report say “we’re back” to a so called decentralized network @SuiNetwork as if na one of those “Google”, “GitHub” centralized servers wey get outage 🤔 I think SUI blockchain na various nodes Abeg make person explain? I dey miss something?

• 
  Matthew Anorkplim Loh (@iam_multiman) reported 36 minutes ago

  You no longer need to login to github to use github copilot

• 
  LeetLLM.com (@leetllm) reported 44 minutes ago

  the official github MCP server burns 42,000 tokens per turn just loading its tool definitions. a 20-turn session pays that tax 20 times. sending 50 JSON schemas back and forth on every chat message isn't an architecture. it's a ddos attack on your api bill.

• 
  Devesh Shukla (@Devesh143) reported 45 minutes ago

  @DenisKursakov Microsoft is burying their one good product under a mountain of legacy bloat. The "one Copilot" slogan is pure cope. You can't fix a 4.5% adoption rate by adding more apps—you fix it by making the product invisible. GitHub Copilot is getting liquidated by Cursor and Claude Code because they focus on THE FLOW, not the brand. Developers don't want a separate assistant; they want their environment to think. Microsoft didn't build a system. They built a distraction.

• 
  Ethan (@DuoEthan) reported 46 minutes ago

  The interview process we have wasn't designed to find good engineers. It was designed for when you couldn't watch someone work in real time. We can now. GitHub history, open-source contributions, a 20-minute live session with a real problem. The companies still running five-round loops at Fortune 500 pace aren't being rigorous. They're just slow.

• 
  Blessed_Patriot_2011 (@jwm_anacortes) reported 48 minutes ago

  @github my account is getting 404 errors on all my repositories on both web and ***. Support (ticket number 4402135) closed my ticket saying there are no restrictions but nothing has been resolved. PLEASE escalate!

• 
  Adam (@adam_narozniak) reported 55 minutes ago

  @OpenAIDevs Quite useless since you still allow access to only 50 most recent chats. Older ones dissapear from the sidebar and you can't open them even if they are found using this new search :( there're quite a few issues on Github reporting it

• 
  Zachary Kurtz (@ledflyd) reported 56 minutes ago

  @lukasweidener I guess I can close my issue on github then 🙏

• 
  Büke Beyond (@BukeBeyond) reported 59 minutes ago

  @Skirge01 @exQUIZitely read your own article: "GitHub Open Source Survey ~95%~3%" Male Female, "1% non-binary, 1% unreported" that is down to 1% sampling noise. If all your fantasies are true: there should be clear evidence in github.

• 
  Tosin Olugbenga (@TosinOlugbenga) reported 60 minutes ago

  I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS. We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server. So we changed the model: Build on GitHub Actions → push to GHCR → Dokploy pulls and runs. No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds. What changed: → Server = run containers, not compile code → Same image from staging (:release) to **** (:production) → Rollbacks = pull a previous tag → Freed ~10GB from old BuildKit cache alone Same app. Cleaner ops. If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.