event

DeepSeek v4.1 Incident

8 items · started 2026-11-11 · ongoing (last activity 2026-11-16)

  1. I had 9% of my weekly usage limit left, which was set to reset today. I decided to use it wisely by selecting Composer and asking it to build a medium-sized feature (a reservation calendar).

  2. Follow-up to last week’s post, which ended on a claim I’d only half-proven: a written-down corpus raises the floor for every model and narrows the gap between them. So I ran it as a before and after.

  3. could not extract summary

  4. I have been getting this issue since yesterday. When I tried using Grok 4.7 it said it was not found.

  5. Hoping someone from the Cursor team sees this, because email support has gone quiet. What happened: - Between 17 and 23 October I was billed 23 separate mid-month invoices, totalling $2,829.91.

  6. We are currently on a legacy $40 team plan with 45 members. Before switching to the new $30 plan, which includes weekly limits, I decided to test an individual account to estimate our potential weekly token allowance.

  7. I use Cursor for daily coding (personal and professionally) and used to be very happy with Grok 4.7 being my default for everyday work. But this past week it is fumbling horribly and much more often.

  8. TL;DR: Same company, same task. Grok on grok.com writes it every time, in 42 seconds to 1 minute 6 seconds, and names its model (Grok 4.7).

← all threads