HomeProvider details
Data API

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

· rebuilt about every 30 minutes

Is the Tencent TokenHub API down right now?

Reachable from all 4 regions

Last successful probe Nov 7, 21:15 UTC · every 5 minutes from 4 region(s)

Every probe from every region reached the tencent-tokenhub API successfully in the last 72 hours. Measured from outside tencent-tokenhub’s own network, independently of its status page; full log: measured AI API incidents.

Real requests: not measured for Tencent TokenHub — 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.

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

As of November 07, 2026, the tencent-tokenhub AI API responds in 266 ms p50 (edge, time-to-first-byte) from Asia (Tokyo) — its fastest measured region — with 100% uptime. Slowest is South America (São Paulo) at 796 ms p50.

Endpoint response (TTFB), 24 h
266 ms
Typical (p50) from Asia (Tokyo), the fastest region
Uptime, 24 h
100%
144 probes across 4 region(s)
Failed probes, 72 h
0
of 144 probes, all regions
Reported by Tencent TokenHub, 72 h
—
no machine-readable status page

Was Tencent TokenHub down in the last 3 days?

No. All 144 probes from 4 region(s) reached the tencent-tokenhub API in the last 72 hours.

Show this live in your README: Tencent TokenHub API status badge — embed code

What Tencent TokenHub’s own status page reported

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

Is Tencent TokenHub 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

tencent-tokenhub — hourly p50 edge latency (ms) and probe outcomes per region, last 72 hoursEndpoint response time in milliseconds. Lower is faster. Each region uses the same vertical scale from 0 to 1000 ms. Lines show hourly p50 values; gaps have no successful timed probes. Outcome counts are listed after this chart.Nov 5Nov 6Nov 7nowNov 4, 22:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 4, 23:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 00:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 01:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 02:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 03:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 04:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 05:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 06:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 07:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 08:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 09:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 10:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 11:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 12:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 13:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 14:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 15:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 16:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 17:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 18:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 19:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 20:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 21:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 22:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 5, 23:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 00:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 01:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 02:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 03:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 04:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 05:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 06:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 07:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 08:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 09:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 10:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 11:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 12:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 13:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 14:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 15:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 16:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 17:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 18:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 19:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 20:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 21:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 22:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 6, 23:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 00:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 01:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 02:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 03:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 04:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 05:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 06:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 07:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 08:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 09:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 10:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 11:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 12:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 13:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 14:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 15:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 16:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 17:00 UTC Europe (Germany): no successful timed probe US (Central): no successful timed probe Asia (Tokyo): no successful timed probe South America (São Paulo): no successful timed probeNov 7, 18:00 UTC Europe (Germany): typical 455 ms (p50 TTFB) US (Central): typical 607 ms (p50 TTFB) Asia (Tokyo): typical 274 ms (p50 TTFB) South America (São Paulo): typical 781 ms (p50 TTFB)Nov 7, 19:00 UTC Europe (Germany): typical 633 ms (p50 TTFB) US (Central): typical 626 ms (p50 TTFB) Asia (Tokyo): typical 266 ms (p50 TTFB) South America (São Paulo): typical 797 ms (p50 TTFB)Nov 7, 20:00 UTC Europe (Germany): typical 463 ms (p50 TTFB) US (Central): typical 585 ms (p50 TTFB) Asia (Tokyo): typical 246 ms (p50 TTFB) South America (São Paulo): typical 799 ms (p50 TTFB)Nov 7, 21:00 UTC Europe (Germany): typical 501 ms (p50 TTFB) US (Central): typical 590 ms (p50 TTFB) Asia (Tokyo): typical 299 ms (p50 TTFB) South America (São Paulo): typical 813 ms (p50 TTFB)10000Nov 4, 22:00 – Nov 7, 17:00 UTC: no probes recordedNov 7, 18:00 – Nov 7, 21:00 UTC: all 36 probes succeeded10000Nov 4, 22:00 – Nov 7, 17:00 UTC: no probes recordedNov 7, 18:00 – Nov 7, 21:00 UTC: all 36 probes succeeded10000Nov 4, 22:00 – Nov 7, 17:00 UTC: no probes recordedNov 7, 18:00 – Nov 7, 21:00 UTC: all 36 probes succeeded10000Nov 4, 22:00 – Nov 7, 17:00 UTC: no probes recordedNov 7, 18:00 – Nov 7, 21:00 UTC: all 36 probes succeeded
Europe (Germany)latest 501 · median 482 msUS (Central)latest 590 · median 599 msAsia (Tokyo)latest 299 · median 270 msSouth America (São Paulo)latest 813 · median 798 ms
Probe counts by region
Europe (Germany): 0 failed / 36 endpoint probes · 68 hour(s) without dataUS (Central): 0 failed / 36 endpoint probes · 68 hour(s) without dataAsia (Tokyo): 0 failed / 36 endpoint probes · 68 hour(s) without dataSouth America (São Paulo): 0 failed / 36 endpoint probes · 68 hour(s) without data
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 Tencent TokenHub 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.
RegionTypical (p50 TTFB)Slower (p95)Uptime
Asia (Tokyo)266 ms292 ms100%
Europe (Germany)463 ms670 ms100%
South America (São Paulo)796 ms828 ms100%
US (Central)605 ms1977 ms100%

Measured from Asia (Tokyo), tencent-tokenhub responds in 266 ms; from South America (São Paulo) the same API takes 796 ms — 3.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 tencent-tokenhub’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 tencent-tokenhub’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, while a 410 Gone means the API has been shut down and is counted as neither (rule).

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 Tencent TokenHub’s own reports are shown next to the measurements rather than folded into them.