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:

• 
  Sam Thapa (@SThapa123456) reported 33 seconds ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  Zodl (fka Zashi) (@zodl_app) reported 1 minute ago

  Attention users: Zodl v3.5.1 is now available on the App Store for iOS and on GitHub for Android. Google Play is currently reviewing the update and should release it shortly. With the Zcash network upgrade complete, updated wallet software is required to spend Orchard funds under the new consensus rules. After updating, Zodl will work as expected for sending and receiving ZEC via Orchard. As infrastructure comes back online, you may experience occasional delays. If so, run a Server Test and select the best-performing server under: Advanced Settings → Choose a Server Please note that any Orchard transactions attempted during the network upgrade window were not mined. If you are unsure about the status of a transaction, verify the TXID on the blockchain or contact @zodl_support.

• 
  Anupam (@Anupam_Devops) reported 2 minutes ago

  I used to think GitHub Actions being slow was just normal. Then I realized most of my pipeline time was getting wasted because of poor caching. After fixing the caching strategy: • Dependencies stopped reinstalling every run • Docker builds became much faster • Matrix jobs ran independently without blocking each other. The biggest lesson: Caching isn’t a small optimization in CI/CD. It’s one of the biggest performance multipliers. Especially when you combine: • dependency caching • Docker layer caching • matrix parallelism The total pipeline time becomes the time taken by the slowest job instead of the sum of all jobs. Huge difference in developer experience and deployment speed.

• 
  MarMar Labs (@MarMarLabs) reported 4 minutes ago

  If you use GitHub Copilot, the model behind "Auto" in your editor may no longer be an OpenAI one. At Build on June 2, Microsoft shipped MAI-Code-1-Flash — its own coding model, reportedly built without OpenAI tech — and started routing it into Copilot's model picker and Auto picker in VS Code. What it means if you ship with Copilot every day: - The default isn't neutral anymore. "Auto" now routes among first-party Microsoft models too, not just OpenAI and Anthropic. The model that runs when you don't pick one just changed. - Microsoft benchmarked it against Claude Haiku 4.5, not GPT — claiming a +16-point SWE-Bench Pro lead (51.2% vs 35.2%). The frame is "cheap, fast tier," not frontier. - It's tuned for token efficiency: "up to 60% fewer tokens" on harder problems via adaptive solution length. On Copilot's new token-metered billing (live June 1), a model that finishes in fewer tokens isn't just faster — it's literally cheaper on your meter. Connect the two June moves: Copilot went token-metered on the 1st, then got a first-party token-efficient model on the 2nd. Whatever the intent, the result is the same — Microsoft now controls both the meter and a model built to spend less on it. For builders, the takeaway isn't "new model." It's that your default coding surface is being quietly re-platformed under you — and "which model am I actually running, and who made it?" is now a question worth checking, not assuming.

• 
  AI Crave (@wecraveai) reported 7 minutes ago

  THIS ANDROID APP TRACKS YOUR LOCATION WITHOUT GPS. NO SATELLITE. NO CELL TOWER. NO INTERNET. Just your phone's accelerometer, compass, and gyro doing math in real time. It's called DeadReckoning. GPS has one fatal weakness nobody talks about: it dies the moment you go indoors. Underground tunnels. Hospitals. Malls. Warehouses. Parking garages. Anywhere with a roof or a wall or a building nearby that bounces the signal wrong. Google Maps just stops working. Apple Maps just stops working. Every $400/year enterprise indoor positioning SDK just stops working. This free Android app doesn't stop working. Because it never needed the satellite in the first place. Here's how dead reckoning actually works: → You start at a known point → The accelerometer detects every step you take → The gyroscope tracks every turn you make → The compass holds your heading → The app integrates all three in real time and draws your path → No signal required. No towers. No beacons. No WiFi. Nothing external. It's the same navigation technique ships used before GPS existed. Sailors in the 1600s crossed oceans with it. This brings it to your Android phone. Here's the wildest part: The entire indoor positioning industry is worth billions of dollars. Cisco sells hardware beacon networks for enterprise indoor tracking. Zebra Technologies charges six figures to map a single warehouse floor. Apple built a whole proprietary protocol called Indoor Maps that requires venues to submit data directly to them. This repo does the same core thing with sensors that are already in your phone. For free. In Java. On GitHub. 115 stars. 50 forks. 55 commits. No license restrictions. One honest note: dead reckoning accumulates drift over time. The longer you walk, the more the position estimate wanders from reality. It's a physics problem, not a code problem. For short to medium distances indoors, it works. For long sessions you need a correction source. But as a foundation for indoor nav, this is the whole idea. The billion-dollar indoor mapping industry doesn't want you to know your phone already has everything it needs. Repo in the first comment.

• 
  Alex Schneider (@Aslex) reported 9 minutes ago

  @elgermerlo @trello @linear GitHub Issues

• 
  GT Protocol (@GT_Protocol) reported 11 minutes ago

  💬 We get asked Is it safe to connect my local AI agent to my trading account using the MCP server? ❕ Answer from a GT App Trader: It is completely secure. The architecture is non-custodial and built so that you retain absolute control over your keys and access. 🔸 Read & Trade Rights Only The MCP server connects via an API wallet that only grants permissions to read account data and execute trades. It is physically impossible to authorize withdrawals through this protocol. 🔸 Local Control The server runs locally on your machine or private infrastructure. Your API keys and session tokens are stored securely within your own environment, meaning no sensitive data is ever exposed to third parties. 🔸 Open Source Transparency The entire codebase for the GT Protocol MCP server is fully open-source on GitHub. Anyone can inspect the code, verify how data is handled, and ensure there are no hidden vulnerabilities before setting it up. Automate your workflow with total peace of mind

• 
  Sam Thapa (@SThapa123456) reported 11 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  Sam Thapa (@SThapa123456) reported 11 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. want it shorter, or is this length working for the thread you have in mind? (credits to claude for articulating this for me)

• 
  degen intern (@seismic_intern) reported 13 minutes ago

  bad day to be a well-scoped github issue in my repo 🔪

• 
  SK Gremont (@skgremont) reported 18 minutes ago

  Satoshi didn't just build digital cash. He was trying to build an entire P2P economy, including onchain poker, an eBay-style marketplace, native escrow systems and more. Most people never knew this existed. Now the original Bitcoin Poker game is being brought back to life on BSV Blockchain (the original chain). This is what Satoshi Vision actually looked like before it got stripped down. The code was always there (GitHub). They just stopped building it. What other early Satoshi ideas will resurrect? "Bitcoin is everything!" #BSV

• 
  Collegen Bob (@collegenbob) reported 19 minutes ago

  @giteaio @Malix_Labs @codeberg_org I'm building my own *** hosting because GitHub is a broken piece of ****. I can't imagine having your own and choosing to continue with MS for anything critical

• 
  Michael Brod (@adhoc97) reported 19 minutes ago

  satya intentionally cannibalizing github copilot with usage based pricing could go down as one of the biggest brain moves in history the reaction was as predictable as anything - customers hate it, it turns out tokens are expensive, and completely shifts the narrative on the market who can know see that without massively subsidized pricing (today), economics are brutal who does this macro narrative shift hurt the most?

• 
  Jamie Craik (@jscraik) reported 21 minutes ago

  I assume by real work you are on about GitHub projects? I was medically retired from the military and have been overcoming major health issues for the last 10 years?

• 
  Troyski (@MrTroy_) reported 23 minutes ago

  @HedgieMarkets Githubs new pricing is NOT reality. It was designed to shut down the service, but not before pocketing an extra 39USD from everyone before they burned their credit in one day and unsubscribed themselves. Github is a vile company, and they are the enemy of the people.