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:

• 
  Brian (@Brian2shv) reported 3 minutes ago

  @IntCyberDigest several years back I report to coinbase , github Linked Metadata Fix’s from open source . Email both on same day stating , While Was In mu account s. All language Was in Korean Language Metrio math From login to web3 aws Github I was blocked by both Coinbase github Spam aggregation Month band Never really Had coinbase connection github spam Few times once my data An account had said I deleted my profile deleted repository Month band or three month band

• 
  Soumyaranjan Panda (@Soumyapx) reported 4 minutes ago

  GitHub Models getting shut down is a useful correction. The company that owns the default home for code tried to become a model access layer. Now the playground, model catalog, inference API, and BYOK path are all being retired together. They even scheduled brownouts before the cutoff. That usually means one thing: this was never core. And that is the real critique. GitHub had one of the best distribution wedges available. Repo context. Pull requests. CI. Issues. The place where code already lives. If there was any company that could make model access feel native to software work, it was GitHub. Instead it looked too much like a showroom. A catalog is easy to demo. A playground is easy to screenshot. An inference endpoint makes the product map look complete. But none of that answers the harder question: why should the model layer belong to GitHub instead of the cloud, the IDE, or the app itself? Copilot at least has an answer. It sits in the work. Models did not. So now the migration path is basically: use Microsoft Foundry for model access, use Copilot if you want AI on GitHub. That is a clean org chart. It is not a great product thesis. My read is simple. Developers do not want one more place to sample models. They want the model to show up where the decision already is. GitHub had that surface. It just shipped the wrong abstraction.

• 
  Glenn 'devalias' Grant (@_devalias) reported 10 minutes ago

  @thsottiaux IMO it should be a default part of the repo's agent instructions / GitHub actions / similar that raised PR's should explicitly cross-link to related issues raised; ideally with 'closing keywords' / etc so that GitHub's awareness features can actually work as intended.

• 
  Open_ERV (@open_erv) reported 11 minutes ago

  Nice! I think the self tapping screws, or the machine screws right into the plastic, might last a surprisingly long time. In my experience they tend to, the plastic squishes around but rarely actually leaves the hole. I can also use a slightly longer screw if the old one doesn't fit, for instance. My phone doesn't have a barometer, but I have an sps30 sensor I could use... In the past, I used a similar approach, using slices of the tw4 heat exchanger in a pipe as the resistance elements, and the pressure sensor after the flow restrictor. They can be stacked to form greater or lesser resistance. That's a hassle to print though. Again the only purpose was to compare fans, in that case I also got flow measurements with a hot wire anemometer. Yesterday I was thinking of how I might do this kind of thing, and I think I might try a paddle with a weight, and suspended on a wire. The paddle in the airflow path, and then three different flow restrictors. The air would come through the flow restrictor and hit the paddle. It would not be able to measure actual static pressure. The position of the paddle would rotate until equilibrium was achieved with the air hitting it. It might bounce around, though. The whole thing would have to be level. I like this kind of thing because it depends only on weights and airflow, not for cost but for the natural accuracy and repeatability that can bring. I tried using inclined manometers which similarly draw more directly from natural phenomena, but they did not work out well, for pressure measurement n this context. The problem with a non inclined manometer is that the fluid is too dense, you have a very hard time measuring only a couple pascals, and repeatably. The inclined manometer is better but has to be level, and the hysteresis caused by the meniscus is a real problem. In the end I switched to the sps30 for pressure, and it's actually a flow measurement device in disguise. It has a tiny hole in it and measures the airflow through the hole, using the same principles as a hot wire anemometer, then computes pressure. But the sps30 is not needed for this kind of thing. Indeed, since the only challenge is to match fans, I would not bother with calibration, you can just measure a bunch of fans and match them from that. After my exploration of this kind of thing for some time, my favorite method to try in the future is the use of a camera and some kind of floating or high drag to weight ratio object, perhaps a bit of dryer lint or some fluffy seed stuff. I would print a rig to hold the camera, and focus the camera at a fixed point, hold a ruler up to determine the mm per pixel (the ruler can be removed to not affect airflow), and then at the same distance from the camera, release the fluffy stuff with some tweezers. Frame by frame analysis could be used just by eye to determine m/s. I found some stuff for the phone that does this, called frameskip, but you could just transfer it to the computer, kind of nice to be able to do it on your phone. Then you would need various flow restrictors with known properties. I found it to be awkward and not as easy as I thought, but I think it has potential for more precise measurements, perhaps calibrating this kind of thing with a complicated but low cost procedure. It could also be used to measure the airflow at the intake of the actual air purifier, perhaps. I like this more than a hot wire anemometer even, because it's pretty closely tied to things we know are highly accurate, the timing of the phone and the camera (and the yardstick/ruler/measuring tape). I made a $1 anemometer, which is shared in the BQAP github repository (requires a pico or similar to read it), which appears to have good repeatability and precision in the 0.1 m/s range, and I figured out a way to calibrate it. I swing it on an arm of known length at known speed through still air. I haven't done it with that anemometer yet, but I used the method to validate an off the shelf hot wire (thermistor) anemometer and it went well.

• 
  Yazi (@Yazi_27) reported 11 minutes ago

  @bil0090 Well im sure I tested with workflows too, but this issue has been widely reported on github claude code, I should maybe try and run it again.

• 
  Siriux Design (@SiriuxDesign) reported 13 minutes ago

  My finding, Claude is amazing. I just gave it a detail prompt and handed over my github connection and it did its thing. It worked out all the backend stuff and connections. Troubleshot its own problems like a developer. Took about 1.5 days for this conversion.

• 
  Stephen Turner 🇬🇧🇺🇦 (@LittleBrainz) reported 14 minutes ago

  @code Without support for OpenAI OAuth, VS Code and GitHub Copilot have become deeply disappointing. I used to be a strong supporter of the open nature of VS Code, complete with a Pro account. The dumbing down forced me to cancel it.

• 
  Ironic Ape (@Ironic_Ape) reported 18 minutes ago

  @thsottiaux @jxnlco BTW love 5.6 it’s a massive improvement. Few things I’ve noticed 1. On chat web - it seems to now push many “finished” push notifications to my phone I think each time an agent finishes one task in the longer task? - annoying. 2. Goals seem to get stuck if they get steered - the solve the steer request but often then go back and try and solve the same steer over and over vs moving back to the main goal 3. Not a major but it would be great if I could get a push notification to my phone if it detects my main codex machine has gone to sleep or lost connection, would be cool to have a wake on Lan type feature from mobile 4. Viewing app and outputs on mobile is a bit of a pain - when using the mobile app it should know that when I launch the app to view to give me a version that will work remotely and far to frequently if I ask it to open the app, it will open a dead page not checking the local server (and all supporting servers needed for the app to run) are running - really annoying. 5. If I turn pets off in settings - I’d really love they stay off - they keep turning on 6. The little preview browser window popup - not sure the point - it would be useful if I could click on it to expand and open the larger browser view to actually see explore and see 7. Lots of - capacity reached (understandable!) - add a setting and allow the user to set their preferred “secondary / back up model” so it will automatically try that IF the user has approved the use of a fall back model so builds can continue, some tasks I’d be pissed off if it did it automatically so I want the choice in settings 8. All resets as banks (greatful BTW!) 9. The in built browser keeps cutting the right hand side of the app view off - works fine in other browsers but the way it renders frequently cuts off like 3cm of the right side of the app. 10. Add a good local or unlimited agent model natively in the app no setup needed - have codex check the hardware requirements and have it setup the most suitable local model (I do have a bridge setup with Ollama but it’s just not as smooth - it’s annoying not being able to do anything after usage runs out - stuff like “open the app” or push to “GitHub” a set of basic commands really need to be unlimited and I won’t be topping up credits anymore given the massive disparity in cost vs subscription, I would however pay for a full banked reset (which didn’t adjust my normal reset timings I.e. when it’s meant to reset (before purchase the same date and time retains static instead of resetting it and then just adds another banked reset ready to use when the paid one runs down so basically resets have no expiration and run in parallel to paid subs) or just give all pro subscribers a totally unlimited agent 🙏 10. Keep up the amazing work! Literally helping make dreams come to life with a mouse click. Can’t explain how awesome codex is🤯

• 
  Mike Williams (@Miwico1) reported 18 minutes ago

  @TheAhmadOsman @CoreyGallon @MikeBradleyAI Still as difficult as it ever was for non technically older guy. Would love to figure this out. sending me to A github page does not help. what the heck do i do with that page. When the ai tech engineer types can dumb down the process with actual steps, local AI will be adopted

• 
  oruuke 🎀 折る受け (@oruuke) reported 21 minutes ago

  wtf is github down again?????

• 
  CryptoDev (@JharolOzuna) reported 23 minutes ago

  My account (jjharoll) has been flagged for a month, causing a critical production outage for my clients' SaaS platforms. Ticket #4487157. Please help! @github

• 
  Kaspa Daily (@DailyKaspa) reported 23 minutes ago

  Two weeks since Toccata went live on Kaspa mainnet. I checked the actual developer numbers instead of the vibes. Here's what the data says: — New Kaspa repos on GitHub: 39 in July 1–14 alone, vs 58 in all of June. Fastest monthly pace this year (March was 52, April 78, May 70). — Covenant-specific repos running at roughly 2x the pre-fork rate. — Silverscript: 21 forks against 42 stars, a 1:2 ratio means people are cloning to build, not bookmarking. 15 PRs/issues in the last weeks, and external contributors are now landing code: a Groth16 verifier builtin, typed sig-check builtins, an RFC for cross-contract validation. One issue is literally titled "from building a mainnet contract." That's the signal you want, outsiders hitting real problems and reporting back. What actually shipped in 14 days: the first covenant explorer (kascov), a covenant-based KAS vault, a native L1 covenant token, a covenant pattern library, a wallet standard, a Swift SDK, a testnet raffle dApp, several other projects under development. Most interesting pattern: three independent projects converged on the same idea, covenants as spending guardrails for AI agents. An x402 payment protocol binding, two agent wallets where the AI can only spend inside covenant constraints. And the community just voted $25K toward an AI agent hackathon at Imperial College targeting 1,000+ devs. The agentic-payments thesis is forming bottom-up. Core isn't idle either: Silverscript pushed commits this week, template hash hardening, reproducible builds. That's pre-production housekeeping, not feature chasing. Meanwhile discussion has shifted from price to fundamentals: the $6M developer fund and covenant atomic swaps are the topics now. Caveats, because they matter: Silverscript is unaudited and still landing breaking changes. Devs report RPC friction on deployment, up to 11 retries in some cases. And absolute numbers are small: this is dozens of motivated builders, not thousands. No major outside team has announced a covenant product yet. But two weeks in, the shape is clear: infrastructure activated, tooling hardening, and builders showed up without being paid to. The Q3 question is whether that compounds.

• 
  majorjayyy1 (@Majorjayyy1) reported 24 minutes ago

  Whatever my next BIG vulnerability affecting Android is. Isn’t going to any oem, isn’t going to vrp. It’s going on GitHub and I’ll share it here. The process is too slow, uncoordinated, full of ***** patches. I’m tryina see something. Maybe some small ones too cuz fck it

• 
  Hifihedgehog (@hifihedgehog) reported 31 minutes ago

  @kimmonismus I tried GPT-5.6 Sol again just to humor myself and it honestly performed worse than Opus 4.8 with one of my most technical codebases, which happens to be a FOSS project on GitHub. After doing a scan of the codebase and migrating memory over from Claude Code, I sent Codex to a routine code audit as Opus 4.8 would. With the Sol model and Ultra thinking enabled, GPT-5.6 introduced serious regressions that would have caused game controller output issues (for things like LEDs and lighting that get relayed back to the physical controllers from the parent virtual controller) with controller profile changes had I shipped its AI slop. I am honestly not all too impressed with it and I think a lot of the hype is from inexperienced vibe coders who do more boilerplate-esque code. It does well with simple tasks or as a subagent to Opus 4.8 or Fable 5, but it is not something I would use in an engineering setting with my private repositories. This experience makes me more excited for Opus 5 than anything.

• 
  Brian Sparker (@PeerReview) reported 34 minutes ago

  github stars are agent SEO now. an agent picking an MCP server can't read your code, so it trusts your star count. recruiters and investors already do. so fake stars stopped being vanity. they poison the cheap signal everyone leans on to choose.