Status — Wakemark

Status

Provider health, as routing sees it.

Wakemark routes every job across the providers you connect, and this page shows the signal that routing acts on: circuit-breaker state per provider and capability, built from live submit traffic. When a provider develops a failure pattern its circuit opens and routing steers jobs to the others — the table below reads the same state the failover engine reads, refreshed here about once a minute. There are no synthetic probes and no invented uptime numbers here: what the engine has observed is exactly what you see.

16 providers · 10 tracked cells10 awaiting first trafficas of 2026-07-21 17:54:31 UTC

aiml

Black Forest Labs

bfl

image-to-image
no recent observationsno submit outcomes on this instance yet
text-to-image
no recent observationsno submit outcomes on this instance yet

ElevenLabs

elevenlabs

EvoLink

evolink

text-to-image
no recent observationsno submit outcomes on this instance yet

fal

text-to-image
no recent observationsno submit outcomes on this instance yet

gemini

Kie.ai

kie

text-to-image
no recent observationsno submit outcomes on this instance yet

laozhang

modelslab

muapi

OpenAI

openai

text-to-image
no recent observationsno submit outcomes on this instance yet

PiAPI

piapi

text-to-image
no recent observationsno submit outcomes on this instance yet

Replicate

replicate

text-to-image
no recent observationsno submit outcomes on this instance yet

Runware

runware

text-to-image
no recent observationsno submit outcomes on this instance yet

segmind

WaveSpeed

wavespeed

text-to-image
no recent observationsno submit outcomes on this instance yet

How to read this

This is circuit-breaker state from live submit traffic on the running engine instance, observed since 2026-07-21 14:22:04 UTC. It is the routing engine's own signal, shown unedited — not a marketing dashboard fed by anything else.

Where the data comes from: Every submit success — and every provider-fault failure — updates a breaker keyed on (provider, capability)— a provider's video pipeline can be down while its images are fine, so each is tracked separately. Failures that are the customer's own (invalid input, a moderation refusal, one account's rate or quota limits) never touch a cell. Each provider also carries one uncategorized pass-through cell for submits to models outside the catalog. The state lives in memory on the running instance, so a deploy resets it — observed since above tells you exactly when observation began.
What counts as a failure: Only provider-side faults: 5xx responses, timeouts, and transport errors. A customer's invalid input, a moderation refusal, or one account's rate limit would fail identically anywhere, so they never mark a provider unhealthy.
No synthetic probes: Every generation costs real money, so Wakemark never burns jobs as pings. A cell no customer traffic has touched reads no recent observations — an absence of data, never dressed up as healthy.
An open circuit is failover working: Open means a real failure pattern was detected and routing is steering jobs to other providers right now. Recovery pending confirmation means the breaker is letting trial traffic through to confirm the provider is back before trusting it again.
What this page does not know: There are no uptime percentages or latency numbers here because none are measured yet, and this page will not invent them. When ledger-fed telemetry lands, it is designed to be added to this same surface — with the same sourcing statement.
One instance at a time: Breaker state lives in memory on whichever engine instance answered this request. Behind more than one machine, another instance may hold a different view — so this is a per-instance snapshot that settles across the fleet over time, not a single global truth. Honest, and worth knowing before you read a single reading as the whole story.

Basis — the endpoint's own words

circuit-breaker state derived from live submit outcomes on this instance since observed_since; only provider-fault failures (5xx, timeouts, transport) count — customer input errors, moderation refusals, and per-account rate/auth/quota trouble never open a circuit; no synthetic probes, no uptime percentages, no invented history

This page is the human face of GET /v1/providers/health — the same JSON, public and unauthenticated. The page re-reads it every 60 seconds. It reports the providers Wakemark routes across, not the wakemark.ai site itself; when the engine cannot be reached, this page says so instead of guessing.

Curious what runs behind these rows? Browse the providers we route across or the models & prices.