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:

• 
  Sorbifer (@Sorbifer2) reported 3 minutes ago

  @Journeywastaken @MonsoonMommy @heynavtoor I use Sunshine on Windows PC with Moonlight as a client on Macos. Never tried opposite so no idea whether whether it is a server for macos too, but check github. There or nowhere...

• 
  Yash Agarwal (@yashagl) reported 3 minutes ago

  @legionsdev @RustyRishii Students gets most of this stuff for free… like GitHub copilot. plus if it’s helping you make money then whats the issue in getting that GST registration as a student. I have GST registration, maintaining that only takes about 1-2 hr every quarter… what expenses you talking about?

• 
  Alexandre Alencar (@alexandreitpro) reported 10 minutes ago

  @ayubio @Microsoft @github this is a serious issue. You guys should reach out to your government liaison and demand an explanation.

• 
  Joe Blau (@joeblau) reported 11 minutes ago

  Fable 5 has created so many GitHub issues that my new bottleneck is my CI... I wanted to create my own runners, but guess what's all sold out...

• 
  Arpit Bhayani (@arpit_bhayani) reported 12 minutes ago

  GitHub went down for ~70 minutes yesterday. Interestingly, the root cause was not a database (the usual suspect), but an auth was returning 401s. Although outages are not good, we as engineers can learn a thing or two from them. Here's a quick dissection... So, about 15% of API traffic started getting "Unauthorized" responses for requests that were perfectly valid. The credentials were fine. But the 'infra' was lying. Here is the part that makes this interesting. Every well-behaved HTTP client reauths when it receives 401. So thousands of apps did exactly what they were supposed to do - and that made things worse. Every client getting a false 401 (root cause for 401 not mentioned yet) kicked off a token refresh, which piled more load onto an already struggling auth layer. Here is my key takeaway... When a 401 comes back, we typically reauthenticate, and we should. But if we get 10 consecutive 401s on a token that was just refreshed, reauthenticating again is not the answer. That is a circuit-breaker moment - back off, raise an alert, and stop hammering the system. Retrying blindly in an auth-failure loop could turn an incident into a full outage. So, this is something you can account for when building your next system :) Hope this helps.

• 
  boyingking (@boyingking) reported 13 minutes ago

  everyone keeps asking why $NVDA is on every "AI stock picks" list again - like it's breaking news. it's not. but here's what the headline isn't saying: "appealing valuations" is doing a lot of heavy lifting in that framing. let me lay out why I'm still long but watching levels tighter than I have in months. the multiple has compressed - that part is real. we went from the 35-40x forward P/E territory that had every value screen screaming to a range that historically attracts institutional reaccumulation. and the price action backs it: every meaningful leg down over the last two quarters found buyers before the obvious support levels cracked. that's not retail FOMO - that's structured demand absorbing supply. it tells you something about who's on the other side. but here's the part of this story I keep coming back to: MSFT is the sleeper. NVDA gets the airtime because picks-and-shovels narratives are easy to tell. chips. racks. data centers. tangible infrastructure. traders love a clean story. MSFT is messier to model - Copilot attach rates are embedded in enterprise seats, Azure AI workloads show up inside a blended revenue line, GitHub Copilot doesn't have its own P&L visible to the street. there's no clean "AI revenue: $X billion" disclosure. which means the market tends to underprice MSFT on the way up and overreact to any margin guide that even hints at AI investment headwinds. added MSFT on the last pullback. still holding from that entry. thesis unchanged. where I get cautious on both names: curated stock-pick lists are a lagging signal by construction. by the time NVDA and MSFT are sitting at the top of analyst recommendations with "exciting" in the headline lede, the fast money has been positioned for weeks - sometimes months. that's not a reason to exit. it's a reason to stop adding at market and start letting defined stops do the work. current setup I'm running on NVDA specifically: - consolidation base needs to hold the recent range - on a clean vol expansion break with confirmation, I'll scale into calls on the first leg up - not before - stop is defined. I know exactly where the thesis breaks. that number exists before the trade exists. the AI infrastructure narrative is intact. the capex cycle is real. hyperscaler spend hasn't shown a cliff. but "exciting" is not a trade - exciting with a tight stop, defined target, and a RR you can defend before entry, that's a trade. ngl, missed the absolute low on the last pullback by a couple sessions. doesn't matter. still in, adding on dips that hold structure, trimming into rips. momentum is on our side right now - just not unconditionally.

• 
  Moniruzzaman Mahadi (@m_mahadi__) reported 23 minutes ago

  @Liearmer @thsottiaux Ohh found some guy facing the same issue in github issues in the codex repo. Someone suggested to open the config.toml disable multi_agent_v2 and to add a few more line of codes. So it is a real but inside codex they should fix.

• 
  sophie (@qw3rtyqw3rty) reported 25 minutes ago

  Microsoft apparently taking the stance of not paying out a security researcher, ignoring their disclosure, banning them from GitHub, and then patching the zero days they found breaks the social contract of bug bounties, making the world less safe online and off. Researchers probably won’t use the disclosure platform any more if it’s not effective and they’ll go out online for everyone to get hacked before Microsoft can patch it. Terrible move.

• 
  Geo Anima (@geo_anima) reported 26 minutes ago

  @koltregaskes GitHub is having issues past hour or so.

• 
  新着 (@lfji) reported 27 minutes ago

  @steipete I'm doing personal development projects that I don't plan to release, but I'm wondering - is it better to create Issues in a local directory and pretend to use GitHub, or actually have people create Issues and PRs through GitHub?

• 
  Arslan Iqbal (@thearslaniqbal) reported 27 minutes ago

  @Hey_Aivetra @TencentAI_News Connecting to GitHub and Slack sounds useful. But can it actually fix a bug in my code or just organize the task?

• 
  Aseem Kishore (@akishore) reported 32 minutes ago

  The triggers: Slack messages, GitHub PR events (open/merge/push), PagerDuty incidents, Linear issues, cron schedules, and custom webhooks. Each automation runs in an isolated cloud sandbox. Changes are staged for review, never applied automatically unless you configure it. This is the first IDE feature that puts AI inside the actual DevOps loop, not just the coding session.

• 
  hue 🎨 (@huebound) reported 32 minutes ago

  sooo... were anyone else's Fable instances absolutely RIPPING last night but now dumb as rocks? like, can't connect properly to github dumb? hoping anthropic's just having another outage...

• 
  Nightcrawler (@0x_Crawler) reported 32 minutes ago

  on a test built to mimic a senior engineer, Fable 5 scored 91 out of 100, while Opus 4.8 managed 63. the reviewer spent a week with it and landed on the cleanest framing i've seen: it's a warp drive, not a city car. built for the galaxy-jumps, the months-long jobs it now does in an afternoon. useless for the short trips, where it's just slow and expensive. what he got it to do: > one prompt to read Borges and build it as a playable 3D browser game, hours on its own, first try > a conversion problem in survey data his team had missed for weeks, found in minutes > closed dead GitHub tickets and shipped working fixes for the rest, unprompted the operator setup that turns this into a daily driver, and the catch on the free window, is the breakdown to pair it with.

• 
  Elie Nahas (@NahhasElie) reported 36 minutes ago

  AI builders: stop pitching “works across any workflow.” Pick one ugly input: - vague tickets - messy invoices - sales calls - half-written GitHub issues Then turn it into one decision-ready output. Generic agents impress builders. Specific agents get bought.