Status / SiliconFlow
Live monitoring · checked every 2 minutes · last check 24s ago
Is 硅基流动 down? SiliconFlow status right now
No, 硅基流动 is up and working normally.
Operational Current status
100% Uptime 24h
100% Uptime 30 days
1484 ms API response time
Last 24 hours 12:42 UTC · 0 checks · 0 failed · avg — 13:12 UTC · 0 checks · 0 failed · avg — 13:42 UTC · 0 checks · 0 failed · avg — 14:12 UTC · 0 checks · 0 failed · avg — 14:42 UTC · 0 checks · 0 failed · avg — 15:12 UTC · 0 checks · 0 failed · avg — 15:42 UTC · 0 checks · 0 failed · avg — 16:12 UTC · 0 checks · 0 failed · avg — 16:42 UTC · 0 checks · 0 failed · avg — 17:12 UTC · 0 checks · 0 failed · avg — 17:42 UTC · 0 checks · 0 failed · avg — 18:12 UTC · 0 checks · 0 failed · avg — 18:42 UTC · 0 checks · 0 failed · avg — 19:12 UTC · 0 checks · 0 failed · avg — 19:42 UTC · 0 checks · 0 failed · avg — 20:12 UTC · 0 checks · 0 failed · avg — 20:42 UTC · 0 checks · 0 failed · avg — 21:12 UTC · 0 checks · 0 failed · avg — 21:42 UTC · 0 checks · 0 failed · avg — 22:12 UTC · 0 checks · 0 failed · avg — 22:42 UTC · 0 checks · 0 failed · avg — 23:12 UTC · 0 checks · 0 failed · avg — 23:42 UTC · 0 checks · 0 failed · avg — 00:12 UTC · 0 checks · 0 failed · avg — 00:42 UTC · 0 checks · 0 failed · avg — 01:12 UTC · 0 checks · 0 failed · avg — 01:42 UTC · 0 checks · 0 failed · avg — 02:12 UTC · 0 checks · 0 failed · avg — 02:42 UTC · 0 checks · 0 failed · avg — 03:12 UTC · 0 checks · 0 failed · avg — 03:42 UTC · 0 checks · 0 failed · avg — 04:12 UTC · 0 checks · 0 failed · avg — 04:42 UTC · 0 checks · 0 failed · avg — 05:12 UTC · 0 checks · 0 failed · avg — 05:42 UTC · 0 checks · 0 failed · avg — 06:12 UTC · 0 checks · 0 failed · avg — 06:42 UTC · 0 checks · 0 failed · avg — 07:12 UTC · 0 checks · 0 failed · avg — 07:42 UTC · 0 checks · 0 failed · avg — 08:12 UTC · 0 checks · 0 failed · avg — 08:42 UTC · 10 checks · 0 failed · avg 1670 ms 09:12 UTC · 15 checks · 0 failed · avg 1359 ms 09:42 UTC · 26 checks · 0 failed · avg 1633 ms 10:12 UTC · 15 checks · 0 failed · avg 1324 ms 10:42 UTC · 15 checks · 0 failed · avg 1302 ms 11:12 UTC · 15 checks · 0 failed · avg 1388 ms 11:42 UTC · 15 checks · 0 failed · avg 1373 ms 12:12 UTC · 15 checks · 0 failed · avg 1388 ms 24h ago now
API response time (24h) 0 1457 2914 p50 1341 ms · p95 2196 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: 100.00% up · 0 failed / 126 checks 90 days ago 100% uptime today
Incident history SiliconFlow 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 SiliconFlow every 2 minutes from our global monitoring network. Last check: 24s ago.
What is 硅基流动’s uptime? Measured by ModelBank: 100% in the last 24 hours, 100% over 30 days and 100% 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.
Get free alerts Browser push · Slack / Discord · Feishu / DingTalk / WeCom · RSS — free, no sign-up