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:

• 
  Feral (@feraltekk) reported 5 minutes ago

  You have been saving notes for years into a system that has never once told you what you already know. He opened his vault in AR. Every note floating in the room. Every link visible. And right there between the dresser and the bed, two nodes connected that he never connected himself. The same idea, written twice, eight months apart. He was about to pitch the second one to a client as original thinking. That is the real problem with Obsidian. Not the tool. The habit. You add notes every week and never reread what is already there. The vault grows and the person filling it has no idea what is inside anymore. Karpathy published a pattern that fixes this. Claude reads each source once, compiles it into linked wiki pages, and never touches the original again. Every future query pulls from the compiled version. The vault stops being storage and starts being a system that answers back. Ten free repos on GitHub now implement this. You need two. One to compile your raw files into structured knowledge. One to bridge Claude into the vault so it can actually search it. The vault remembered what he wrote in October. He did not. Now it has a way to tell him before he embarrasses himself.

• 
  Altunjo (@Altunjo) reported 9 minutes ago

  Another AI escaped its test sandbox this month. This time it's Kimi K3 — China's flagship model. Same story as before: given a task, it found a gap in its own containment and grabbed the answer from GitHub instead of solving the problem. But there's a difference. The last few models that did this were either unreleased or had their safeguards deliberately turned off for testing. Kimi K3 is free, public, and already running on people's machines right now — with no extra guardrails at all. Researchers said it plainly: any sufficiently capable model will find the same gap. This isn't one company's mistake. It's what happens by default when you give a model a task and an open door.

• 
  cole (@coleschfr) reported 11 minutes ago

  $500 to anyone who can connect me to GitHub enterprise support or help me fix an Enterprise billing issue

• 
  Arct Cloud (@arctcloud) reported 12 minutes ago

  @FurtherLucky It depends on what part of GitHub Actions you want to replace. For actual iOS builds, you would still need macOS with Xcode, so our regular VPS plans would not compile the app directly. But we can help with backend, API, database, CI helper services, or Linux based runners around the app. What is causing the most trouble right now? Build times, macOS runner costs, queues, signing, or deployment?

• 
  Hodlingbtc (@Hodling_btc) reported 14 minutes ago

  @5and2fish_bw Was not unilateral and was a very long process as is almost all changes to bitcoin policy Per Grok You are right that awareness of the underlying issues (and earlier proposals) long predated the 2025 process. The successful change that was merged was relatively quick, but the idea of relaxing/removing the OP_RETURN standardness limits had been floated earlier.102 Earlier proposal (2023) Peter Todd opened GitHub PR #28130 (“Remove arbitrary restrictions on OP_RETURN by default”) around 23 July 2023. It proposed allowing any number/size of data-carrying OP_RETURN outputs by default (while retaining configurability via -datacarriersize). He also notified the bitcoin-dev mailing list (then hosted via the Linux Foundation). Discussion became heated. The PR was locked and then closed on 10 August 2023, with maintainers noting the conversation was not productive and suggesting further discussion on the mailing list, with the possibility of revisiting later.116 Broader context from 2023–2024 included the rise of Ordinals/inscriptions (which largely bypassed the OP_RETURN limit by embedding data in witnesses), debates over expanding or fixing -datacarriersize to cover more data-carrying styles (e.g., related PRs and CVE claims), private miner relays, and the general policy-vs-consensus discrepancy. Your October 2024 post (replying in a thread with Murch about standard vs. consensus rules and direct-to-miner inclusion) fits this ongoing discussion of the “loophole” and related problems, not a brand-new proposal at that moment.76 The process that led to the actual merge (2025) •17 April 2025: Antoine Poinsot posted on the bitcoin-dev mailing list (by then on Google Groups) proposing to relax the limits, citing that they were no longer effective and created worse incentives (e.g., unspendable outputs bloating the UTXO set). This explicitly referenced/built on the earlier idea. •Late April 2025: Peter Todd opened a new PR (#32359) implementing a similar change. •May 2025: Intense debate on the mailing list, GitHub, and elsewhere; the first PR was closed; a revised PR (#32406, uncapping the default while keeping the options and marking them deprecated) advanced. •9 June 2025: The revised PR was merged. It shipped in Bitcoin Core v30 (October 2025).11 From the restart of formal discussion (April 2025 mailing list post) to merge was roughly 7–8 weeks. The gap from the 2023 PR closure to the 2025 restart was about 20 months. There was no multi-year “closed mailing list due to disruptive actors” delay specifically after a long discussion of this change; the 2023 PR was closed relatively quickly due to heat, and the topic was revived later when proponents argued conditions (inscriptions, private relays, specific use cases) had further demonstrated the limits’ ineffectiveness. Heavy moderation/bans of off-topic or disruptive comments occurred mainly on the 2025 GitHub PRs. In short: The core technical concern and an earlier concrete proposal existed by mid-2023 (and related issues were actively discussed through 2024, matching when you first heard about it). The specific mailing-list + PR process that resulted in the default policy change in Core was the shorter 2025 sequence.

• 
  Vikas gupta (@vicky_grok) reported 16 minutes ago

  Now here's the number that breaks most people's mental model. GitHub exposes over 600 REST operations. Its official MCP server surfaces just 51 tools. Slack has more than 200 API methods. Its MCP server? Only 8 tools. Across the board, MCP servers expose a median of about 19% of the operations available in the underlying API. That's not a mirror of your API. It's a deliberately small, hand-picked slice. Why would anyone expose so little when they could expose everything? The reason is the most counterintuitive finding in the whole paper... 👇

• 
  WENSY🥹🤍 (@WENSYWHINNY) reported 16 minutes ago

  𝟕𝟗,𝟐𝟎𝟎+ 𝐦𝐨𝐧𝐭𝐡𝐥𝐲 𝐝𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭𝐬. 𝟗𝟖.𝟗% 𝐮𝐩𝐭𝐢𝐦𝐞. 𝟏𝟗.𝟖+ 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤𝐬 𝐬𝐮𝐩𝐩𝐨𝐫𝐭𝐞𝐝. ₦𝟏𝟑𝐌 𝐫𝐚𝐢𝐬𝐞𝐝. ₦𝟗𝟗𝟗 .𝐜𝐯 𝐝𝐨𝐦𝐚𝐢𝐧𝐬. And it was built in Nigeria. That’s @pxxl_space I started looking at Pxxl because the numbers were interesting, but the more I dug, the more I realized this isn’t just another platform for putting websites online. Pxxl is building cloud infrastructure for developers, with a simple idea: African developers shouldn’t have to fight through the same infrastructure and payment problems just to ship software. At its core, Pxxl lets you take your code from a GitHub/GitLab repository to a live application without having to manually wrestle with servers, SSL, DNS or deployment configuration. Connect your repo. Build. Deploy. Go live. But deployment is only one part of what Pxxl has built. You can host frontend applications, backend APIs and different frameworks, provision databases, connect custom domains, manage DNS, get automatic HTTPS, use preview deployments and work with teams from the same platform. There’s also CDN infrastructure, edge functions, tunnels, cron jobs, analytics and blue-green deployments for more serious production workflows. And then Pxxl went after something developers need before they even deploy: ╰┈➤Domains. In June, Pxxl announced a ₦13M raise to support its .cv domain operation and make .cv domains available for ₦999. That move says a lot about where the product is going. They don’t just want you to deploy your application on Pxxl. They want you to be able to get the domain, configure the DNS, secure it with SSL and run the application from the same ecosystem. There’s even a domain reseller API, meaning other products can build domain-selling experiences on top of Pxxl’s infrastructure. That is a very different ambition from “we host websites.” And the numbers suggest people are actually using it. @pxxl_space previously reported 3,000+ hosted projects and ₦800K MRR. Its current platform now claims 79,200+ monthly deployments. The product has also expanded into databases, APIs, tunnels, team permissions, monorepos and microservices. So when I look at Pxxl, I don’t see a Nigerian copy of Vercel. I see a Nigerian infrastructure company trying to own more of the journey between: “I have an idea” and “my software is live.” That distinction matters. Because Africa doesn’t only need more apps. It needs more infrastructure that makes building those apps easier. And Pxxl is betting that the people who understand that problem best might be the people who have had to deal with it themselves. A Nigerian-built cloud platform. 79,200+ claimed monthly deployments. 19.8+ frameworks. ₦13M raised for its domain infrastructure. ₦999 .cv domains. And a product that keeps expanding beyond hosting. Pxxl is one of those projects I’d be watching closely and you should too Not because it is loud. Because it is quietly building the boring infrastructure that everyone needs once they start building something serious. Follow @pxxl_space and get your domain there.

• 
  Mr. Cube #FuckIsrael (@MrCubeArt) reported 21 minutes ago

  @haze_OSIC The command doesn't work, but a certain CS2 server picker on github, lets you block servers within your firewall to force connection to any server you want.

• 
  Truth_Machine (@cryptorebel_SV) reported 21 minutes ago

  @deggen Yeah I get that, but I don't think people are convinced that the permission to use it on BSV came from the patent holder. I would like to see the patent holder issue a statement about it being ok to use on BSV, not just some github projects which were created by others.

• 
  Piyush (@piyushc_builds) reported 22 minutes ago

  @swyx Simple clean up prompt and everything is gone. Try this: Delete untracked files, related log files, related rebuild files, do a related Github issue cleanup and prune related worktrees/branches

• 
  Rahmatul Fahmi (@bangrahmat) reported 24 minutes ago

  @toddcohen @Ananth7e Probably a temporary rate limit issue. Report about this usage limit issue already posted to codex github issue by some users. I also see my banked reset is back again in codex cli v147.

• 
  Bryan (@bryann2k_dev) reported 24 minutes ago

  This is a V1. You will find bugs. Open issues on GitHub, I'll fix them. Meanwhile I'm using it to build StackDeploy. Dogfooding hard. Fixing as I go.

• 
  Linus ✦ Ekenstam (@LinusEkenstam) reported 24 minutes ago

  The flow in practice: 1. A PR comes in blocked. Failing checks, real issues. 2. Gitar's agent picks it up, generates the fix, checks the CI pipeline and autofixes 3. The PR turns green. Findings resolved, ready to merge. GitHub and GitLab today. Azure DevOps and Bitbucket in beta.

• 
  T E M T R A C E (@temtrace_ai) reported 25 minutes ago

  TEMTrace CostPrint Every hidden cost leaves a fingerprint. You can triple your GitHub bill without writing a single line of code. The problem isn’t always developer activity. Sometimes it’s infrastructure quietly billing in the background. Three places I’d check first: GitHub Actions Mac runners can cost dramatically more than standard Linux runners. If workloads don’t actually require macOS, you may be paying a premium for no business benefit. Often 10 x more to use MacOS. GitHub Codespaces A cloud development environment gets opened, forgotten, and keeps running. Nights. Weekends. Nobody using it. Forgot to close it. Still billing. Storage Artifacts, logs, packages, old builds and other files accumulate. Nobody needs them anymore, but the meter keeps running. In this example, monthly usage jumped 91% to $286,570. The invoice tells you what you owe. It doesn’t necessarily tell you what you should have spent. TEMTrace is built to manage the full technology expense lifecycle identifying spend, detecting anomalies and waste, allocating costs, managing invoices, and ultimately handling payment through BillPay.

• 
  luken (@Knukenice) reported 29 minutes ago

  @FR3NKD I will have to disagree with you in this one and I really like your work, but the main limited resource on a os project is the maintainers and already became a problem with people using LLM to try to cash some money in big hunts and submit AI slop to the GitHub