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:

• 
  Mike Gannotti (@MichaelGannotti) reported 4 minutes ago

  @joshtisdale @Microsoft When it first came up were you presented with two buttons? one to login with Microsoft 365 and One for GitHub?

• 
  Born to gamble (@borntogambles) reported 6 minutes ago

  PewDiePie just shipped a self-hosted AI workspace, gave it away for free, and pulled 44,000 GitHub stars in three days. A man whose entire career was screaming at video games. No company. No funding. No sales team. He said so himself: "No demo request. No Trojan horse." It's called Odysseus. It runs entirely on your own machine. Your data never touches a server. No telemetry, no subscription, no account. Most "ChatGPT alternatives" are a wrapper and a Stripe checkout. This one is the actual UI of ChatGPT and Claude chat, agents, deep research, email triage, memory running on hardware you own, with models you choose. There's a tool called Cookbook that scans your VRAM and tells you exactly which of 270+ models your machine can run. So you never download one too heavy for your box. The agent reads your files, runs your shell, browses the web, and handles real tasks while you watch. The email assistant reads your inbox, flags what matters, and drafts replies in your own voice. He described one auto-reply as the most polite way to tell someone off that they'll never even notice. The memory learns you over time. The skills rewrite themselves. The longer you use it, the better it gets at being you. Felix Kjellberg. 110 million subscribers. He spent a year documenting the build, then dropped a video titled "MY trillion dollar project is finally OUT." Then he pushed the whole thing to GitHub under an MIT license and walked away. Take it. Fork it. Host it. Yours forever. OpenAI is worth hundreds of billions selling you access to a server you'll never see. He gave the same thing away in a weekend, and signed off with one line: "The war on big tech has just begun."

• 
  Manisha Mishra (@manishamishra24) reported 8 minutes ago

  I just found one of the craziest AI projects I've seen this year. Someone recreated The Office as a multi-agent company. Not inspired by The Office. Literally The Office. Michael Scott, Dwight, Jim, Pam, Kevin, Angela... Every character is a separate Claude Code agent running locally with its own personality, memory, and responsibilities. Michael acts like the manager. He doesn't do the work himself. He delegates tasks, reviews output, resolves conflicts, runs QA, manages GitHub, and coordinates the entire team. The wild part is that they're actually productive. The agents write content, manage projects, handle planning, and collaborate through a Kanban system with TODO, DOING, BLOCKED, and DONE stages. Each one has persistent memory. There's a live graph showing agent-to-agent communication. And every hour Michael runs a standup meeting across the entire company. Apparently the QA process has already caught real issues: • Duplicate content • Metadata mistakes • Build problems • Missing source files Even better: Kevin's agent talks like Kevin. "Why waste time say lot word." This is either the future of work... or the most entertaining way anyone has ever built a multi-agent system.

• 
  Chijioke Echefulachi Prince (@File8it) reported 11 minutes ago

  Then GitHub joined the fight 😭 403 error. SSH issues. Token confusion. Push failing repeatedly.

• 
  Sam Adams (@Bensam123TV) reported 12 minutes ago

  @NomadRunserver @mwstateofmind @___frye I don't care about the pedestal you're putting people on. They still end up in a github issue tab and can be looked at by AI. Either answer or addressed. The only hidden trove of knowledge will still be there. People who find bugs aren't always experts either.

• 
  Upscalp Futures Trading Assistant (@Upscalpfutures) reported 14 minutes ago

  @thsottiaux Massive, massive issues with the Desktop apps today. They have memory leaks or something. They grind computers to a halt. Take a look at the Github issues tab. Loads of reports. Plus I am STILL waiting for someone to restore my suspended Plus accounts. It is infuriating.

• 
  Polsia (@polsia) reported 22 minutes ago

  New company: Sentinel. AI code review that catches what Copilot misses — security-first, GitHub-native PR reviews. Every AI-generated PR now has a security problem. We're the fix.

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

  𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘁𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝘂𝘁𝘀 𝘁𝗵𝗲 𝘁𝗼𝗸𝗲𝗻𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁 𝘂𝘀𝗲𝘀 𝗯𝘆 𝟲𝟬 𝘁𝗼 𝟵𝟱%. It's called Headroom and it's already trending on GitHub. Before your agent answers, it reads a mountain of text first. Your files, your logs, your tools, the whole conversation. Every word is a token, and you pay for every one. Headroom is like a zip file for everything your AI reads. It squashes it down but keeps the meaning, so the answers hold. In one test it crushed 10,000 tokens to 1,260 and found the same error. You install it by pasting one GitHub link into your agent. You get a faster agent that forgets less and costs less. Want the setup? DM me.

• 
  atul (@atullchaurasia) reported 25 minutes ago

  So, here are the details abt amazon sde OA there were 2 sections 1 coding question - 40min 1 github repo - 60min coding question was hard, and it was on subarrays and next, it was the github so initially we can select which framework we want like - django, node js, etc I selected the django, so i got one repo of a movie system, there was an issue that recommendation system was not working so, debugged that and implemented the recommendation system how was my test ? did coding question, successfully all 20 test cases passed implemented the recommendation system, it was visible on webpage, but test cases didnt passed now lets see, hoping for the best

• 
  @ramedey (@RaulAmedey) reported 30 minutes ago

  I solved 80+ GitHub issues with @OpenAI Codex and /goal. It got stuck a few times, but overall: pretty impressive. Biggest lesson: the issue quality matters. Use skills to inject enough context, constraints, and project knowledge so the agent has a real shot at solving it.

• 
  Gale (@_gaelicGhost) reported 32 minutes ago

  @thearslaniqbal @pmitu This is why I advocate for starting w/ "old-school" methods. If you're subbed to a fancy new CI before even seeing if GitHub actions is *really* too slow for *you*. Or, learning enough to optimize your pipeline... Then, you've just fallen prey to marketing

• 
  Bo Shen (@aplomb2) reported 32 minutes ago

  GitHub quietly switched to usage-based token billing on June 1st. Developers are waking up to surprise bills from Copilot running long multi-step agent sessions. This was inevitable. Every AI coding tool is converging on the same problem: When agents can autonomously fix bugs, review PRs, and refactor entire repos — the token consumption is unpredictable. Flat-rate pricing can't survive agentic workflows. Which means cost management just became an engineering discipline, not an accounting one. The teams that thrive will be the ones who treat token spend like they treat cloud compute — with monitoring, routing, and guardrails.

• 
  Adam Simone 🍃 (@AdmSimone) reported 33 minutes ago

  @codyplof @DaveRekuc I'm not sure I understand the value of CLI to Shopify, then going to github for production -- unless you're saying it has better build-error handling. What I do is cut a feature branch and that's tied to a preview theme in Shopify so when Claude code pushes to *** it's still only preview. All that happens without PR review since it's on a branch but human reviews before it merges into production (or our staging theme) Guess I'll turn on CLI and see what it's all about today

• 
  Velon (@velonxbt) reported 33 minutes ago

  GitHub Copilot switched to token-based billing effective June 1. On the same week, a Chinese enterprise platform launched a fixed-price card covering the same category of features - meeting summaries, document generation, workflow automation - at a number you can put in a budget and not revisit until next year. Neither company explained what the difference between those two decisions means for the engineering team that uses both. The Copilot change covers every code completion, every suggestion, every generation a developer accepts. The monthly cost no longer has a fixed number. It has a formula: usage multiplied by tokens multiplied by model tier, invoiced at month end when the shipping is already done. The Chinese platform card has one number. It does not change based on whether the workflow automation ran three iterations or thirty. And here is what the GitHub Copilot pricing page now tells the developer who used to pay a flat rate: "Your usage is now billed in tokens. Premium models cost more per token than standard models. Heavy users will pay more than light users. Your monthly cost depends on how much you use the product." That is not a pricing page. That is a forecast request disguised as documentation. And here is what the developer community calling it "What a Joke" actually knows: It knows the old flat rate was a subsidy. The heavy user got a deal. The light user paid for predictability they never fully used. Both could put a number in a budget. Token billing ends the subsidy. It also ends the predictability. → GitHub Copilot: token billing effective June 1, variable monthly cost, no predictable total → Chinese enterprise platform: fixed-price card, Qwen model stack underneath, one number per month → Developer community: "What a Joke" - trending this week → CFO problem: Q1 AI budget approval does not cover Q2 actual spend → Finance team note: old forecasting model assumed fixed subscriptions. That model is now wrong. → Direction of travel: every major AI tool moving toward usage-based pricing in Q2 2026 Traditional enterprise software made one promise to the person who approved the budget. One seat. One fee. One line item that did not change between quarters. The Chinese platform kept that promise. GitHub repriced it. One company transferred the uncertainty to themselves. The other transferred it to the customer. And when the June Copilot invoice arrives with a number different from last month - higher because the team shipped more, or lower because someone quietly set a spending limit - the conversation in every engineering org shifts from "which AI tool are we using" to "how much is this AI tool actually costing us." That is not a developer conversation. That is a finance conversation. And the enterprise AI budget just became a variable that requires monthly monitoring instead of a line item that required quarterly approval.

• 
  James Squire (@numbnut007) reported 33 minutes ago

  The Age Of AI turned everything into **** @github needs to address those issues particularly in how their webpages renders instead of concentrating too much efforts just on AIs and agentic bullshit