While kbin.social’s site mentioned that they were migrating to a new provider, and as a result, the site might be experiencing some issues, kbin.social has been serving up a similar HTTP 50x errors, and that migration message for well over a month, if not more.
What happened?
Mbin is indeed the way forward that the community came up with, and pretty much everything still up now runs mbin instead of kbin.
That said, it’s hypothetically possible that the investor of kbin returns tomorrow, fully recovered, and starts to maintain kbin separately from mbin. Very unlikely, but…