NEWTickerr MCP is live →
tickerr

Tickerr / Status / OpenRouter

OpenRouter

Is OpenRouter down right now?

Authenticated API inference - 2 models monitored · How we classify outages

Weekly AI pricing & uptime digest

Price drops, new model releases, and incident summaries - every Monday. Free.

OpenRouter is currently down - official outage reported - 425ms HTTP response. Last checked . 90-day uptime: 99.9%. OpenRouter API: 0/2 models up - check inference section below.

Down425ms response
Partial outage - Ongoing34d agoOfficial

[Automated] Chat (/api/v1/chat/completions) is inaccessible

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 OpenRouter status on your site, README, or docs.

OpenRouter status

HTTP uptime (90d)

99.9%

2 incidents (90d)

HTTP response now

425ms

HTTP p50 (7d)

426ms

median ping response

HTTP p95 (7d)

1823ms

tail ping response

API Inference Monitoring

Live · every 5 min

Best TTFT (p50)

time to first token

Best throughput

output tokens/sec (24h avg)

Min success rate

0%

worst model (24h)

ModelStatusTTFT nowp50 TTFTp95 TTFT24h uptime
deepseek/deepseek-v3:free11 checks
Bad response
0%
qwen/qwen3-235b-a22b:free11 checks
Bad response
0%

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

No TTFT data yet - first check will appear within 5 minutes of deploying.

ⓘ 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 OpenRouter slow right now?

OpenRouter is currently experiencing an outage or significant issues. Check the status section above for details.Last checked just now.

ModelCurrent TTFT7d BaselineStatus
deepseek/deepseek-v3:free Unavailable
qwen/qwen3-235b-a22b:free Unavailable

HTTP endpoint response: 425ms (7-day p50: 426ms). 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

OpenRouter speed FAQ

Is OpenRouter slow right now?

OpenRouter is currently experiencing an outage or significant issues. Check the status section above for details.

Why is OpenRouter so slow today?

OpenRouter is currently experiencing an outage, not just slowness. Check the status section above for the latest incident details and expected resolution.

Is OpenRouter down or just responding slowly?

OpenRouter is currently down — not just slow. An active outage or major incident has been detected. Check the status section above for details.

How does Tickerr determine whether OpenRouter is slow?

Tickerr sends authenticated API requests to OpenRouter 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 OpenRouter?

Tickerr is still collecting baseline data for OpenRouter. Normal response times will be available after sufficient monitoring history has accumulated.

Can one OpenRouter model be slow while others are working normally?

Yes. OpenRouter runs multiple models (e.g. deepseek/deepseek-v3:free, qwen/qwen3-235b-a22b:free), and each can have independent performance characteristics. Tickerr monitors each model separately. A slowdown on one model doesn't necessarily affect others.

HTTP endpoint response time (7 days)

p50 426ms·p95 1823ms

HTTP response times to OpenRouter's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the OpenRouter API Status section above.

90-day uptime

Jun 26 99.7%Jul 26 100%Aug 26 100%
99.9%
90-day uptime · HTTP + API inference
May 30Today
100%99–99.9%95–99% or API failures<95% or major API failures
HTTP pings + API inference checks · checked every 5 min · 90 days

Incident history

Partial OutageOngoingOfficial
Jul 23, 2026
08:57 PM UTC
[Automated] Chat (/api/v1/chat/completions) is inaccessible

Jul 23, 8:57 PM UTC INVESTIGATING - Chat (/api/v1/chat/completions) cannot be reached by our automated monitoring.

34d 6h (ongoing)
Partial OutageResolvedOfficial
Jul 5, 2026
06:00 AM UTC
Scheduled Database Maintenance

Jul 5, 6:00 AM UTC IN_PROGRESS - Scheduled maintenance is currently in progress.

1d 0h

Related pages

OpenRouter API not working? Common error codes

If OpenRouter's API is returning errors, the table below explains what each code means and how to fix it. If errors are widespread, check the live status above - a service incident will appear there within minutes.

ErrorWhat it means & what to do
HTTP 429OpenRouter rate limit or upstream provider throttling
HTTP 502Upstream provider error - check which model/provider you're routing to
HTTP 503OpenRouter or upstream provider unavailable

Note: Tickerr monitors OpenRouter's status endpoint, not individual API calls. An HTTP 429 or 500 in your app may be specific to your account tier - check the rate limits page for plan-specific thresholds.

About OpenRouter status

OpenRouter is an API aggregator that provides unified access to 100+ LLMs from OpenAI, Anthropic, Google, and others. OpenRouter outages can affect all downstream models or specific providers. Monitoring reflects OpenRouter's own API availability, not individual provider status.