Tencent Hunyuan
Live monitoring · checked every 2 minutes · last check 21s ago

Is 混元 down? Tencent Hunyuan status right now

Official site
OperationalCurrent status
99.61%Uptime 24h
99.61%Uptime 30 days
2039 msAPI response time

Last 24 hours

12:46 UTC · 0 checks · 0 failed · avg —13:16 UTC · 0 checks · 0 failed · avg —13:46 UTC · 0 checks · 0 failed · avg —14:16 UTC · 0 checks · 0 failed · avg —14:46 UTC · 0 checks · 0 failed · avg —15:16 UTC · 0 checks · 0 failed · avg —15:46 UTC · 0 checks · 0 failed · avg —16:16 UTC · 0 checks · 0 failed · avg —16:46 UTC · 0 checks · 0 failed · avg —17:16 UTC · 0 checks · 0 failed · avg —17:46 UTC · 0 checks · 0 failed · avg —18:16 UTC · 0 checks · 0 failed · avg —18:46 UTC · 0 checks · 0 failed · avg —19:16 UTC · 0 checks · 0 failed · avg —19:46 UTC · 0 checks · 0 failed · avg —20:16 UTC · 0 checks · 0 failed · avg —20:46 UTC · 0 checks · 0 failed · avg —21:16 UTC · 0 checks · 0 failed · avg —21:46 UTC · 0 checks · 0 failed · avg —22:16 UTC · 0 checks · 0 failed · avg —22:46 UTC · 0 checks · 0 failed · avg —23:16 UTC · 0 checks · 0 failed · avg —23:46 UTC · 0 checks · 0 failed · avg —00:16 UTC · 0 checks · 0 failed · avg —00:46 UTC · 0 checks · 0 failed · avg —01:16 UTC · 0 checks · 0 failed · avg —01:46 UTC · 0 checks · 0 failed · avg —02:16 UTC · 0 checks · 0 failed · avg —02:46 UTC · 0 checks · 0 failed · avg —03:16 UTC · 0 checks · 0 failed · avg —03:46 UTC · 0 checks · 0 failed · avg —04:16 UTC · 0 checks · 0 failed · avg —04:46 UTC · 0 checks · 0 failed · avg —05:16 UTC · 0 checks · 0 failed · avg —05:46 UTC · 0 checks · 0 failed · avg —06:16 UTC · 0 checks · 0 failed · avg —06:46 UTC · 0 checks · 0 failed · avg —07:16 UTC · 0 checks · 0 failed · avg —07:46 UTC · 0 checks · 0 failed · avg —08:16 UTC · 0 checks · 0 failed · avg —08:46 UTC · 12 checks · 0 failed · avg 2892 ms09:16 UTC · 15 checks · 0 failed · avg 2257 ms09:46 UTC · 26 checks · 0 failed · avg 2991 ms10:16 UTC · 15 checks · 0 failed · avg 2298 ms10:46 UTC · 15 checks · 0 failed · avg 2336 ms11:16 UTC · 15 checks · 0 failed · avg 2548 ms11:46 UTC · 15 checks · 0 failed · avg 2420 ms12:16 UTC · 15 checks · 0 failed · avg 2401 ms
24h agonow

API response time (24h)

027885575p50 2384 ms · p95 4038 ms (ms, UTC)

90-day uptime history

2026-06-27: no data2026-06-28: no data2026-06-29: no data2026-06-30: no data2026-07-01: no data2026-07-02: no data2026-07-03: no data2026-07-04: no data2026-07-05: no data2026-07-06: no data2026-07-07: no data2026-07-08: no data2026-07-09: no data2026-07-10: no data2026-07-11: no data2026-07-12: no data2026-07-13: no data2026-07-14: no data2026-07-15: no data2026-07-16: no data2026-07-17: no data2026-07-18: no data2026-07-19: no data2026-07-20: no data2026-07-21: no data2026-07-22: no data2026-07-23: no data2026-07-24: no data2026-07-25: no data2026-07-26: no data2026-07-27: no data2026-07-28: no data2026-07-29: no data2026-07-30: no data2026-07-31: no data2026-08-01: no data2026-08-02: no data2026-08-03: no data2026-08-04: no data2026-08-05: no data2026-08-06: no data2026-08-07: no data2026-08-08: no data2026-08-09: no data2026-08-10: no data2026-08-11: no data2026-08-12: no data2026-08-13: no data2026-08-14: no data2026-08-15: no data2026-08-16: no data2026-08-17: no data2026-08-18: no data2026-08-19: no data2026-08-20: no data2026-08-21: no data2026-08-22: no data2026-08-23: no data2026-08-24: no data2026-08-25: no data2026-08-26: no data2026-08-27: no data2026-08-28: no data2026-08-29: no data2026-08-30: no data2026-08-31: no data2026-09-01: no data2026-09-02: no data2026-09-03: no data2026-09-04: no data2026-09-05: no data2026-09-06: no data2026-09-07: no data2026-09-08: no data2026-09-09: no data2026-09-10: no data2026-09-11: no data2026-09-12: no data2026-09-13: no data2026-09-14: no data2026-09-15: no data2026-09-16: no data2026-09-17: no data2026-09-18: no data2026-09-19: no data2026-09-20: no data2026-09-21: no data2026-09-22: no data2026-09-23: no data2026-09-24: 99.61% up · 0 failed / 128 checks
90 days ago99.61% uptimetoday

Incident history

Tencent does not publish a machine-readable status page. Outages are detected by ModelBank’s own probes (see the 90-day history above).

FAQ

Is 混元 down?

No, 混元 is up and working normally. ModelBank checks Tencent Hunyuan every 2 minutes from our global monitoring network. Last check: 21s ago.

What is 混元’s uptime?

Measured by ModelBank: 99.61% in the last 24 hours, 99.61% over 30 days and 99.61% over 90 days.

What should I do if 混元 is not working?

First check this page and the official status page. If 混元 is up for everyone else, try clearing cache, logging out and in, switching network, or checking your API key and rate limits (HTTP 429). If it is a real outage, switch to an alternative model — see the alternatives on this page — or use a router with automatic failover.

Get notified when 混元 goes down

We’ll notify you the moment ModelBank detects a 混元 outage, and again when it recovers.

Browser push · Slack / Discord · Feishu / DingTalk / WeCom · RSS — free, no sign-up