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:

• 
  Jack Vinijtrongjit (@juminoz) reported 3 minutes ago

  Is it just me or @github is down again? Can't login at all. Can't even go to any public GitHub repo either.

• 
  Desmond Abiola (@desmondabiola_) reported 4 minutes ago

  Follow up from last week's DNS/networking post. This week I moved one layer up the stack: Nginx HTTPS with an internal CA, followed by a reverse proxy in front of a Python backend. I hit two different certificate errors before HTTPS worked: one involving trust, another involving the certificate identity and a missing SAN. Fixed both and verified the result with OpenSSL and curl. Then I got a 502 from the reverse proxy. Nginx wasn't broken. The backend simply wasn't running. Same lesson across three labs: don't trust the first symptom. Trace the request path, test each component independently, and use evidence to find the failure. Full writeup on GitHub, link in reply. #Linux #Nginx #SysAdmin

• 
  Tino Wening (@TinoWening) reported 6 minutes ago

  @Howaboua I’m pretty cautious when it comes to relying on third-party cloud systems. Think of GitHub, AWS, and CloudFlare outages. What happens if there’s an outage right when you’re in the zone? I think a local backup system makes sense if you don’t have much trust in third-party providers. It’s always a balance between dependence and self-maintenance. With the latter, you’re in control and can decide what happens, when, and how.

• 
  Lain on the Blockchain (@CryptoCyberia) reported 8 minutes ago

  @EmperorBag @F_A_T_W_ I think it makes a lot of sense to use github as a metric. my issue is that when you use use of experience as a metric, you isolate so many insanely good cracked young devs.

• 
  Chris 👽 (@VeryBullishGuy) reported 9 minutes ago

  @namespacelabs this is one of the smartest capex calls in infra right now and its not even close. apples license only lets macOS run on apple hardware, and only two VMs per machine. thats not a policy on a pdf somewhere, its enforced in code. try to boot a third one and the framework just errors out. so if you want to sell iOS CI you have to physically own the metal. no way around it. thats why AWS has to lock a dedicated host for a 24 hour minimum just to stay compliant, which is completely useless for a 6 minute build. and its why github charges about 10x for a mac minute vs linux, 6 cents against half a cent. that spread IS the business. apple killed the mac pro in march and has no server product at all now. so custom shelves full of consumer hardware is the only play anyone has. this isnt an unboxing video, its a barrier to entry.

• 
  Megz 📚 (@DeltaXtc) reported 12 minutes ago

  Lmao CT are so slow It's a joke and the GitHub is authentic Change bitcoin to fabcoin

• 
  Shawn McAllister (@eas4ai) reported 13 minutes ago

  @Griveau @karrisaarinen @linear This is not hyperbole... I missed an email - via issues on github - about my Rust MCP SDK (mcp-daemon) becoming the official Rust SDK from Anthropic and I missed it by 3 months because I had subscribed to the Cline issues feed somehow and missed it in all of the chatter. I released it in Feb 2025. I was ok with it though. I made the MCP SDK for my own use primarily and did not want to be tied to it like that.

• 
  Keshav Sharma (@BasedDesiMan) reported 14 minutes ago

  GitHub actions are down again… At this point they should just call it quits .

• 
  Matt (@acidgambit_) reported 19 minutes ago

  there's no way github actions are down again rn

• 
  ponta_kokemomo (@ponta_kokemomo) reported 23 minutes ago

  A Ledger vulnerability was making the rounds on CT today, but according to Ledger’s CTO, the issue has already been fixed. As long as your firmware and apps are up to date, you should be fine. You can’t completely avoid zero-day risks, but in general, applying security patches and keeping your software updated is still the safest approach. Dev tools you pick up from GitHub are a different story, though. The latest version isn’t always the safest lol

• 
  Jamie Stevens (@BodhiBlues0) reported 24 minutes ago

  @dhh I'm running it on my 2021 M1 Pro at the moment. It is mostly good. The biggest issue I had was Wifi breaking after sleep, I managed to fix that in a hacky way though and posted my solution to the omarchy-mac github. Battery life also drains at about 2-3% per hour in sleep.

• 
  Raven (@heyraven_io) reported 31 minutes ago

  @kimmonismus the model has been out for seven minutes and the github issue is already open

• 
  archv.ai (@archv_ai) reported 31 minutes ago

  GitHub was down for seven hours and 47 minutes. Its 20 August postmortem puts the cause at capacity rather than a code or configuration change. GitHub says it has since added more than three million CPU cores. What breaks in your stack when GitHub does?

• 
  Vibranium Audits (@VibraniumAudits) reported 32 minutes ago

  What a real audit gets you: A named senior team reading your code line by line. No junior queue. Every finding with a fix. Reports public on GitHub. 480+ audits, zero exploits on secured code. Security isn't a PDF.

• 
  Lee Packham (@Joolz) reported 34 minutes ago

  You just know the current @github outage is bad when they clearly hand-wrote that latest status update about Vitess. /cc @QuinnyPig