Status / Xiaomi MiMo
Live monitoring · checked every 2 minutes · last check 1m ago
Is 小米 down? Xiaomi MiMo status right now
No, 小米 is up and working normally.
Operational Current status
90.87% Uptime 24h
90.87% Uptime 30 days
10000 ms API response time
Last 24 hours 12:43 UTC · 0 checks · 0 failed · avg — 13:13 UTC · 0 checks · 0 failed · avg — 13:43 UTC · 0 checks · 0 failed · avg — 14:13 UTC · 0 checks · 0 failed · avg — 14:43 UTC · 0 checks · 0 failed · avg — 15:13 UTC · 0 checks · 0 failed · avg — 15:43 UTC · 0 checks · 0 failed · avg — 16:13 UTC · 0 checks · 0 failed · avg — 16:43 UTC · 0 checks · 0 failed · avg — 17:13 UTC · 0 checks · 0 failed · avg — 17:43 UTC · 0 checks · 0 failed · avg — 18:13 UTC · 0 checks · 0 failed · avg — 18:43 UTC · 0 checks · 0 failed · avg — 19:13 UTC · 0 checks · 0 failed · avg — 19:43 UTC · 0 checks · 0 failed · avg — 20:13 UTC · 0 checks · 0 failed · avg — 20:43 UTC · 0 checks · 0 failed · avg — 21:13 UTC · 0 checks · 0 failed · avg — 21:43 UTC · 0 checks · 0 failed · avg — 22:13 UTC · 0 checks · 0 failed · avg — 22:43 UTC · 0 checks · 0 failed · avg — 23:13 UTC · 0 checks · 0 failed · avg — 23:43 UTC · 0 checks · 0 failed · avg — 00:13 UTC · 0 checks · 0 failed · avg — 00:43 UTC · 0 checks · 0 failed · avg — 01:13 UTC · 0 checks · 0 failed · avg — 01:43 UTC · 0 checks · 0 failed · avg — 02:13 UTC · 0 checks · 0 failed · avg — 02:43 UTC · 0 checks · 0 failed · avg — 03:13 UTC · 0 checks · 0 failed · avg — 03:43 UTC · 0 checks · 0 failed · avg — 04:13 UTC · 0 checks · 0 failed · avg — 04:43 UTC · 0 checks · 0 failed · avg — 05:13 UTC · 0 checks · 0 failed · avg — 05:43 UTC · 0 checks · 0 failed · avg — 06:13 UTC · 0 checks · 0 failed · avg — 06:43 UTC · 0 checks · 0 failed · avg — 07:13 UTC · 0 checks · 0 failed · avg — 07:43 UTC · 0 checks · 0 failed · avg — 08:13 UTC · 0 checks · 0 failed · avg — 08:43 UTC · 10 checks · 0 failed · avg 7829 ms 09:13 UTC · 15 checks · 0 failed · avg 8545 ms 09:43 UTC · 26 checks · 0 failed · avg 6420 ms 10:13 UTC · 15 checks · 0 failed · avg 6403 ms 10:43 UTC · 15 checks · 0 failed · avg 5640 ms 11:13 UTC · 15 checks · 0 failed · avg 6158 ms 11:43 UTC · 15 checks · 0 failed · avg 4009 ms 12:13 UTC · 15 checks · 0 failed · avg 7872 ms 24h ago now
API response time (24h) 0 5751 11501 p50 6811 ms · p95 10000 ms (ms, UTC)
90-day uptime history 2026-06-27: no data 2026-06-28: no data 2026-06-29: no data 2026-06-30: no data 2026-07-01: no data 2026-07-02: no data 2026-07-03: no data 2026-07-04: no data 2026-07-05: no data 2026-07-06: no data 2026-07-07: no data 2026-07-08: no data 2026-07-09: no data 2026-07-10: no data 2026-07-11: no data 2026-07-12: no data 2026-07-13: no data 2026-07-14: no data 2026-07-15: no data 2026-07-16: no data 2026-07-17: no data 2026-07-18: no data 2026-07-19: no data 2026-07-20: no data 2026-07-21: no data 2026-07-22: no data 2026-07-23: no data 2026-07-24: no data 2026-07-25: no data 2026-07-26: no data 2026-07-27: no data 2026-07-28: no data 2026-07-29: no data 2026-07-30: no data 2026-07-31: no data 2026-08-01: no data 2026-08-02: no data 2026-08-03: no data 2026-08-04: no data 2026-08-05: no data 2026-08-06: no data 2026-08-07: no data 2026-08-08: no data 2026-08-09: no data 2026-08-10: no data 2026-08-11: no data 2026-08-12: no data 2026-08-13: no data 2026-08-14: no data 2026-08-15: no data 2026-08-16: no data 2026-08-17: no data 2026-08-18: no data 2026-08-19: no data 2026-08-20: no data 2026-08-21: no data 2026-08-22: no data 2026-08-23: no data 2026-08-24: no data 2026-08-25: no data 2026-08-26: no data 2026-08-27: no data 2026-08-28: no data 2026-08-29: no data 2026-08-30: no data 2026-08-31: no data 2026-09-01: no data 2026-09-02: no data 2026-09-03: no data 2026-09-04: no data 2026-09-05: no data 2026-09-06: no data 2026-09-07: no data 2026-09-08: no data 2026-09-09: no data 2026-09-10: no data 2026-09-11: no data 2026-09-12: no data 2026-09-13: no data 2026-09-14: no data 2026-09-15: no data 2026-09-16: no data 2026-09-17: no data 2026-09-18: no data 2026-09-19: no data 2026-09-20: no data 2026-09-21: no data 2026-09-22: no data 2026-09-23: no data 2026-09-24: 90.87% up · 0 failed / 126 checks 90 days ago 90.87% uptime today
Incident history Xiaomi 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 Xiaomi MiMo every 2 minutes from our global monitoring network. Last check: 1m ago.
What is 小米’s uptime? Measured by ModelBank: 90.87% in the last 24 hours, 90.87% over 30 days and 90.87% 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.
Having problems with 小米? 0 reports in the last hour · 0 in 24h
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Signals
Our API probe API responded HTTP 0 in 10000 ms
Official status not published
Status since 13m ago
Xiaomi models USD per 1M input / output tokens
Alternatives if it’s down
Embed this status [](https://modelbank.ai/status/xiaomi-mimo)
Get notified when 小米 goes down We’ll notify you the moment ModelBank detects a 小米 outage, and again when it recovers.
Get free alerts Browser push · Slack / Discord · Feishu / DingTalk / WeCom · RSS — free, no sign-up