Tickerr / Status / Cohere Command R
Is Cohere Command R down right now?
Authenticated API inference - 1 model monitored · How we classify outages
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Cohere Command R is currently operational - 389ms HTTP response. Last checked . 90-day uptime: 99.9%. Cohere Command R API: 0/1 models up - check inference section below.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live Cohere Command R status on your site, README, or docs.
HTTP uptime (90d)
99.9%
4 incidents (90d)
HTTP response now
389ms
HTTP p50 (7d)
704ms
median ping response
HTTP p95 (7d)
1174ms
tail ping response
API Inference Monitoring
Live · every 5 minBest TTFT (p50)
—
time to first token
Best throughput
9tok/s
output tokens/sec (24h avg)
Min success rate
22%
worst model (24h)
P50 = typical speed. P95 = worst case 95% of the time. Measured by Tickerr's independent inference checks. Requires ≥10 checks to display.
TTFT over 24 hours
ⓘ Authenticated streaming API calls via native fetch. TTFT = milliseconds from request start to first streamed token chunk. Throughput = output tokens ÷ generation time. Checks run from Vercel us-east-1. Independent of the provider's official status page.
Is Cohere Command R slow right now?
Cohere Command R API is currently experiencing issues. Some models are not responding to requests.Last checked 1m ago.
HTTP endpoint response: 389ms (7-day p50: 704ms). This measures basic reachability, not model inference speed.
TTFT (time-to-first-token) is measured via authenticated streaming API calls every 5 minutes. Current values are compared against 7-day and 30-day rolling baselines. A minimum of 5 successful checks is required before classification. Methodology
Cohere Command R speed FAQ
Is Cohere Command R slow right now?
Cohere Command R API is currently experiencing issues. Some models are not responding to requests.
Why is Cohere Command R so slow today?
Cohere Command R is currently responding within its normal speed range. If you're experiencing slowness, it may be specific to your region, account tier, or the particular model you're using. Tickerr monitors multiple models independently.
Is Cohere Command R down or just responding slowly?
Cohere Command R appears to be down — some models are not responding to API requests at all. Check the status section above for the latest incident details.
How does Tickerr determine whether Cohere Command R is slow?
Tickerr sends authenticated API requests to Cohere Command R every 5 minutes and measures time-to-first-token (TTFT). Current TTFT is compared against a rolling 7-day and 30-day baseline. A model is classified as slow when its current p50 TTFT exceeds 2x its baseline, and severely slow at 3.5x. At least 5 successful checks are required before any classification is made.
What is normal response time for Cohere Command R?
Tickerr is still collecting baseline data for Cohere Command R. Normal response times will be available after sufficient monitoring history has accumulated.
Can one Cohere Command R model be slow while others are working normally?
Yes. Cohere Command R runs multiple models (e.g. command-r-plus-08-2024), and each can have independent performance characteristics. Tickerr monitors each model separately. A slowdown on one model doesn't necessarily affect others.
Experimental capability checks
PUBLIC PILOTTickerr sends deterministic test prompts to Cohere Command R every hour and evaluates the output using code-based pass/fail checks. These results are informational onlyduring the pilot period and do not affect the tool's status verdict.
How Tickerr tests this
Every hour, Tickerr sends three deterministic test prompts to each monitored model via the provider's API. Each response is evaluated with a code-based pass/fail check — no subjective judgement.
- Instruction following: asks the model to reply with an exact word. Graded by exact string match.
- JSON schema: asks for a JSON object matching a fixed schema. Graded by parse + field validation.
- Tool call: asks the model to call a function with specific arguments. Graded by parsing the tool-call response.
Infrastructure errors (timeouts, rate limits, auth failures) are tracked separately and excluded from capability pass rates. Models that don't support tool calls are marked “not supported” rather than counted as failures. Full methodology
HTTP endpoint response time (7 days)
p50 704ms·p95 1174msⓘ HTTP response times to Cohere Command R's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the Cohere Command R API Status section above.
90-day uptime
Incident history
Status: Investigating We are investigating a partial outage affecting our documentation site. Some documentation pages may not load correctly due to an ongoing issue with our upstream documentation pr…
Status: Investigating 🔎 We are currently investigating an issue affecting the Cohere Dashboard (dashboard.cohere.com "dashboard.cohere.com": http://dashboard.cohere.com). Users may experience a conti…
Status: Identified /audio/transcriptions endpoints availability is affected now due to the Cohere ASR model backing the endpoint throws error for any audio inputs that are in the expected sampling rat…
Related pages
About Cohere Command R status
Cohere provides enterprise-grade language models via API, including Command R+. Cohere API downtime affects enterprise customers and developers. Status is monitored every 5 minutes.