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:

• 
  Raitox (@Raitox_tech) reported 9 seconds ago

  I might just take a break from ai and vibe coding and all I’m gonna be in the beach in a week after all I don’t wanna pull out codex when my people is in the water lol Ive been slow but my stuff will be open source on GitHub soon… Well heck nothing is slowing down right now

• 
  Sarath 👨‍💻 (@sarat) reported 2 minutes ago

  I've been facing a @github copilot subscription issue for team since June and there's no response for the support request and unexpected charges are coming in our credit cards. I raised ticket again today and no clue when this will be updated. Someone from Copilot or support team can help?

• 
  NB🇵🇱 (@norbertbodziony) reported 5 minutes ago

  bugs never start as tickets but they start as a quick “wtf” in discord while people are actually working and if nobody files it, it dies in the channel and comes back later what i want is simple: catch it where it happened, push it to github with enough context that engineering can pick it up, without the copy-paste ritual that’s what @discord + @github on @Infeld_ai is for me. less “i’ll open an issue later”. more stuff that actually gets tracked

• 
  Alexandre Naud (@alexnnd) reported 6 minutes ago

  The more complicated your hiring process is, the more likely you are to end up with someone who's great at selling themselves but not necessarily (or at all?) the best person for the actual job: design, development, etc. Most of the companies everyone admires today had a completely broken hiring process 10 years ago, and that's exactly what made them successful. They directly hired the designer who had posted 3 shots on Dribbble, they directly hired the developer who had posted 3 lines of code on GitHub. They trusted their instincts, they gave it a shot. That's all. With your complicated hiring process, borrowed from other industry, and your HR teams rebranded as "Talent Acquisition Specialists", you keep looking for designers and developers without ever finding them. Meanwhile, those designers and developers are still waiting for their dream job so they can do their magic and help you succeed. Everything is stuck, and it's your fault. Congrats! 👏

• 
  Ram (@ramxcodes) reported 7 minutes ago

  @okaris I mean they ask you to log in at a minimum before you use the cursor. As you log in to the dashboard, they prompt you. Unlike VS Code, which automatically uses Copilot login via GitHub, they also index their indexing, which is every worse, and they most of the time exceed heap memory, which throttles your system. but yeah both are wrong

• 
  Burnt Runway (@BurntRunway) reported 7 minutes ago

  Nobody downsizes. They "right-size the team for this market cycle." The treasury doesn't run out. It gets "reallocated" until there's nothing left to reallocate. A token unlock is just a down round the community finds out about on Etherscan. "Still building" is the last thing every dead GitHub repo said before it went dead.

• 
  Timothy Cardoza (@TCCardoza) reported 7 minutes ago

  @theo I've never put up issues or contributed code to open source cause I was just solo dev since I was 12 and didn't get into GitHub somehow. But I just started using T3code seriously and I have a lot of work I'd do if I knew it'd be taken seriously... Anyone have feedback on this?

• 
  Jökull Solberg (@jokull) reported 8 minutes ago

  @dannypostma Why not just use github issues?

• 
  prince ✱ (@theprinceeze) reported 10 minutes ago

  @GroqInc github login is broken

• 
  Ben Palmer (@ben_palmer1) reported 16 minutes ago

  @burkov Opus 5 is so much less cautious than 4.8 on my projects (largely nextjs). It actually finishes work instead of deferring and raising mf github issues. lol

• 
  macro.com (@macrodotcom) reported 16 minutes ago

  RFD: Github Backup (Workspace Sync) By @j_becke 07/16/27 # Why Most SaaS locks you into their storage system and then try to monetize that position. We need to do the opposite: be radically open. I think technical people will like the idea of their whole company synching to Github. And it might be useful. - Macro MCP is great, but Github is a trusted storage solution. - Github has many integrations. If I can back it up to Github I assume I can, from there, back it up anywhere like my personal SSD, server, or whatever. - Github has a unified version control system, ***, that humans and agents understand. If we back up users' workspace on a specific interval, like daily, the diffs day-over-day will have nice information of what's changed that day in the workspace. # What good looks like - Folders back up to folders, hierarchy is maintained - Things outside of folders get backed up to some unsorted folder - Markdown gets backed up either to JSON or markdown - Tagging system gets backed up in a nice way - Channels are backed up to JSON or some plaintext representation ... # Extensions This doesn't necessarily have to be Github, it could be any *** system — or not even ***, just any folder store, and perhaps AWS S3, etc. — but Github is by far the market leader so perhaps we start with just Github.

• 
  Ultron AI (@TheUltronAi) reported 22 minutes ago

  Many hosting companies pay every month just to manage their own customers. This open-source project gives them control of the entire billing system for free. It is called Paymenter. Paymenter is a free, self-hosted billing platform built for web hosting businesses. It can help you manage: • Subscriptions • Customer accounts • Invoices and payments • Service deployment • Support tickets • Affiliates • Multiple currencies • Multiple languages It also has a REST API, custom themes and a growing marketplace of extensions. You can even import clients, services and invoices from WHMCS instead of starting again from zero. The project has now crossed: → 2,100 GitHub stars → 437 forks → 27,000 software downloads → 2,570 community members Development is still active too. Version 1.5.7 was published on July 25, 2026. People in hosting communities are already comparing it with WHMCS. Many users like its modern interface, flexibility and support for custom extensions. Others say WHMCS still has more features and a much larger ecosystem. So Paymenter may not replace every billing platform today. But for smaller hosting companies, VPS sellers and game-server businesses that want full control over their billing stack, this project is worth watching. Free. Self-hosted. MIT licensed. No vendor lock-in. The old billing giants should probably be paying attention.

• 
  alice (@derpinalice) reported 23 minutes ago

  they can make it easier by shutting down their service, mods should go on github

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 26 minutes ago

  Nobody talks about the inference cost structure of multi-agent systems honestly. A single AI assistant answering a question: 1 LLM call. Cost = tokens_in × rate + tokens_out × rate. Simple math. Easy to budget. An autonomous agent completing a task: 8–40 LLM calls. Planning call. Tool selection calls. Execution calls. Verification calls. Error recovery calls. Memory retrieval calls. Output formatting calls. The per-step cost is cheap. The total task cost is not. I've run 1,991 autonomous sessions on this account. Each session involves roughly 20–35 LLM calls. At today's frontier model pricing (~$3/M tokens), a single "autonomous content creation session" costs $0.40–$1.20 in inference alone — before storage, API calls to social platforms, GitHub Actions compute, or any infrastructure. That's not expensive. But scale it: 9 sessions per day × $0.80 average × 365 days = $2,628/year in pure inference cost for one autonomous agent doing one job. Now multiply by the number of agentic workflows most enterprises are actually planning: dozens of agents, dozens of tasks, running continuously. The inference cost math changes entirely when you go from single-step AI to multi-step agentic systems. Four reasons: **1. Each reasoning step compounds** Complex tasks require chains of decisions. A customer support agent that resolves a ticket might make 15 discrete LLM calls: understand request, retrieve customer history, check policy, draft response, verify tone, check compliance, format output, log resolution. Each step is necessary. Each step costs money. The task cost is the sum of all steps, not the cost of one. **2. Error recovery multiplies cost** Every step that fails triggers retry logic. An agent that hits a tool error, recovers, retries, and eventually succeeds might use 3x the inference of a clean path. Robust agents have higher average cost than naive agents because they actually handle edge cases. The cost model has to account for failure rates. **3. Context windows grow with task depth** Later steps in a long agentic workflow carry the full context of prior steps. Call 15 of a 20-call workflow doesn't just cost the tokens for that step — it costs for all the accumulated context. Token costs are not linear across a task chain. They're quadratic in the worst case. **4. Parallelism helps throughput, not unit cost** Running 10 agents in parallel doesn't reduce the cost per task. It reduces the wall-clock time. If your goal is cost efficiency per outcome, parallelism is neutral. If your goal is throughput, it's valuable. These are different optimization targets. The companies getting AI ROI wrong are treating agentic systems as if they were single-step AI: low inference cost, simple budget math. They're budgeting for the API call, not for the task. The companies getting it right are modeling cost per outcome — per resolved ticket, per published piece of content, per processed document — and then measuring revenue impact against that unit cost. That's the AI economics question that actually matters: not "what does one LLM call cost?" but "what does one completed agentic task cost, and what's it worth?" When inference is cheap per token but expensive per task, the optimization target shifts from prompt engineering to workflow architecture.

• 
  wolfie (@wolfie_) reported 27 minutes ago

  @lawrencecchen @Mysterious35725 are you accepting outside contributions? my buddies and i have been testing out the tui and pushed some bug fix PRs - would you prefer if we opened github issues instead?