Kimi, Moonshot AI’s AI service, temporarily paused new K3 subscriptions after demand over a 48-hour period pushed its GPU capacity close to its limits. The company said it is prioritizing compute for existing subscribers, who remain unaffected, while adding capacity and planning to reopen subscriptions in batches. The supplied evidence supports a temporary restriction, but does not establish how long rationing will continue or when added capacity will arrive.
2026-08-08T18:32:37Z
The access-rationing episode remains historically corroborated, but weeks of reobservations have produced no policy change, first-party capacity update, or evidence that the original bottleneck still governs access. Comment growth around the local deployment is non-diagnostic, so this case has exhausted its useful monitoring horizon.
2026-08-06T18:31:42Z
The nominal attachment adds no diagnostic evidence beyond the established access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and whether inference capacity remains the operative constraint are unresolved; repeated engagement-driven review is noise.
2026-08-06T17:34:26Z
The nominal evidence trigger is only negligible engagement churn on the already-priced deployment and adds nothing about Moonshot’s current subscription policy or production capacity. Practical K3 rationing remains corroborated, but capacity as the continuing cause and the episode’s endpoint remain unresolved; keep monitoring event-driven.
2026-08-06T16:34:55Z
The nominal evidence trigger adds nothing diagnostic beyond the established access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; review only after an observable policy or capacity change.
2026-08-06T15:26:43Z
The nominal new-evidence trigger adds nothing beyond the already-priced access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; repeated attachment churn is noise.
2026-08-06T13:32:03Z
The nominal new-evidence trigger contains no identifiable substantive addition beyond the established access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; monitoring should remain event-driven.
2026-08-06T11:25:16Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved. Repeated attachment and engagement triggers are noise; revisit only after an observable access-policy or first-party capacity change.
2026-08-06T08:26:05Z
The apparent update is only negligible engagement churn on already-priced evidence and adds nothing about Moonshot’s subscription policy or production capacity. Practical K3 scarcity remains corroborated, but capacity as the continuing cause and the episode’s endpoint remain unresolved; monitoring should stay event-driven.
2026-08-06T07:24:44Z
No substantive evidence was added beyond the already-priced access reports and demanding deployment profile. Practical K3 scarcity remains corroborated, but Moonshot’s current subscription policy and capacity as the continuing cause remain unresolved; engagement-driven review is repetitive noise.
2026-08-06T06:25:04Z
The nominal attachment contains no identifiable new evidence beyond the established reports of rationed access and K3’s demanding serving profile. Practical scarcity remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; review should stay event-driven.
2026-08-06T05:24:50Z
The nominal attachment contains no identifiable evidence beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; repeated engagement-driven triggers are noise.
2026-08-06T04:28:50Z
The trigger adds no identifiable evidence beyond the established access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; defer review until an observable policy or first-party capacity change.
2026-08-06T03:26:59Z
The nominal evidence trigger adds no substantive information beyond the established access reports and deployment evidence. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; further review should be event-driven.
2026-08-06T01:25:55Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved. The repeated attachment trigger is noise; revisit only after an observable access-policy or first-party capacity change.
2026-08-06T00:28:41Z
The nominal evidence trigger contains no substantive addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and capacity as the continuing cause remain unresolved; ignore further churn until an observable policy or first-party capacity change.
2026-08-05T23:29:01Z
The nominal new-evidence trigger provides no identifiable addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; review only after an observable access-policy or first-party capacity change.
2026-08-05T22:26:40Z
The nominal new-evidence trigger contains no identifiable addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; further engagement-driven review is noise.
2026-08-05T21:29:33Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Treat repeated attachment and engagement triggers as noise and revisit only after an observable access-policy or first-party capacity change.
2026-08-05T20:30:39Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Engagement-driven triggers are repetitive noise; revisit only after an observable access-policy or first-party capacity change.
2026-08-05T19:35:59Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Repeated attachment triggers are noise; review only after an observable access-policy or first-party capacity change.
2026-08-05T18:32:08Z
No substantive new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. The repeated attachment trigger is noise; revisit only after an observable access-policy or first-party capacity change.
2026-08-05T17:31:14Z
The nominal attachment provides no identifiable evidence beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and whether inference capacity remains the operative constraint are unresolved; further engagement-driven triggers are noise.
2026-08-05T16:34:40Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Repeated attachment and engagement triggers are noise; revisit only on an observable access-policy or first-party capacity change.
2026-08-05T15:26:52Z
The nominal new-evidence trigger contains no identifiable addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; review only on an observable policy or capacity change.
2026-08-05T14:30:07Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Repeated attachment triggers are noise; revisit only on an observable access-policy or first-party capacity change.
2026-08-05T13:31:31Z
The nominal attachment adds no diagnostic evidence beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; ignore further engagement-driven triggers until an observable policy or capacity change.
2026-08-05T12:25:38Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved. Repeated attachment and engagement triggers are noise; revisit only after an observable access-policy or first-party capacity change.
2026-08-05T11:30:43Z
The nominal new-evidence trigger adds nothing diagnostic beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; repeated attachment churn is noise.
2026-08-05T10:26:14Z
No substantive new evidence changes the established picture: practical K3 access rationing is corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved. Repeated attachment and engagement triggers are noise; revisit only on an observable access-policy or first-party capacity change.
2026-08-05T09:28:49Z
The nominal new-evidence trigger contains no identifiable addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; review only on an observable policy or capacity change.
2026-08-05T08:30:54Z
No identifiable new evidence changes the case: practical K3 access rationing remains corroborated, but Moonshot’s current subscription status and whether inference capacity remains the operative constraint are unresolved. Repeated attachment and engagement triggers are noise; revisit only on an observable access-policy or first-party capacity change.
2026-08-05T07:25:09Z
The trigger contains no identifiable new evidence beyond the already-priced access reports and 16-node deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; ignore further attachment churn until an observable policy or capacity change.
2026-08-05T06:29:35Z
The nominal new-evidence trigger identifies no substantive addition beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and whether inference capacity remains the operative constraint are unresolved; review only on an observable policy or capacity change.
2026-08-05T05:25:51Z
The latest change is only negligible engagement on the already-priced deployment, adding nothing about Moonshot’s subscription status or production capacity. Practical K3 rationing remains corroborated, but capacity as the continuing cause and the episode’s endpoint remain unsettled; keep review event-driven.
2026-08-05T04:25:33Z
The trigger adds no identifiable diagnostic evidence beyond the already-priced access reports and deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and inference capacity as the continuing cause remain unresolved; repeated attachment churn should not prompt frequent review.
2026-08-05T03:28:47Z
No diagnostic evidence was added beyond the already-priced deployment and access reports. Practical K3 rationing remains corroborated, but Moonshot’s current subscription status and inference capacity as the continuing cause remain unresolved; engagement-driven triggers are repetitive noise.
2026-08-05T02:30:14Z
The nominal evidence trigger adds nothing diagnostic beyond the already-priced deployment and access reports. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and whether inference capacity remains the operative constraint are still unresolved; ignore engagement churn until an observable policy or capacity change.
2026-08-05T01:22:46Z
The trigger adds no identifiable evidence beyond the already-priced deployment and access reports. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy, capacity as the continuing cause, and the endpoint remain unsettled; monitoring should remain event-driven.
2026-08-05T00:27:31Z
The nominal new-evidence trigger identifies no substantive addition beyond the already-priced deployment and access reports. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy, the continuing role of inference capacity, and the endpoint remain unsettled; monitoring should stay event-driven.
2026-08-04T23:30:57Z
The nominal new-evidence trigger contains no identifiable addition beyond the already-priced deployment and access reports. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy, the continuing role of inference capacity, and the endpoint remain unsettled; monitoring should stay event-driven.
2026-08-04T22:28:57Z
The nominal new-evidence trigger adds nothing identifiable beyond the already-priced 16-node deployment. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy, the operative role of inference capacity, and the endpoint remain unsettled; continue event-driven monitoring only.
2026-08-04T21:26:13Z
The trigger adds no identifiable evidence beyond the already-priced 16-node deployment, which demonstrates K3’s demanding serving profile but says nothing new about Moonshot’s subscription policy or production capacity. Persistent practical rationing remains corroborated, while its current cause and endpoint remain unsettled; further review should be event-driven.
2026-08-04T20:25:31Z
The independent 16-node GB10 deployment demonstrates that full K3 can achieve useful throughput on substantial dedicated hardware, reinforcing the model’s demanding serving profile. It does not show that Moonshot has added equivalent production capacity or reopened subscriptions, so persistent rationing remains corroborated while its endpoint and operative cause stay unsettled.
2026-08-04T20:21:44Z
evidence attached: reddit.post.1vfl525 — A substantive independent deployment shows full K3 can now run at useful throughput on a 16-node GB10 cluster, materially contextualising the capacity bottleneck behind access rationing.
2026-08-03T20:30:42Z
The nominal new-evidence trigger contains no identifiable addition beyond the already-priced reports of rationed access, high serving costs, and capacity buildout. Practical K3 scarcity remains corroborated, but current first-party subscription restrictions and inference capacity as the continuing cause remain unresolved; monitor only for an observable policy or capacity change.
2026-08-03T19:22:02Z
Refreshed discussion only amplifies K3’s high serving cost and Moonshot’s reported compute buildout; it does not establish that first-party subscriptions remain restricted or that capacity is still the operative bottleneck. Practical rationing remains corroborated, but further review should wait for an observable access-policy or first-party capacity change.
2026-07-31T18:26:20Z
The trigger contains no identifiable evidence beyond the already-priced capacity-expansion report. Practical K3 rationing remains corroborated, but Moonshot’s current subscription policy and whether capacity rather than provider economics is the continuing constraint remain unsettled.
2026-07-31T17:28:16Z
No identifiable new evidence changes the case: practical K3 access remains rationed, but Moonshot’s current subscription policy and whether inference capacity rather than provider economics is the continuing cause remain unsettled. Repeated attachment and engagement triggers are noise; review only on an observable access-policy or first-party capacity change.
2026-07-31T16:28:57Z
The nominal new-evidence trigger adds nothing identifiable beyond the already-priced 20,000-GPU cluster report. Practical K3 access constraints remain corroborated, but Moonshot’s current subscription status, the capacity bottleneck’s severity, and the reopening timeline remain unsettled.
2026-07-31T15:28:06Z
The reported 20,000-GPU Alibaba cluster makes Moonshot’s capacity-expansion effort more concrete, but does not show how much compute serves K3 inference or that rationing has ended. Persistent practical access constraints remain corroborated, while the bottleneck’s current severity and reopening timeline stay unsettled.
2026-07-31T15:21:44Z
evidence attached: hn.story.49122838 — The reported 20,000-GPU Alibaba cluster materially contextualizes Moonshot's effort to expand Kimi inference capacity.
2026-07-31T05:22:21Z
The nominal new-evidence trigger adds no diagnostic evidence beyond the already-priced quota report. Practical K3 access remains rationed, but Moonshot’s subscription status and whether capacity rather than provider economics is the continuing cause remain unsettled.
2026-07-31T01:24:53Z
The nominal new-evidence trigger adds nothing diagnostic beyond the already-priced quota report. Practical K3 access remains rationed, but Moonshot’s subscription status and whether capacity rather than provider economics is the continuing cause remain unsettled.
2026-07-30T16:25:42Z
The latest trigger adds no diagnostic evidence beyond the already-priced report of rapidly exhausted quotas. Practical K3 access remains rationed, but Moonshot’s current subscription policy, the role of inference capacity versus provider economics, and the reopening timeline remain unsettled.
2026-07-30T14:29:33Z
The new user report adds a time-separated symptom of rapidly exhausted K3 quotas across third-party API and subscription channels, strengthening the view that practical access remains rationed. It does not establish that Moonshot’s own subscriptions are still closed or that inference capacity, rather than provider economics and plan design, is the continuing cause.
2026-07-30T14:21:34Z
evidence attached: reddit.post.1vatzo6 — Independent user report of rapidly exhausted API and subscription limits corroborates continuing Kimi K3 capacity rationing.
2026-07-28T21:25:59Z
The trigger adds no identifiable evidence beyond the established subscription pause, later waitlist, and broader third-party availability. First-party rationing remains corroborated, but its current capacity cause and endpoint remain unsettled; ignore engagement churn until an observable policy change or first-party capacity update.
2026-07-28T16:26:40Z
No substantive new evidence changes the established picture: first-party access rationing remains corroborated by the subscription pause and later waitlist, while the continuing capacity bottleneck and reopening timeline remain unproven. Treat repeated attachment and engagement triggers as noise until Moonshot changes access policy or provides a capacity update.
2026-07-28T15:27:10Z
The nominal attachment adds no diagnostic evidence beyond the established pause, waitlist, and third-party availability. First-party rationing remains corroborated, but its current capacity cause and endpoint remain unsettled; ignore further engagement churn and review only on an observable policy or capacity change.
2026-07-28T14:30:18Z
The nominal new-evidence trigger contains no substantive addition beyond the established subscription pause, later waitlist, and broader third-party availability. Persistent first-party rationing remains corroborated, but its capacity cause and endpoint remain unsettled; engagement-driven review is now repetitive noise.
2026-07-28T13:33:37Z
The nominal new-evidence trigger contains no substantive addition beyond the established pause, waitlist, and third-party availability. Persistent first-party rationing remains corroborated, but its capacity cause and endpoint remain unsettled; further review should be event-driven.
2026-07-28T12:27:28Z
The only observable change is minor comment churn on Ollama’s separate metering of K3, which adds no evidence about Moonshot reopening subscriptions or expanding capacity. First-party rationing remains corroborated, but its current cause and endpoint remain unsettled; monitoring should stay event-driven.
2026-07-28T11:25:28Z
The nominal evidence trigger contains no substantive addition beyond the established pause, waitlist, and third-party availability. Persistent first-party rationing remains corroborated, but its current capacity cause and endpoint remain unsettled; keep monitoring event-driven.
2026-07-28T10:25:11Z
The nominal new-evidence trigger adds nothing diagnostic beyond the established subscription pause, later waitlist, and broader third-party availability. Persistent first-party rationing remains corroborated, but its current capacity cause and endpoint remain unsettled; continue event-driven monitoring only.
2026-07-28T09:26:38Z
The nominal new-evidence trigger identifies no substantive addition beyond the established pause, waitlist, and third-party availability. First-party rationing remains corroborated, but its current capacity cause and endpoint remain unsettled; further review should be event-driven.
2026-07-28T08:27:54Z
The trigger supplies no identifiable new evidence beyond the established pause, waitlist, and broader third-party availability. First-party rationing remains corroborated, but its present capacity cause and endpoint remain unsettled; keep monitoring event-driven.
2026-07-28T07:27:11Z
No identifiable new evidence changes the case: the initial pause and later waitlist still corroborate persistent first-party rationing, while neither Moonshot’s current capacity constraint nor a reopening timeline is established. Third-party availability and engagement churn do not resolve or strengthen that duration claim.
2026-07-28T06:23:31Z
No identifiable new evidence changes the picture: Moonshot’s first-party rationing remains corroborated, while broader third-party access does not establish that its capacity constraint has ended. Keep the case event-driven pending a subscription reopening, renewed restriction, or first-party capacity update.
2026-07-28T05:22:08Z
The refreshed discussion only repeats that K3 is expensive to serve and adds no evidence of continued first-party restrictions, reopening, or Moonshot capacity expansion. Third-party availability broadens fallback access but leaves the corroborated first-party rationing episode and its capacity explanation unresolved.
2026-07-28T02:23:07Z
Telnyx availability shows K3 access broadening through third-party infrastructure, but it does not establish that Moonshot reopened subscriptions or relieved its own capacity bottleneck. Persistent first-party rationing remains supported, while its cause and endpoint stay unsettled.
2026-07-28T02:21:08Z
evidence attached: hn.story.49076505 — A third-party inference provider making Kimi K3 available is independent evidence that access is broadening, potentially challenging the case's expectation of continued rationing.
2026-07-27T23:25:03Z
The comment update only reiterates that K3 is expensive to serve; it does not show any further restriction, reopening, or Moonshot capacity expansion. Persistent rationing remains corroborated by the subscription pause and waitlist, while its current cause and duration remain unsettled.
2026-07-27T22:26:43Z
Ollama’s decision to meter K3 separately supports the broader conclusion that serving it is unusually costly, but does not independently show that Moonshot’s subscriptions remain restricted because of capacity. Persistent rationing is still corroborated by the pause and waitlist, while its current cause and reopening timeline remain unsettled.
2026-07-27T22:21:19Z
evidence attached: reddit.post.1v8f0c4 — K3 being excluded from Ollama’s subscription and routed to paid overage access is direct evidence of constrained or premium access.
2026-07-25T15:22:52Z
The nominally new attachment contains no identifiable evidence beyond the existing waitlist, so persistent access rationing remains supported without clarifying whether inference capacity is still the bottleneck or when subscriptions will reopen. Keep monitoring event-driven; repeated attachment and engagement triggers add no urgency.
2026-07-25T14:24:51Z
The 48-hour staleness check adds no evidence beyond the existing waitlist, so ongoing access rationing remains supported while its capacity cause and reopening timeline stay unsettled. Keep the case event-driven; Scott’s up-vote sustains medium relevance, but minor engagement churn adds no urgency.
2026-07-22T13:31:38Z
The trigger adds no diagnostic evidence beyond the already-priced waitlist, so persistent access rationing remains supported without clarifying whether inference capacity is still the bottleneck or when subscriptions will reopen. Scott’s up-votes sustain medium practical relevance, but unchanged engagement does not increase maturity or urgency.
2026-07-22T06:24:08Z
The trigger provides no identifiable evidence beyond the already-priced waitlist, so persistent access rationing remains supported but the capacity-bottleneck explanation and reopening timeline remain unsettled. Keep monitoring event-driven; engagement churn does not increase maturity or urgency.
2026-07-21T23:29:11Z
The latest trigger adds no identifiable evidence beyond the already-priced waitlist, so persistent rationing remains supported without clarifying whether inference capacity is still the bottleneck or when access will reopen. Scott’s up-votes sustain medium practical relevance, but comment churn does not raise maturity or urgency.
2026-07-21T22:21:32Z
No evidence beyond the already-priced waitlist shows further tightening, reopening, or added capacity, so the duration hypothesis is unchanged. Scott’s repeated up-votes raise its practical relevance, but engagement churn does not strengthen the underlying capacity explanation.
2026-07-21T19:29:58Z
The newly observable waitlist shows that access rationing persists beyond the initial subscription pause, providing a second, time-separated line of evidence for the duration hypothesis. It still does not independently establish that inference capacity is the current bottleneck or indicate when access will reopen.
2026-07-21T19:21:42Z
evidence attached: reddit.post.1v2rfwn — A new Kimi Code waitlist is direct evidence that Kimi is still rationing access amid capacity constraints.
2026-07-21T18:30:01Z
The nominally new attachment contains no diagnostic evidence of continued restrictions, reopening, or added capacity, so the case remains an unresolved duration question rather than a strengthening capacity signal. Stop engagement-driven review and wait for an observable subscription-policy change or first-party capacity update.
2026-07-21T15:34:14Z
The attachment provides no diagnostic evidence that subscriptions remain restricted, have reopened, or that added capacity has arrived. The case remains a supported temporary pause with unresolved duration and should be monitored only for an observable policy change or first-party capacity update.
2026-07-21T13:25:25Z
The trigger adds no identifiable evidence that subscriptions remain restricted, have reopened, or that added capacity has arrived. The case remains a supported temporary pause with unresolved duration and should stay event-driven rather than react to repeated engagement updates.
2026-07-21T12:24:34Z
The trigger contains no identifiable new evidence about subscription reopening, continued restrictions, or added inference capacity. The case remains an unresolved duration question and should be reviewed only on an observable policy change or first-party capacity update, not repeated attachment triggers.
2026-07-21T10:24:57Z
The trigger adds no identifiable evidence about subscription reopening, continued rationing, or expanded capacity; the case remains a supported temporary pause with unresolved duration. Repeated evidence-only or engagement-only triggers are non-diagnostic, so monitoring should remain event-driven.
2026-07-21T07:24:42Z
No substantive new evidence establishes whether subscriptions remain restricted or added capacity has arrived; the repeated trigger is non-diagnostic. Keep this event-driven and revisit only for a first-party capacity update or observable subscription-policy change.
2026-07-21T04:24:34Z
The attachment adds no new diagnostic evidence about subscription reopening, continued rationing, or expanded capacity. The case remains an event-driven duration question; repeated engagement or unchanged evidence should not trigger another review.
2026-07-21T02:23:34Z
The trigger identifies no substantive new evidence about reopening, continued restrictions, or added capacity. The case remains an event-driven duration question, and repeated attachment or engagement updates should be treated as noise until an observable policy change or first-party capacity statement.
2026-07-21T01:25:51Z
No identifiable new evidence shows whether subscriptions remain restricted or added capacity has arrived. The case remains an event-driven duration question; engagement-only triggers add no signal and should not prompt frequent review.
2026-07-20T23:24:40Z
The trigger contains no identifiable new evidence about subscription reopening, continued restrictions, or added inference capacity. The case remains a supported temporary pause with unresolved duration; engagement-only reobservations should be ignored until an observable policy change or first-party update.
2026-07-20T22:25:19Z
The trigger attaches no identifiable new evidence about reopening, continued restrictions, or added capacity, so it does not change the supported temporary-pause interpretation. Engagement-driven reobservations are repetitive noise; monitor only for an observable subscription-policy change or first-party capacity update.
2026-07-20T21:24:26Z
The attachment adds no diagnostic evidence beyond the established temporary pause; it does not show whether subscriptions remain restricted, have reopened, or whether capacity expanded. The case should remain event-driven, with engagement-only triggers ignored until an observable policy change or first-party update.
2026-07-20T20:28:12Z
The trigger contains no identifiable evidence that subscription restrictions persist, have reopened, or that capacity has expanded. The case remains a supported temporary pause with an unresolved duration, and should now be event-driven rather than revisited on engagement changes.
2026-07-20T19:24:25Z
The trigger adds no diagnostic evidence about whether subscriptions remain restricted or capacity has caught up; the attached material still only supports the original temporary pause. Repeated engagement-only reobservations are noise, so wait for a first-party update or observable subscription-policy change.
2026-07-20T18:27:57Z
The trigger supplies no identifiable new evidence about subscription reopening, renewed restrictions, or added capacity. The temporary pause remains supported, but its continuation is unresolved and repeated engagement-only updates are non-diagnostic.
2026-07-20T17:34:02Z
The trigger adds no identifiable diagnostic evidence beyond the known temporary pause and derivative discussion. Continued rationing remains unresolved, but repeated engagement-only reobservations are noise; wait for a first-party capacity update or observable subscription-policy change.
2026-07-20T16:26:54Z
No new diagnostic evidence shows that subscription rationing persists or that added capacity has arrived; the material remains derivative or unrelated to subscription reopening. The case is unchanged and should wait for a first-party capacity update or an observable access-policy change.
2026-07-20T15:38:08Z
The new Reddit post is derivative community retelling, not independent confirmation that restrictions persist or that capacity remains constrained. It adds no diagnostic evidence beyond the established temporary pause, so the case stays cold pending a first-party update or observable reopening.
2026-07-20T15:21:44Z
evidence attached: reddit.post.1v1o00v — This provides additional community-level reporting that K3 signups were paused after demand exceeded available inference capacity.
2026-07-20T14:27:17Z
No diagnostic evidence was added about continued subscription restrictions or new capacity; the case remains a supported temporary pause with an unresolved duration. Repeated engagement-only reobservations should no longer trigger frequent review.
2026-07-20T13:25:59Z
The attachment contains no new diagnostic evidence about whether subscriptions remain restricted or added capacity has arrived. Repeated reobservations are noise; revisit only for a first-party capacity update or an observable reopening or renewed restriction.
2026-07-20T12:27:36Z
The attachment adds no diagnostic evidence beyond the known temporary pause and broad K3 launch; it still does not show whether subscription restrictions persist or capacity has caught up. Repeated reobservations are now noise, so defer review until a first-party capacity update or observable subscription reopening or restriction.
2026-07-20T11:24:54Z
The newly attached material remains non-diagnostic about whether subscriptions are still restricted or added capacity has arrived. Repeated reobservations are not changing the case, so defer further review until an observable reopening, renewed restriction, or first-party capacity update.
2026-07-20T10:21:52Z
The attached evidence remains non-diagnostic: it confirms K3’s broader launch, not whether new subscriptions are still restricted or added capacity has arrived. Repeated engagement updates are amplification rather than evidence, so only a first-party capacity statement or observable subscription reopening should move the case.
2026-07-20T09:38:00Z
The attachment adds no diagnostic evidence beyond the known launch and temporary subscription pause, so continued rationing remains unconfirmed rather than newly strengthened. Further engagement is repetitive amplification; only a reopening, renewed restriction, or first-party capacity update would change the case.
2026-07-20T09:22:21Z
No genuinely new evidence establishes that subscription rationing continues or that added capacity has arrived; the attached launch material remains non-diagnostic. The case stays a supported temporary pause but an unresolved duration claim awaiting a first-party reopening or capacity update.
2026-07-20T08:18:36Z
The supposedly new attachment is unchanged launch evidence and still does not establish whether subscriptions remain restricted or capacity has caught up. The case remains a supported temporary pause but a cold, unresolved duration claim awaiting a first-party reopening or capacity update.
2026-07-20T07:24:54Z
The negligible engagement change and lack of new subscription or capacity information add no evidence that rationing persists. Broad K3 availability still does not answer whether new subscriptions have reopened, so the case remains cold pending a first-party update or observable access change.
2026-07-20T06:31:51Z
The web and app launch confirms broad K3 product availability but does not show that new subscriptions reopened or that Moonshot’s added capacity has caught up. It therefore neither corroborates nor disproves continued subscription rationing, leaving the case dependent on a first-party capacity or reopening update.
2026-07-20T06:04:40Z
evidence attached: reddit.post.1uy3a0q — The web and app launch provides direct evidence about K3 availability and whether Moonshot can serve initial demand.
2026-07-20T05:52:30Z
The attached evidence reiterates the already-grounded temporary subscription pause but adds no independent indication that rationing persists or when capacity will catch up. Continued engagement is repetitive amplification, so the case remains cold pending a reopening, extension, or first-party capacity update.
2026-07-20T05:22:25Z
Grounding upgrades the report from a purely anecdotal capacity claim to a supported temporary subscription pause while Moonshot adds compute. The duration and reopening pace remain unknown, so this warrants monitoring rather than corroboration.
2026-07-20T04:47:10Z
grounded: converges/low — Kimi’s temporary capacity rationing reinforces Scott’s existing use of provider-neutral gateways, explicit fallback paths, and cost-tiered routing as protection
2026-07-20T04:21:13Z
No genuinely new evidence was attached; the negligible score increase on the same Reddit post does not confirm continued rationing or its cause. The case remains a cold, single-source operational claim awaiting first-party confirmation or observable subscription changes.
2026-07-20T03:21:06Z
The tiny engagement increase adds no independent evidence that rationing persists or that capacity remains constrained. This is repetitive amplification of the original report, so the case stays speculative and cold.
2026-07-20T02:20:52Z
The signal remains a single Reddit report, with anecdotal OpenRouter latency adding context but not independent confirmation of Kimi’s capacity constraints or their duration. Engagement has flattened, so this is repetitive amplification rather than evidence of continued rationing.
2026-07-20T01:36:10Z
case created — The reported subscription pause is a concrete operational consequence of K3 adoption and is distinct from its capability and pricing cases.