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:

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 5 minutes ago

  Is it just me or github and brew are ultra slow? 🤔

• 
  Lucky Luciano Polkadot (@KingTofCrypto) reported 7 minutes ago

  🚨The #Polkadot narrative is officially shifting to Positive! and anyone sitting on the sidelines is about to get left behind. For months the crowd slept on the relentless developer activity and the massive backend upgrades, but the market sentiment is finally flipping hard into the green. The data doesn’t lie, the massive spike in social media buzz and explosive social sentiment tracking across CoinMarketCap AI Analysis proves that the crypto community is waking up to what is happening here. We are talking about a complete overhaul that slashed staking unbonding times from nearly a month down to just two days, killed off slashing risks for everyday stakers, and systematically choked token inflation by enacting a hard supply cap of 2.1 billion $DOT. The smart money is noticing the sheer volume of code hitting GitHub—ranking #Polkadot number one in total developer commit activity and the sudden explosion in online momentum. This isn't a temporary pump, it is the calculated awakening of a sleeping giant that is primed to melt faces. If you aren't loaded up on $DOT before this train leaves the station, you simply aren't paying attention. 💯

• 
  Nitesh (@NiteshTechAI) reported 7 minutes ago

  OpenCut is building a free, open-source video editor that runs in the browser, on desktop, and on mobile. No subscription. No watermark on work you made yourself. • Free and open source, on web, desktop, and mobile • New version built on a single Rust core across platforms • Plugin-first design with real third-party plugins • MCP server so AI agents can drive the editor • Headless mode for batch rendering and automation It is a real answer to the closed editors, and the rebuild adds an editor API and a scripting tab, so you can automate edits instead of clicking every single cut. ⭐ Over 75,000 stars on GitHub. MIT licensed. 🔗 GitHub link in the comments 👇

• 
  Olaoluwa Ajibade (@ajibadde) reported 11 minutes ago

  🪝 Webhooks This one isn't for users. It's for servers. A webhook is simply one server making an HTTP request to another server when something happens. Examples: • Stripe tells your backend a payment succeeded. • GitHub tells your backend a push happened. • Paystack notifies your app about a completed transaction. Your server receives the event and decides what to do next. Think of webhooks as service-to-service notifications. One system says: "Something happened. Here's the data."

• 
  hammi (@hammi_ip) reported 12 minutes ago

  @Farhan776777 @github The Problem with Skills That's why almost never

• 
  Saeed Anwar (@saen_dev) reported 12 minutes ago

  The reason AI-generated sites look like slop isn't the model, it's the default CSS every LLM reaches for. One component library with 75K GitHub stars fixes a problem that better prompting never will.

• 
  Boy Pro. (@ether_45) reported 12 minutes ago

  OpenAI just announced its next major model, Astra, and buried the announcement inside a math paper. The model is called Astra. An internal version solved ten open problems across mathematics and theoretical computer science, each of them unsolved for at least a decade. Total compute cost: approximately $2,000 at current Sol API rates. Every proof was published on GitHub with machine-checkable Lean 4 certificates. No unverified steps across all ten solutions. Astra is not publicly available yet. No release date has been given too. No hype needed here. The facts speak for themselves.

• 
  Myles Marino (@mylesmarino) reported 17 minutes ago

  The correct way to use AI is increasingly looking like an onboarding checklist. Like adding a new remote drop-in teammate. Most people are still using AI like a search engine: 1. Ask question 2. Get an answer 3. Start from scratch again That's close to being a thought partner. Or if you are a bit more advanced, an assistant. Useful, reactive. Mostly a good way to save ten minutes. But treating these tools as teammates has been a critical unlock for us the past few months. You would normally give new hires: - a laptop - ticketing system logins - Slack handle - scoped credit card Even if they didn't need it all day one. But withholding critical systems means they are more "contractors" than they are drop-in remote workers. Do the same for AI: GitHub, Jira, Slack, Mercury, internal docs, the whole 9. Treat this like a new hire who happens to be forgetful. Write down everything and make a reference guide. Have scheduled reviews, so you can provide feedback and continuously improve.

• 
  RelativelySmart (@DumbEinstein) reported 19 minutes ago

  Genspark open sourced GenOffice. A full local AI-native office suite for macOS and Windows. • Docs, Sheets, Slides, PDF with familiar editing surfaces • Built in Super Agent that researches, analyzes data, drafts, and iterates inside the document • Free, add free, no watermarks; AI features consume Genspark credits • Full source on GitHub One engineer, one week, ~$10 k in tokens The interesting architectural choice is the two-layer design: AI generates structured content, then a deterministic conversion engine produces clean .docx .xlsx & .pptx. files This avoids the usual "Markdown that falls apart when you open it in Word” problem. Worth testing if you want an agentic office that actually stays local. Link to the Github repo below

• 
  Justin Searls (@searls) reported 19 minutes ago

  I joked last year that by leveraging coding agents I now "played the orchestra", by directing multiple programmers at once. I have changed jobs again. Now I tell Fable to conduct an orchestra of Opus 5 agents for me. It's closed 55 GitHub issues in 6 hours across my iOS apps.

• 
  Camilo Sacanamboy (@camilosaka) reported 26 minutes ago

  POAP has always resonated with me because I’ve spent almost 10 years building in the events industry. I’ve issued millions of tickets with Peewah, and today, with HashProof, we’ve issued 12,000+ verifiable attendance certificates onchain in five months. But I always felt POAP was missing something. I heard many people say they loved collecting POAPs. I heard far fewer say they truly needed them. In events, sometimes even a PDF certificate is enough. What organizations usually need is something tied to a person’s identity: their name, attendance record, verification, and often integration with the rest of their operation. The collectible itself often felt more like a nice-to-have than a painful problem being solved. That doesn’t take away from what POAP achieved. They attracted millions of users, worked with major organizations, built a beautiful product, and created one of the most recognizable brands in crypto. But engagement, love for a product, and even a strong brand do not automatically create a sustainable business. From the outside, it seems they were unable to make the business sustainable before the funding ran out or before securing more capital. Crypto cycles, speculation, and changing technology may have made things harder, but they are not the fundamental issue. It is okay to acknowledge that. This also connects to a mistake many builders, including myself, have made: falling in love with the technology and building solutions in search of problems. I spent years going from hackathon to hackathon, winning prizes, accumulating dozens of dead GitHub repositories, and ending up with almost no users. I think we are finally starting to see blockchain for what it is: just another technology whose purpose is to solve real problems. I also disagree that longevity and brand equity are the only moats left. Those are valuable, but the strongest moats will still belong to the teams that understand customer problems most deeply and build the best distribution. Huge respect to the POAP team for what they built. The product was beautiful, the brand was loved, and I’m sure the team will go on to build great things.

• 
  Fatah (@ahmedafatah) reported 27 minutes ago

  @HendrixLiu29208 one deployed side project that solves a real problem does more work for you than 20 polished github repos nobody runs. employers want proof of shipping, not proof of writing.

• 
  Daniel Ospina (@_Daniel_Ospina) reported 28 minutes ago

  I filed the issue in your github

• 
  Chubigans (@metatransformr) reported 29 minutes ago

  Just ran my first fully autonomous overnight build for my complex Godot RPG with Codex. I used a dispatcher that maintains a concurrency of N=2 (can tune it up as tokens permit) substantial spec-driven tasks at a time. Uses an automated playtesting API to prove the tasks are done. It's easy to make a simple game, it's really hard to make a complex game (mine is Mount & Blade + Wizards) Not everything can be done in an automated way, not even close. But a lot of systems-y tasks, bugfixes and cleanups *can* be done, or at least prototyped relatively autonomously. The workflow is: nightshift runs the backlog off my github project, I wake up and review everything, playtest the build, record bugs and plan out the development for the day. This is spec-driven development for games, and it's definitely the future. The bottleneck is graphics/animation/gamefeel/juice and such. There are so many problems that can't be currently done in an autonomous way, without wasting tokens. This is the "research problem" I (and other AI game engine startups that are vc-backed) am working on. A fascinating field.

• 
  kache (@yacineMTB) reported 31 minutes ago

  check out my github for an opencode plugin that repeatedly hammers the opencode deepseek api across 5 different subprocesses in parallel until you get past the annoying 503 errors!