What is the doubao API's uptime?

Measured uptime for the doubao API averages 99.8% across 4 region(s) over the last 24 hours.

Is the doubao API down? Live status, latency & uptime by region

Last verified October 22, 2026 · rebuilt about every 30 minutes

Is the doubao API down right now?

Reachable from all 4 regions

Last successful probe Oct 22, 01:46 UTC · every 5 minutes from 4 region(s)

There was an outage: on Oct 19, 08:00 UTC, host probes failed from 3 of 4 regions simultaneously for at least 10 minutes. No other provider failed in that window, so a shared route or CDN does not explain it. Measured from outside doubao’s own network, independently of its status page; full log: measured AI API incidents.

Real requests: not measured for doubao — only the API host is probed here, so errors limited to specific models are invisible to these probes. That is exactly what a status page tends to report, hence the line below.

doubao publishes no machine-readable status page, so there is nothing to cross-check against.

As of October 22, 2026, the doubao AI API responds in 360 ms p50 (edge, time-to-first-byte) from Europe (Germany) — its fastest measured region — with 100% uptime. Slowest is South America (São Paulo) at 694 ms p50.

Endpoint response (TTFB), 24 h

360 ms

Typical (p50) from Europe (Germany), the fastest region

Uptime, 24 h

99.8%

1,153 probes across 4 region(s)

Failed probes, 72 h

of 3,459 · Europe (Germany), US (Central), Asia (Tokyo), South America (São Paulo)

Reported by doubao, 72 h

—

no machine-readable status page

Was doubao down in the last 3 days?

Yes. 5 outage(s) could be attributed to doubao in the last 72 hours: probes failed from two or more regions at once while no other provider was failing.

Oct 21, 17:06 UTCAsia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 21, 05:45 UTCSouth America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · [Errno 101] Network is unreachable
Oct 20, 18:16 UTC2 of 4 regions (Europe (Germany), US (Central)) — 2 other provider(s) failed in the same minutes, not attributed · at least 14 minutes · 2 failed probe(s) · timeout
Oct 20, 16:10 UTCSouth America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 20, 13:55 UTCSouth America (São Paulo) only — not an outage · at least 15 minutes · 2 failed probe(s) · timeout
Oct 20, 09:20 UTCSouth America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 20, 07:35 UTCAsia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 20, 07:10 UTC2 of 4 regions (Europe (Germany), South America (São Paulo)) — 1 other provider(s) failed in the same minutes, not attributed · at least 9 minutes · 2 failed probe(s) · timeout
Oct 20, 05:35 UTCSouth America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Oct 20, 03:30 UTC2 of 4 regions (Asia (Tokyo), Europe (Germany)) — 1 other provider(s) failed in the same minutes, not attributed · at least 20 minutes · 3 failed probe(s) · timeout
Oct 20, 02:20 UTC2 of 4 regions (Asia (Tokyo), South America (São Paulo)) — 3 other provider(s) failed in the same minutes, not attributed · at least 15 minutes · 3 failed probe(s) · timeout
Oct 20, 01:40 UTCSouth America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · [Errno 101] Network is unreachable

Earlier days with doubao incidents: Oct 19 (5 outages) · Oct 18 (4 outages) · Oct 17 (3 outages) · Oct 16 (1 outage) · Oct 9 (1 outage) · Oct 5 (1 outage) · Oct 3 (1 outage) · Oct 2 (1 outage)

Show this live in your README: — embed code

What doubao’s own status page reported

doubao publishes no machine-readable status page, so there is nothing to set against the measurements above.

Is doubao getting faster or slower?

Endpoint response (TTFB) · milliseconds · lower is faster

Last 72 hours · UTC · newest time on the right · current hour is incomplete.

Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.

typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded

Probe counts by region

Europe (Germany): 18 failed / 864 endpoint probesUS (Central): 10 failed / 862 endpoint probesAsia (Tokyo): 16 failed / 862 endpoint probesSouth America (São Paulo): 38 failed / 862 endpoint probes

Chart details

The strip shows endpoint probe outcomes, not model-request success. Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.

Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.

How fast is the doubao API from each region?

Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics

Endpoint response (TTFB)Network connection and the first response byte, without model inference.

Typical · p5050% of successful timed samples finish within this time.

Slower · p9595% of successful timed samples finish within this time.

Region	Typical (p50 TTFB)	Slower (p95)	Uptime
Asia (Tokyo)	493 ms	1223 ms	99.7%
Europe (Germany)	360 ms	823 ms	100%
South America (São Paulo)	694 ms	1598 ms	99.7%
US (Central)	464 ms	1122 ms	100%

Measured from Europe (Germany), doubao responds in 360 ms; from South America (São Paulo) the same API takes 694 ms — 1.9× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.

What is actually being measured here?

A probe in each region opens a real connection to doubao’s own API host every five minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the response. Nothing is routed through a gateway or aggregator, so these figures describe doubao’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered correctly and is counted as up.

What this page does not tell you

These are edge latency numbers: the time before the model begins generating. They say nothing about answer quality, throughput, price, or how long a full completion takes — those depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every request, before a single token exists, and no prompt engineering removes it. Where an API key is available, inference time-to-first-token is measured separately and shown on the region pages with the model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some models or some accounts — the kind a status page usually reports — which is why doubao’s own reports are shown next to the measurements rather than folded into them.