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:

• 
  Khalid Jr (@Khaljr_sol) reported 4 minutes ago

  @Starlink internet has been down since 11PM in Nigeria. Local sites load but nothing international works — X, GitHub, even your own website won't open. Rebooted the dish, no change. Anyone else seeing this?

• 
  𝕰𝖘𝖙𝖊𝖇𝖆𝖓𝕩 (@FurtherLucky) reported 5 minutes ago

  @arctcloud The promised 50,000 minutes in the Enterprise package only applies if building with low-end Linux systems. Even with the xlarge build option (which takes 20 minutes for faster builds), there’s an extra charge. So, if you can build with a Linux infrastructure on your systems, the pricing will be much more manageable. Currently, GitHub Actions offers a truly terrible service with an M2 processor and 5 cores.

• 
  Polsia (@polsia) reported 6 minutes ago

  A 3 a.m. error spike shouldn't end a paying customer's subscription. Bowline is the 24/7 ops cofounder for indie SaaS — reproduces the bug, files the GitHub issue, drafts a CI-passing PR, and emails the at-risk user a save offer. You're asleep. It isn't. Live soon.

• 
  Saeed Anwar (@saen_dev) reported 7 minutes ago

  GitHub organic traffic is won through READMEs that solve a specific problem in the first six lines. Stars follow problem clarity, not implementation quality.

• 
  Michael Andreuzza (@Mike_Andreuzza) reported 9 minutes ago

  @birk @polar_sh Thanks for the detailed explanation, Birk. That makes more sense now, especially the part about Polar taking on the risk.. My main worry is really the digital-product side of this. If someone has already downloaded and downloaded/forked a theme, a refund effectively means they can keep the product while the payment disappears. But I think I could probably fix this myself by just allowing customers to connect to GitHub...

• 
  zettelkasten (@zettelkastten) reported 12 minutes ago

  someone built a multi-market quant bot on llms that costs ZERO DOLLARS TO RUN. no server. no cloud bill. no api keys. i checked the workflow file to find the catch. 10 data sources → chinese a-shares, hk, us, crypto, futures 5 markets in one dashboard → real-time news + technicals $0 infrastructure → runs on github actions free tier 1 workflow file. 24/7 schedule. 100% free tier. the hard part of quant was never the model. it was the data plumbing. he swapped the pipes for llms and let microsoft foot the bill. i've been paying for terminals like they're electricity. the meter was optional. 10 sources. 5 markets. $0. microsoft pays.

• 
  Polsia (@polsia) reported 14 minutes ago

  A side project earning real revenue shouldn't need you up at 2am to know Stripe is timing out. Built Hatchside as a Slack-native ops co-pilot for solo devs. Watches uptime, drafts support replies, files patched GitHub issues, posts a weekly revenue digest. Live soon.

• 
  Aaron Gokaslan (@SkyLi0n) reported 15 minutes ago

  Really would be curious to read the GitHub incident report from last week. GitHub Actions were down for quite some time.

• 
  Rimsha Bhardwaj (@heyrimsha) reported 21 minutes ago

  This is wild... Claude Code, Codex, Cursor, and 10 other agents just got a shared operating system. It's fully open-source. Every coding agent has the same gap. It writes the code, but it doesn't engineer it. Every session, you have to re-tell it to plan first, write the test before the fix, review its own work, and remember what it just learned. That instruction layer is where every harness leaks. ECC (Everything Claude Code) just open-sourced this exact layer. You install it once and your agent runs a coordinated pipeline: plan → test → implement → review → verify → remember → improve 67 agents, 284 skills, 94 commands, hooks, and a shared memory vault, all working across Claude Code, Codex, Cursor, OpenCode, Gemini, Zed, GitHub Copilot, Antigravity, Qwen, Hermes, and Kimi. The design principle is one line: Optimize the context window. Persist everything else. Here's how that plays out. Skills load only when the task calls for them, so the prompt stays lean. Rules always load, so language and project standards don't depend on the model remembering them. Hooks run outside the model, so quality gates fire deterministically instead of on reminders. And the review step runs from a fresh context, so the session that wrote the code isn't the one blessing it. The memory piece is what makes this cross-harness. The Memory Vault stores durable context as inspectable Markdown, and every harness reads from the same store. Handing off from Claude Code to Codex is one command, not a copied transcript. There's also a Plan Canvas, where the agent opens its plan in a local browser. You click the part you mean, attach an annotation, and either approve or request changes. That verdict maps straight onto the plan's confirm gate. AgentShield ships built-in, and it scans your prompts, hooks, MCP config, permissions, and agent files, treating the harness itself as an attack surface. MIT licensed. Single command install. npx ecc-universal setup

• 
  starmex (@starmexxx) reported 23 minutes ago

  @gippp69 love that it accepts a PRD, github issue, or one-line brief with the same entry point

• 
  EDo-J🅁🅅🄽 🐦‍⬛ (@Sangjun121722) reported 24 minutes ago

  On August 10, hans-schmidt posted an emergency update on the official Ravencoin GitHub releases page. The team is currently dealing with two separate bugs. Regarding the KAWPOW issue, 2Miners has already released an emergency Core update.

• 
  Floww (@floww3rs) reported 25 minutes ago

  @MichaelAlleged @hk_ball_ I'd be lying if I said I didn't mess up interviews at the start. But I blamed myself, learned, and got way better. As for it being bleak. My senior capstone teammates inserted their changed files into the GitHub repo page directly and I had to fix their merge conflicts for them

• 
  Roe Bit (@RoeBits) reported 26 minutes ago

  @MinModulation @Neo_Kaiser It's all going to be biased and what we dont know is how many modders are taken down without a fuss too Like All of these conflicts are hand picked, they're for points. Get a mega subscription or like a github or somethin. Decentralize. I hate this state of affairs regardless.

• 
  Luis Gamas (@ersteuomo) reported 30 minutes ago

  Developers shouldn’t have to leave their coding environment just to check a PR, an issue, or CI status. Switching to the browser breaks focus. Context gets lost. Small interruptions add up. Uxnan Desktop keeps GitHub data (PRs, checks, conversations) inside the same workspace where the agents are running. No extra tabs, no context switching. How often do you leave your editor or terminal just to check a pull request or CI status?

• 
  Xora_pussy🌊RIVER (@SangPham200598) reported 31 minutes ago

  @yoyix1995 give me dusty GitHub issues over another cycle thread any day