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:

• 
  🏍benyamin (@BenyaminHolley) reported 23 seconds ago

  Github for revops? what the heck is it? why would you use it? Exactly what the class Michael Slawson and I will be teaching with Maven will go through from 101 to some more esoteric use cases! this class is not talking about turning you into a software engineer. and honestly I dont think you need to be one to get something out of this. Most revops folks are probably better positioned than I was when I did all this stuff to get the most out of these systems. Vibe coding and revops are naturally best friends. 🧑‍🤝‍🧑🤝 But it all starts with github in my opinion. Github + vercel is sauce when it comes to building workflows and systems from scratch that vendors just don't provide in a bespoke fashion out of the box. a few things i've actually shipped, running off a repo deployed to production: • a slack bot that catches every reply across our outbound tools and pings the rep the second someone's actually interested, nothing dropped, nothing double-worked. has to be listening 24/7, that only works if it's actually deployed somewhere • built an attribution tool that mined a bunch of different sources (outbound tools, the crm, everything in between) to reconstruct the actual first and last touch on a deal, tell the story of the customer journey, and settle whether it should get credited to outbound at all • a bot that watches target companies for job postings matching our ICP, drafts the outreach, and drops it in slack for a rep to approve. reps just click yes • a dashboard watching every sending domain, catching placement problems, and auto-suppressing bad addresses before they tank a domain's reputation. that has to run continuously in the background, not something you'd ever run as a one-off script none of it needed a CS degree. needed ***, an agent, and somewhere to actually host the thing. but most people dont even know where to start, which is what we're going to show in this lesson 😎 if you want the walkthrough on how to build one of these for yourself, sign up for the class below 👇

• 
  Gary Alexander Devenay (@GaryDevenay) reported 2 minutes ago

  @poteto @bot GitHub login gives me a 500 after MFA

• 
  Tony Tong | Founder | Ancient Systems x AI (@tonytonggg) reported 6 minutes ago

  @KiraFeed The gap between a demo and a shipped agent is a pile of small bugs nobody films. I once filed a QA report against two of our own real GitHub PRs, cross tab navigation was broken and the nav bar height was inconsistent. That's the part these clips skip.

• 
  KD (@krisd23_) reported 8 minutes ago

  @0xkasana Basically the problem was from new changes implemented by GitHub that requires additional info for verification. That's it.

• 
  rftd (@rftd09) reported 9 minutes ago

  Single-use seals are what stop RGB from double-spending, binding a piece of contract state to one specific Bitcoin UTXO so spending it once closes the seal for good, permanently, no way to reopen it. Elegant design. Bitcoin's own proof of work backs the guarantee, which is a genuinely rare property for an asset layer that never touches the main chain directly. Here's what doesn't get repeated as often. Because only the parties involved validate a transaction, RGB inherits a real data availability problem, missing history or an unreachable counterparty can stall a transfer that a fully broadcast chain like Ethereum never has to worry about. The RGB team's own release notes go further. Their v0.12 changelog openly admits the earlier design running two separate seal types created serious complexity across the code, the API and user experience, and left behind what they themselves called a large attack surface. @utexocom launched on v0.11.1, the exact version carrying that dual seal design RGB's core developers later rebuilt specifically because of that admission. Shipping on the version right before your own protocol team publicly flags its attack surface isn't disqualifying, but it's the kind of detail that belongs in the audit trail, not buried in a GitHub changelog nobody outside the repo reads.

• 
  Afrah (@Afrah4Real) reported 10 minutes ago

  @TomasReimers No wonder why GitHub is always down

• 
  Rasbin Thapa (@rasbin__thapa) reported 10 minutes ago

  @Taniyatweets_ No problem at all. Github, migrated projects to codeberg Use neovim for coding FREE AI models are better than stack overflow Docker might be missed a bit

• 
  Alex McFarlane (@flipdazed) reported 11 minutes ago

  Call for contributors for a paper on DeFi liquidations... Liquidator roles have changed drastically since the addition of tokenised assets as DeFi collateral. Originally coordinators of infrastructure, they are now expected to provide balance sheet to absorb market and credit risk. The problem is that DeFi protocols have been built assuming assets can be sold instantly to a willing buyer. Whilst risk managers have taken this into account somewhat with LTVs, the protocol design has neglected the liquidator's need for a haircut to warehouse these risky assets. Our calls with leading liquidators this week confirmed what we suspected: most are unaware that protocols have hard constraints on the discounts that can be applied to collateral. This means that a slightly unhealthy position in a tokenised fund is unlikely to find any bidders, and will instead sit idle in the market. It is also possible that under certain conditions an asset can never be liquidated, as the maximum discount available is simply not enough for any rational actor. Different lending protocols have different constraints, but we found that in general none were well suited to clearing tokenised assets and funds in their default configuration. Some DeFi lending protocol teams, as well as some risk managers, have been aware of this issue and have been working on fixes. In talking to industry practitioners, one recurring theme was that levered credit positions rarely (if at all) got liquidated. The liquidation business for tokenised assets was therefore a low priority for most would-be liquidators, despite a surge in interest earlier this year. What this means is that for these assets, liquidators are relied upon to provide a service that is objectively negative expected value for them. We expect that some of the largest market operators, Aave for example, can justify this position as a service. But it gives reason to believe that the majority cannot, or would not, in a big market sell-off. The incentives are skewed against them, as being a liquidator in such conditions is effectively being a charity. We consider any third-party agreements (SLAs) with liquidators under such conditions to be largely spurious unless there are significant protocol changes: they are effectively deep out-of-the-money uncleared put options. This concerns us as retail exposure to DeFi increases through exchanges, PSPs and neobanks. It represents a critical fragility vector. Link to the GitHub repo below. It's still a draft, but we've spent about a week tidying it up so that it's ready for outside reviewers and contributions.

• 
  Abro (@br_huni) reported 12 minutes ago

  @initjean Just because of that bro, GitHub goes down every two hours💀💀

• 
  DGB Signal (@dgb_signal) reported 12 minutes ago

  DigiByte's official website was recently redesigned — cleaner, easier to navigate. It's open source, so anyone can suggest a fix or a translation as a pull request on GitHub; a maintainer reviews it before it goes live. #DGB #DGBCommunity

• 
  Fer (@harderthanfire) reported 14 minutes ago

  @thsottiaux Used it to create a self-healing distro build system for our linux distro. Now when a package version bump comes that fails a build it creates an agent that then fixes it and resubmits. It also has to calculate the full dependency tree and build in the correct order. It also self heals if the testing repos get a version conflict it will resolve that so our users never get such issues pushed to stable. The install-ability checker and the reverse and forward dependency resolution explodes in complexity and I wrote the same thing myself 3 times and the one I did with Codex is by far the most reliable. Literally saving us hours a week of time that volunteers would otherwise have to do as well as making updates much more reliable for our users. Just sad no Codex OSS acceptance for us (we are not on github) so it was all out of pocket.

• 
  Polsia (@polsia) reported 15 minutes ago

  Sentry tells you where it hurts. It doesn't write the fix. Plumebug watches live React and Flutter apps and ships audit-grade bug-fix PRs to GitHub — repro steps, QA test cases, full audit trail. Crash-to-PR on autopilot.

• 
  Serge Bulaev (@sbulaev) reported 16 minutes ago

  @WebSummit I am trying to apply for developer pass with my GitHub but getting error: {"error":"bad_verification_code","description":"The code passed is incorrect or expired."}

• 
  lolik (@Serhei060880602) reported 16 minutes ago

  @github honestly the real problem is reviewers not taking time to actually read them. breaking things up helps but if no one's gonna look anyway whats the point

• 
  Kirtesh (@AKirtesh) reported 21 minutes ago

  @DeepStarts plain *** with a self-hosted server or ssh, before github wrapped it with a ui