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:

• 
  Ed Grosvenor (@MaybeEdward) reported 2 minutes ago

  @tomschlick @DCoulbourne Just a cron job that uses the Solo MCP to determine whether I'm actively working and, if not, will do things like look for GitHub issues, exceptions, slow queries, etc. to chew through. Very hacked together WIP stuff at the moment, but I have big plans for it.

• 
  enp2s3 (@enp2s3) reported 3 minutes ago

  Free is not actually free. Here’s the Brave slop from my perspective. Popups everywhere, useless side features constantly jumping in your face like the browser is trying to force you to use them. When you first install Brave, if all you want is a better browser, you have to turn off dozens of settings and features first. Brave Ads, Brave News, Brave Rewards, yeah, earn rewards, because apparently we’re playing a ******* game here instead of looking for a browser, Brave AI Chat, Brave Talk… It genuinely starts feeling like one of the market's spam-filled products. Anyway, after turning all that crap off and getting through the initial setup chaos, you finally think you can relax. But you can’t. Brave looks good, the UI is solid, almost Opera-like hype, and it comes wrapped in all those big privacy-focused slogans. But after actually using it for a while, the whole thing starts turning into clickbait. A lot of Brave settings are disabled by default or set to ask every time, so on popular websites and across the modern web, instead of making your browser experience easier, it keeps costing you extra time. Still, you don’t quit Brave. You spend months fixing settings site by site, changing permissions, adjusting preferences, until you finally reach the comfortable browser experience you should’ve had from the beginning. Then not even 3 or 4 months later, another surprise. After a few browser version updates, basic usage starts falling apart with lag, freezing, stuttering and random slowdowns, gpu acceleration issues. At that point, the whole Brave experience basically becomes this: 1) Use Brave for a while. Spend a few months improving your settings and site preferences until you finally reach the normal browser experience you were supposed to have in the first place. 2) Just when everything finally starts working properly, one of Brave’s chronic problems randomly shows up. 3) Spend a few weeks researching it on github/reddit, trying fixes, taking backups and repeating the similar solutions until you eventually discover that people have been discussing the exact same problem for years and it is somehow still there. 4) Keep your hopes up, reset the browser, go back to Step 1 and start the whole thing over again. 5) After 1 YEAR, or X YEARS, finally find the courage to get rid of Brave and go back to Safari or Chrome and quietly weep. We basically have the browser version of the operating system irony now. The only difference is that we don’t hear about some brand-new operating system every year, while plenty of companies can build another browser, give it amazing PR and make huge promises about privacy, speed and simplicity. And as usual, we users are left quietly weeping.

• 
  RaoulDuke (@RaoulDukeDegen) reported 4 minutes ago

  @koltregaskes github issues show the apology loop where it prioritizes sorry over fixes

• 
  Tony Darrick Baker (@tonydbaker) reported 7 minutes ago

  3/3 The sites already live on my hard drive, organized. I chat. The agent finds the project, finds the page, finds the places to change. It updates SEO, AEO, and speed from the same SOP every time. Grok Build, or any coding agent. Push to GitHub. Cloudflare has it live on the domain in seconds. I'm not hunting files. I'm not rebuilding a CMS. Today I'm pressing forward, rather than pressing issues.

• 
  Harshit Mathur (@spiderboyis) reported 12 minutes ago

  engineers talk endlessly about "technical debt," but nobody talks about the massive pile of "information debt" we accumulate every single week. ​we read deep research papers, bookmark obscure github repos, save architecture threads, and screenshot error fixes. we hoard data under the illusion that saving it equals learning it. ​three months later, when you actually need that exact solution, you spend 45 minutes trying to remember which app, chat, or folder you stashed it in. ​storage has become virtually free, but human context retrieval is more expensive than ever. the future of software isn't about capturing more data it's about zero-friction recall. ​how do you currently keep track of technical insights you know you’ll need months from now?

• 
  Luis (@lamg_dev) reported 14 minutes ago

  @zerosignal_ai I have a good idea for you: - a developer has a popular package in GitHub - they create an GitHub Action that continuously scans the source code for security issues, with decentralized inference - the network produces a ZK proof that the repository is OK - a badge in the README shows "security scan by agent OK"

• 
  XLion (@XLionc) reported 15 minutes ago

  @FullStackNate @theo Terrible UX, not support GitHub Actions syntax

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 16 minutes ago

  A GitHub outage just delayed the launch of a GitHub competitor. You can't script this. Cursor was set to ship Origin, its own code hosting platform. GitHub went dark for 6.5 hours that same day. Millions of devs sat frozen. Then Origin went live. → Your code, your changes, and your AI agent in ONE window → Two-way sync with GitHub. Change either side, both update. → Agents live in every repo. Ask questions. It pushes fixes. → Connect Vercel and every change gets a live preview link You don't have to pick sides. GitHub stays the boss. Origin is the seat belt. When your code host goes dark, a second home stops being nice-to-have. Save this. You'll want it later.

• 
  Patrick J. Auld (@PatrickAuld) reported 18 minutes ago

  I can confidently say local development is dead. I've run remote agents most of the year, and the only reason I run something locally is for a permissions issue. Local agents only found a foothold because it allowed people to grant agents greater access. I priced out my M2 MacBook against GitHub Codespaces when I got it. Codespaces was obviously cheaper. But startup latency was bad, and the tooling managing them wasn't very mature. Agents feel similar. There are options, but none make a ton of sense over running a box yourself. Running the model locally or calling a provider is orthogonal. You want an always-on version of your agents that's accessible across other devices The AI pin or the screenless interface is making more sense. A substantial amount of work can be done if we figure out remote agents with appropriate permissions beyond what the company that runs them can self-provide. Finding the balance between persistent, ephemeral, swarms, and all the complicated parts made simple will be the unlock. Their infinite patterns right now. They're all sort of good at different verticals. The reason all these exist is basically just context management. An agent with sufficient context to run for a long time and have memorables and all of that solves all the problems. I just don't believe current architectures will allow it

• 
  dominioscripto.eth (@septiembre_eth) reported 18 minutes ago

  3/ What just happened. OpenRouter added “Sign in with Ethereum” to its login screen. Next to Google. Next to GitHub. Millions of developers can now authenticate with their .eth wallet on the world’s largest AI platform. No password. No email. Just your Ethereum identity. (3/5)

• 
  Rijalll (@rijalllm) reported 25 minutes ago

  @Wisnu100802 @RialoHQ AGP login via github kah?

• 
  Investkingyru.ton (@kingyru) reported 25 minutes ago

  Cocoon’s problem isn’t just the lack of workers. There’s literally no one to contact: no TON Foundation, GitHub issues get ignored, Telegram Support won’t help, and a DM to Durov costs $150. Are builders just supposed to stop?

• 
  WhiteFlour (@FirstDeployAI) reported 26 minutes ago

  @liam_fallen I am not a big fan of cursor yet, the way that it attaches so hard to the Github for everything is not a long term thing for me, I plan to get far away from github thanks to Microsoft before they ruin it further. It's down now, at times, I never remembered that happening before.

• 
  Nathan Clark (@nathanclark_) reported 26 minutes ago

  As promised, here are some early thoughts on @bot Positives: Three-column setup It is nicely done, and the persistent computer screen preview is oddly satisfying and somehow signals/invites me to do work I know will require a workspace. Just visualising it is a smart UI/UX decision. Multiple accounts per connector!! And executed very well except in a small set of issues (see negatives below) Inline chat cards for auth, account setup, user question tool all very slick. It’s clear the system prompt encourages proactivity. This is definitely a net positive - just not something I personally want OOTB (I want to know its output quality, behaviour, defaults etc before it goes off as majority of my work ends up being a client deliverable that needs my oversight/contribution/refinement etc) Default communication style is clear and without too much puffery. Also good at telling me what isn’t yet done eg. “I have not put them in Notion yet.” Decently fast - though this is more a Grok 4.6 thing than a unique Bot thing. Having the Cursor plugin ecosystem available from day one means extremely high utility very quickly. You can Pin bots and create sections in the sidebar. Like Codex with threads/chats, one Bot can send prompts into others - great for an assistant/orchestrator style Bot - and the UI makes it very clear on both sides when it happens eg. “Message from [Bot]” You can create Routines in chat Channels is a really nice concept. Haven’t fully pulled on this idea yet but on face value I like it and already have some ideas. Negatives: Plugins that use an access token leave a “needs authentication” flag in the settings because you never complete an auth flow. You can’t add two github accounts - only auth option is via PAT (annoying), and while the UI presents the option to add another account it also only presents a single entry for “Setup Values”. I'd like more ability to set permissions and guardrails in a deterministic and obvious way - what can read, write and where. As it stands I’m not fully confident I can dial in with trust what the Bots can and can’t do. Skills and connectors mixed into the one place as “Plugins” feels awkward and not the right model. When installing a plugin and then reinstalling it, I noticed it had kept the accounts. Don’t like this behaviour. Mobile app for iPhone is great, no iPad optimised app - and Grok Bot uniquely out of all major agentic tool companies is already the most primed for it. Please ship a great iPad app! Skills management is limited to its own directory. Makes sense but is annoying for me as someone who across harnesses. Non-issue for “normies” and not a problem for anyone if they are all-in (for now I have a one-way sync from my .agents/skill directory into Private “plugins”) Pinned Bots take up too much space by default, at a relatively thin sidebar width I should still be able to have three across. I can’t manually order Bots inside a section.

• 
  steven (@wxstev) reported 30 minutes ago

  @_kingbob____ @rekoal3rb @RetroNationX anyone with a brain wouldn't put it on github tf, it would get taken down instantly