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:

• 
  bestmark1 (@bestmark_one) reported 37 seconds ago

  This pattern repeats: AI setups often fail at edges—heartbeats, polling GitHub issues, error recovery—not the core models.

• 
  Péter Szilágyi (@peter_szilagyi) reported 2 minutes ago

  @josefprusa @Mojee3d @Prusa3D I have a Prusa, across the parts and kits spent probably over 2K EUR on it. The multi-material printer fails incredibly often, software issues / hangs, random overvoltage errors, ignored github issues, etc. It’s not only about hw price, support is also very lacking, unfortunately.

• 
  Erik Goins (@erikgoinsHQ) reported 3 minutes ago

  I built a financial forecasting app for our real estate business. Some take aways: 1. It's incredible what you can do with AI. This took me ~3 days part time. 2. If you're not a dev, good luck... Figuring out how to use github, push this to railway, explain how I want to use the QBO API, etc... there's still a big learning curve here. 3. Domain expertise is still very real. The first version of this was terrible. I had to help the AI create forecasting rules. 4. Businesses (enterprises) are going to need a lot of AI governance. Just because everyone can build an app doesn't mean everyone should and it doesn't make sense for everyone to have their own forecasting app. You really want one well done app, not 100 bad ones. 5. We're not replacing QBO. Too ingrained- it gets to stay the system of record. Looks like there's still a very real moat for the right SaaS products. Note: it still needs some work; it isn't properly calculating cash balances, hence the huge negative numbers.

• 
  Sean Keenan (@sean9keenan) reported 4 minutes ago

  @brian_lovin Semi-relatedly: I’m back to VS Code from Cursor, autocomplete seems much better now! (Not that I’m crafting code by hand much) But importantly, the… basics seem much more stable (Cmd+f, and saving have been pretty broken in Cursor recently) Curious how GitHub Copilot feels!

• 
  Yashwant Vijayakumar (@V_Yashwant) reported 4 minutes ago

  @svembu Sridhar ji @svembu I recently started paying 40$ a month for Github copilot in order to avail Claude Opus 4.7, a huge step up from Sonnet 4.6 which was underperforming for my coding tasks. With Opus 4.7, now I'm having to understand how it solved my problems than the other way around. My point here is that as we are debating whether it understands the world sufficiently or not, the models are steadily improving their depth. I used think of Claude models like Forrest Gump, quick to react but superficial. These days I feel like I'm Forrest. With due to respect to @fchollet , let me tell you he also may not be able to keep up with the pace of "recursive self improvement" happening now with every new release. Let's not peddle narratives of somebody else, even if he's an expert in the domain.

• 
  ᛗᚨᚱᚴᚢᛋ (@guitaripod) reported 5 minutes ago

  @piq9117 GitHub down? i don't believe you. IT'S IMPOSSIBLE!!😭😭 (luke skywalker reaction)

• 
  DeBros (@DeBrosOfficial) reported 10 minutes ago

  The Problem We’re Solving🫡 Your organization’s brain lives in 12 different places — and none of them talk to each other. Decisions get buried in Telegram threads. Context is split between GitHub and AnChat. Important knowledge disappears within hours. Onboarding becomes tribal knowledge all over again. 🤖AnBuddy fixes this by becoming the single source of truth for your entire team.

• 
  Kamil Skowron (@kamilskowron) reported 11 minutes ago

  @donutkiller_pro If you could - always confirm with the current main branch. If the issues show up on that branch - it would be best if you could dump the generated report into GitHub issues please 🙏🏻

• 
  Alex Derocq (@akaasten) reported 15 minutes ago

  @steipete Crazy how the GitHub "@codex review this" feature is way better than the local review. It spots more issues like 90% of the time.

• 
  Ashish Ranjan (@Ashish_050488) reported 17 minutes ago

  build on laptop (3 secs), upload only the dist folder. 500kb. server just serves files now, doesn’t build anything. deploy went from 15 mins to 5 secs. turns out big companies do this exact thing, just automated. github actions next so i never think about

• 
  AtomicNodes (@AtomicNodes) reported 19 minutes ago

  Hermes Agent vs OpenClaw on Local Qwen 3.6 35B We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb. OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Kris (@RetroRebellion) reported 20 minutes ago

  @VGMHero It really would be a small fix, github nerds got us though lol

• 
  Benitto J D (@BenittoJD) reported 21 minutes ago

  Github actions are down again

• 
  Roj Niyogi (@niyogi) reported 25 minutes ago

  @colinhacks @pullfrogai @Pullfrog so for 90% of folks who are using cursor/windsurf/github copilot/claude code via an IDE "chatting" with their agent, the answer is just to tell your agent to fix everything? i've used both coderabbit and greptile extensively and here's what happens: 1. 20% of what is found is false (and likely even more variable if you pick a model) 2. i cherry pick issues and paste in editor to handle 3. code review is rarely "happy" and you can end up in a loop state that burns tokens bummer that you've got the flexibility on the one end but have a strong opinion on the other for what seems to be an obvious opportunity to close the loop for, i'd guess, a chunky subset of users

• 
  Rinnegatamante (@Rinnegatamante) reported 26 minutes ago

  @dgosiq Did you grab the update from GitHub? I think it might be a broken version (updating it right now there as well). If you have a psp_apps.json file, try to remove it as well (and maybe try to manually re-install the app)