Live data from Hacker News

Moonshot AI suspends new subscriptions due to Kimi K3 demand

twitter.com

51–60 of 118 posts

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#51

> Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected. Such a beautiful paragraph to read, a company that prioritizes their current customers and focus on keeping them satisfied instead of just focusin…

So this is what Hetzner should have done instead of raising prices to calibrate supply and demand?

If anything, this suggests Kimi K3 is underpriced, forcing rationing of compute resources. Anthropic even struggles to avoid 503 errors at the $50/mtok point.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#52

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#53
post #30

Earlier quoted context omitted.

I had the _exact_ same problem. Got the 20 USD/month subscription from Kimi.com (paid annually), exhausted my 5-hour quota with a simple prompt on OpenCode + Kimi K2.7 through their API. Cursor got the same prompt done in minutes. According to their web interface, I'm also on 23% of my weekly usage. That feels crazy, as I do a lot more than that on the 20 USD Cursor plan, and never got even a warning. I thought OpenC…

Moonshot AI has two subscriptions archetypes and the one they link to from their main page is the subscription for the web interface/research/agents/OpenClaw (that they host for you) There is a small link below the tiles for these plans saying something "looking to use it for code? Use Kimi code" and upon clicking you'll get a basically identically looking subscription page with different sub prices and more quota No…

That doesn’t appear to be the case anymore. They just have one set of plans: Allegreto, modereto, etc which apply to both the chat app and the coding apps.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#54
post #43
post #42

Earlier quoted context omitted.

I remember people being so upset when GitHub did exactly this. It was the right move then and now!

People were not upset at Github for pausing new signups. It was the existing customers upset at token-based billing replacing their effectively unlimited $40 a month subscription.

People were absolutely upset with Github for pausing new signups. The token-based billing was a separate thing.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#55

I think the Kimi thing is super cool, especially that they have so many RNN/linear attention layers (3x more than they have full attention). I haven't yet tried it though. It seems like it would be extremely reasonable for long context tasks and I guess this fits the times. I suspect that the reason it has so many parameters is the same reason that compute optimal xLSTMs have some many parameters, and the success of…

Is it an RNN or a state space one, like qwen or there was an arch called mamba if I remember correctly. Or it might be closer to RWKV.

Edit: I checked and it is similar to linear delta net uses by qeen.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#56

I wonder if anthropic and openai will remain relevant simply due to the fact that they're the only ones that are able to handle this much demand for the forseeable future? My bet would be that companies would probably not be too happy with employee time being wasted on outages and other related issues when it already costs so much.

I expect what's most likely to happen is that either Anthropic or OpenAI end up becoming a vendor of record for the government and get a bailout. And then their whole business model will be serving use niches which would be considered too sensitive for Chinese models. That's the only plausible business model I can see here.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#57

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

I have Claude workflows that it takes 30+ minutes to get any feedback while it thinks

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#58

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

Well, to be clear, there was some feedback (e.g. it was calling subagents and printing some thinking messages).

That said, yes, it is pretty common for me to wait 10, 20 and sometimes even 30 minutes without steering the model or looking at what its doing. I usually write a pretty detailed prompt at the start that describes the issue, the usecases, the testing to do and the definition of success; then I sometimes ask it to draft a plan and give it a read, but after that I just press enter, let it run and come back when it's done.

In the end I do a manual review, both of the code and the functionality, but most of the time I get exactly what I wanted.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#59

> Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected. Such a beautiful paragraph to read, a company that prioritizes their current customers and focus on keeping them satisfied instead of just focusin…

i'd clm down; the VCs are pumping so much money into AI, this might just be OpenAI/Anthropic pummping money into the token burning machine to try and distill their datasets (turn tables of course).

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#60

> Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected. Such a beautiful paragraph to read, a company that prioritizes their current customers and focus on keeping them satisfied instead of just focusin…

> a company that prioritizes their current customers and focus on keeping them satisfied instead of just focusing on fast growth. I always hated how the "Login" button is smaller on every website than the "Sign Up" button.

Same for me too. Hunting for the login whilst a massive splash screen for sign up
Post reply on HN