Launch-day reports · historical record
Historical user reports do not measure current Pareto or the absent alias
These accounts concern the R1 launch period. R5 closed routine monitoring after finding no reopening trigger; it made no requests. Do not use these reports as current measurements of paid Pareto or either former identifier.
Read each report as a report, not a rate. Reported 429s, slowness, loops, and errors have incomplete conditions. R1 probes ended at DNS; R2 through R5 made no authorized inference request.
| Author / source | Task / route / settings | Reported result | Boundary |
|---|---|---|---|
| Scott @scottstts | “Monica’s apt test”; reasoning high; route, prompt, and raw trace absent. | Reported a failure after more than an hour; separately reported 13 tool calls in an hour and 70–80 tps. | First-hand coding/tool report with incomplete method; not a benchmark. S12 |
| filipe @filicroval | Client, route, and prompt unknown. | Reported about an hour without visible thinking traces. | UX/availability report; no raw session. S13 |
| Tak @cherry_mx_reds | OpenRouter; provider errors; later benchmark details absent. | Reported provider errors and self-reported speed/cache figures. | Operational observation, not a quality benchmark. S14 |
| Tim Jayas @TimJayas | OpenRouter; prompt, client, and settings unknown. | Reported errors every run and severe slowness. | Cannot establish an outage. S15 |
| Reddit commenters | OpenCode/OpenRouter inconsistently mentioned; settings mostly absent. | Reported stuck thinking, no response, loops, elementary errors, and timeouts; other accounts differed. | Community reports; do not aggregate. S10 |
What a comparable review needs
Task
Prompt and input
Include sensitivity, context size, and expected output.
Route
Model, provider, and client
Record tools, reasoning setting, retries, and fallback.
Outcome
Raw or redacted trace
Record UTC, latency, status/429 headers, errors, and a comparison control.
See current availability and the R5 final-status record.