As of September 07, 2026, the doubao AI API responds in 350 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 695 ms p50.
Is doubao down right now?
Reachable from all 4 regions
Last successful probe Sep 7, 00:17 UTC · every 5 minutes from 4 region(s)
29 isolated failure(s) in the last 72 hours, the most recent (host probes) visible from only one region (Asia (Tokyo)). A single-region failure cannot be separated from a problem on that network path, so it is not called an outage. 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.
Edge latency, 24 h
350 ms
p50 from Europe (Germany), the fastest region
Uptime, 24 h
99.5%
1,154 probes across 4 region(s)
Failed probes, 72 h
43
of 3,456 · US (Central), Asia (Tokyo)
Reported by doubao, 72 h
—
no machine-readable status page
Was doubao down in the last 3 days?
No. 29 isolated single-region probe failure(s) were recorded, none of which meets the bar for an outage (two or more regions at once).
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · at least 5 minutes · 2 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · at least 20 minutes · 3 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · at least 15 minutes · 2 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
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?
hourly p50 latencyall probes succeededsome probes failedhalf or more failedno data
One panel per region: the line is the hourly p50 edge latency (shared scale, ms), the strip beneath it is the outcome of that hour’s host probes. Hover any hour for the numbers. Flat is good; a rising line means the endpoint is slowing down from that origin, a gap means no probe succeeded in that hour.
How fast is the doubao API from each region?
Region
p50 TTFB
p95
Uptime
Asia (Tokyo)
493 ms
1792 ms
98.3%
Europe (Germany)
350 ms
796 ms
100%
South America (São Paulo)
695 ms
1565 ms
100%
US (Central)
493 ms
574 ms
100%
Measured from Europe (Germany), doubao responds in 350 ms; from South America (São Paulo) the same API takes 695 ms — 2.0× 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.