GitHub 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:

• 
  Pavan Joshi (@PavanJ1620) reported 9 minutes ago

  If you want to start a startup: 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) ProductBridge = feedback (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

• 
  Dmonty (@Dmonty28516998) reported 13 minutes ago

  @udohjeremiah_ @kirtandopamine Microsoft. Microsoft’s resources aren’t struggling. GitHub is struggling to use them. GitHub itself says it’s still migrating critical infrastructure out of its own datacenters and into Azure. One of the recent Actions outages was made worse because a core service was still running in GitHub’s datacenter with insufficient capacity. Their stated fix is literally: move it to Azure for more headroom. They’ve spent this year writing postmortems about shared dependencies, old databases, insufficient isolation, architectural bottlenecks and operational failures while they rearchitect the platform. Meanwhile Microsoft never even replaced GitHub’s CEO after he left; GitHub was folded directly into CoreAI. Ironically, a ton of the agent traffic is from OpenAI, being served primarily from Azure, so it's incredibly clear that MSFT infra is not the issue lol.

• 
  Mykyta Pavlenko (@mktpavlenko) reported 14 minutes ago

  your .env file is on GitHub right now your API keys are in your frontend code the agent wrote them inline and you shipped without checking first thing to fix. today.

• 
  Amandeep Singh (@Amandee24524309) reported 17 minutes ago

  @acolombiadev @grok summarise the cause why GitHub was down

• 
  Dmonty (@Dmonty28516998) reported 19 minutes ago

  @kirtandopamine @MarcosHernanz Microsoft’s resources aren’t struggling. GitHub is struggling to use them. GitHub itself says it’s still migrating critical infrastructure out of its own datacenters and into Azure. One of the recent Actions outages was made worse because a core service was still running in GitHub’s datacenter with insufficient capacity. Their stated fix is literally: move it to Azure for more headroom. They’ve spent this year writing postmortems about shared dependencies, old databases, insufficient isolation, architectural bottlenecks and operational failures while they rearchitect the platform. Meanwhile Microsoft never even replaced GitHub’s CEO after he left; GitHub was folded directly into CoreAI. Ironically, a ton of the agent traffic is from OpenAI, being served primarily from Azure, so it's incredibly clear that MSFT infra is not the issue lol.

• 
  NULL (@nulldevpi) reported 21 minutes ago

  cursor (now spacex) shipped origin. github, but for the ai editor people. same day github ate itself for 6+ hours. ~20% errors on prs and the api. you do not get to write a joke this clean. reality already did. origin syncs your github repos. you don't have to leave. it's the "stay, i just got another apartment" of *** hosts.

• 
  aniketh (@Aniketh_Deb) reported 25 minutes ago

  >this is exactly why we need ******* good engineers. >everyone talks about ai like it can “one-shot” engineering, then a production system like github goes down because an istio sidecar hits a concurrency limit, autoscaling fails due to a policy mismatch, ha proxies exhaust flow limits, retries amplify the failure, and one internal endpoint starts a 10x traffic amplification loop. this isn't “write some code” engineering. >this is distributed systems, capacity planning, failure isolation, backpressure, retry semantics, service meshes, load balancing, observability, and understanding how one small failure can cascade across an entire dependency graph. >and look at the copilot token service: normal traffic was ~7–9k rps. during the retry storm it exploded to ~70–100k rps. ai didn't magically prevent that. >because production engineering isn't about generating a function that compiles. it's about knowing what happens when millions of requests hit the system, one dependency becomes slow, clients retry, gateways retry those retries, autoscaling makes the wrong decision, and suddenly your “redundant” infrastructure becomes the amplifier. this is also why top engineers getting $200k+ compensation isn't crazy. you're not paying someone $200k to write crud endpoints. you're paying for someone who can look at a cascading failure at 3am and understand why the entire ******* system is falling over. ai is going to make engineers dramatically more productive. but “ai can code” and “ai can operate a planet-scale distributed system safely” are two completely different claims. the future isn't engineers vs ai. it's insanely good engineers using ai while understanding the systems deeply enough to know when the generated answer is ******* wrong.

• 
  Atul Mishra (@The_AtulMishra) reported 25 minutes ago

  @TheSpacerr That's a terrible idea, people will end up many community *** workplaces instead of Github. Also bitbucket probably will be waiting for this oppurtunity

• 
  Stuart Carr (@Stuey3D) reported 26 minutes ago

  @AjithN628302 @rtlsdrblog You don’t need one, just download the APK from GitHub and it will work. You will have to enable Unknown Sources to install but I am registered with Google so you should have no issues installing it.

• 
  Apollo (@ApollonVisual) reported 28 minutes ago

  Cursor launches Origin to rival GitHub Cursor launched Origin a new code-hosting platform to rival GitHub. GitHub suffered a six-hour worldwide outage on the same day as Origin's launch. The outage featured a nearly 20% error rate worldwide. GitHub has had 257 outages in the past year according to LeadDev. GitHub reports 180 million developers as of last October. Origin is designed to work alongside GitHub interoperably. Cursor is now part of SpaceX. Cursor's primary focus until now was its AI Code Editor.

• 
  Kaan (@kaanyagci) reported 28 minutes ago

  Many people's reactions to the GitHub outage tell you a lot about why you shouldn't make your service free. Free customers are the most painful ones

• 
  Alexander Talavera Karslake (@AlexTKarslake) reported 30 minutes ago

  @EngineerIDE @acolombiadev LOL, I have so many repos on github though... I think almost 50. Some public goodies too, like the absolute best screenshot app for Mac (OSS). I don't want to move away, but the other day I was genuinely blocked for hours regarding a deployment. If I need to fix a critical bug...

• 
  Bob (@skytaleSythe) reported 31 minutes ago

  @DecryptedTech 🤔 Interesting - I have GitHub Agents set up to scan all check ins for defects and it’s found legit issues. For instance some regex in a shell script that would cause it to fail on certain types of processor. We have it set to scan and report only - dev has to decide how to fix it. So far it hasn’t made any suggestions that would make the code less secure (fingers crossed).

• 
  Ram (@ram_krish2000) reported 31 minutes ago

  We won the Vana Cup. 43 apps, 4,707 points, first place. Massive thanks to @vana and the whole team. Vana handed someone like me the same starting line as everyone else, and that is rarer than it should be. Why I built on Vana in the first place? "Data is the fuel. Not models, not compute." Every AI product that matters is downstream of what it knows about you, and right now that data sits locked inside five companies who will never hand it over. I could not have built Patina on any single platform's API. The whole idea needs to look across someone's accounts at once, and normally that means five partnership conversations I would never get. Vana flips it. The user brings their own data. No permission needed. What Patina does? It reads how far back your accounts actually go, YouTube, GitHub, Instagram, LinkedIn, Spotify, and turns it into a signed score anyone can verify offline. No ID, no face scan, no documents. To be precise about what that means: Patina proves tenure, not personhood. It does not tell you someone is a unique human. It tells you nobody could have manufactured this history last Tuesday. Why that matters more every month? Bots are now 53% of internet traffic. Humans are 47% and falling. AI agent traffic grew 7,851% this year. Fake account creation is up 259% then another 89% on top. Every existing trust signal can be bought. Followers, activity, a filled-in profile, all of it is for sale. The one thing nobody can buy is a decade. Age is the only signal that gets harder to fake as AI gets better, because time is the one input that cannot be generated. The roadmap: 1. Tenure for AI agents. The MCP server is already live, so an agent can ask how far back a person goes mid-conversation, no key, no OAuth. The IETF and FIDO are writing the agent trust standards right now. Tenure belongs in them. 2. Become infrastructure, not a destination. A verify API, an embeddable badge and signed attestations already exist. The goal is other products gating on tenure the way they gate on a captcha. Airdrops and allowlists first, because that is where the pain is sharpest. 3. More of the world readable. More sources, better mobile. A score is only fair if the accounts you actually have can produce one. 4. Portable onchain reputation. Your tenure should travel with you across apps and chains without Patina sitting in the middle. If Patina disappears, the proof should still work. So: if you care about this problem, I would like to talk. Users who want a score, builders who want to plug tenure in, and especially anyone who has done the founder part before and remembers what it was like at the start.

• 
  Aymane (@aymanemsi) reported 32 minutes ago

  @Its_Nova1012 Github is down Let's build our own