HomeProvider details
Data API

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

· rebuilt about every 30 minutes

Is the iflytek API down right now?

Reachable from all 4 regions

Last successful probe Nov 6, 22:45 UTC · every 5 minutes from 4 region(s)

On Nov 5, 18:55 UTC host probes failed from 2 of 4 regions — but 1 other provider(s) failed in the same minutes. A cause shared by several unrelated APIs sits above any one of them, and our data cannot say whose it was, so iflytek is not blamed for it. Measured from outside iflytek’s own network, independently of its status page; full log: measured AI API incidents.

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

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

As of November 06, 2026, the iflytek AI API responds in 246 ms p50 (edge, time-to-first-byte) from Asia (Tokyo) — its fastest measured region — with 99.7% uptime. Slowest is South America (São Paulo) at 660 ms p50.

Endpoint response (TTFB), 24 h
246 ms
Typical (p50) from Asia (Tokyo), the fastest region
Uptime, 24 h
99.8%
1,152 probes across 4 region(s)
Failed probes, 72 h
26
of 3,458 · US (Central), Asia (Tokyo), South America (São Paulo)
Reported by iflytek, 72 h
—
no machine-readable status page

Was iflytek down in the last 3 days?

Not attributably. 4 multi-region failure(s) coincided with other providers failing in the same minutes, so the cause sits above any one of them.

  • US (Central) 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
  • 2 of 4 regions (South America (São Paulo), US (Central)) — 1 other provider(s) failed in the same minutes, not attributed · under one 5-minute probe cycle · 2 failed probe(s) · timeout
  • US (Central) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · [Errno 104] Connection reset by peer
  • 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) · [Errno 104] Connection reset by peer
  • Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
  • South America (São Paulo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
  • 2 of 4 regions (South America (São Paulo), US (Central)) — 2 other provider(s) failed in the same minutes, not attributed · under one 5-minute probe cycle · 2 failed probe(s) · timeout
  • 2 of 4 regions (South America (São Paulo), US (Central)) — 1 other provider(s) failed in the same minutes, not attributed · at least 25 minutes · 3 failed probe(s) · timeout
  • Asia (Tokyo) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
  • 2 of 4 regions (South America (São Paulo), US (Central)) — 2 other provider(s) failed in the same minutes, not attributed · at least 10 minutes · 4 failed probe(s) · timeout

Earlier days with iflytek incidents: Oct 5 (1 outage) · Sep 29 (1 outage)

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

What iflytek’s own status page reported

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

Is iflytek 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

iflytek — 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 2000 ms. Lines show hourly p50 values; gaps have no successful timed probes. Outcome counts are listed after this chart.Nov 4Nov 5Nov 6nowNov 3, 23:00 UTC Europe (Germany): typical 295 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 219 ms (p50 TTFB) South America (São Paulo): typical 651 ms (p50 TTFB)Nov 4, 00:00 UTC Europe (Germany): typical 296 ms (p50 TTFB) US (Central): typical 423 ms (p50 TTFB) Asia (Tokyo): typical 222 ms (p50 TTFB) South America (São Paulo): typical 653 ms (p50 TTFB)Nov 4, 01:00 UTC Europe (Germany): typical 297 ms (p50 TTFB) US (Central): typical 404 ms (p50 TTFB) Asia (Tokyo): typical 554 ms (p50 TTFB) South America (São Paulo): typical 652 ms (p50 TTFB)Nov 4, 02:00 UTC Europe (Germany): typical 278 ms (p50 TTFB) US (Central): typical 426 ms (p50 TTFB) Asia (Tokyo): typical 268 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 660 ms (p50 TTFB)Nov 4, 03:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 373 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB)Nov 4, 04:00 UTC Europe (Germany): typical 306 ms (p50 TTFB) US (Central): typical 415 ms (p50 TTFB) Asia (Tokyo): typical 562 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 663 ms (p50 TTFB)Nov 4, 05:00 UTC Europe (Germany): typical 298 ms (p50 TTFB) US (Central): typical 414 ms (p50 TTFB) Asia (Tokyo): typical 598 ms (p50 TTFB) South America (São Paulo): typical 657 ms (p50 TTFB)Nov 4, 06:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 453 ms (p50 TTFB) Asia (Tokyo): typical 257 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 662 ms (p50 TTFB)Nov 4, 07:00 UTC Europe (Germany): typical 304 ms (p50 TTFB) US (Central): typical 426 ms (p50 TTFB) Asia (Tokyo): typical 588 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB)Nov 4, 08:00 UTC Europe (Germany): typical 299 ms (p50 TTFB) US (Central): typical 423 ms (p50 TTFB) Asia (Tokyo): typical 616 ms (p50 TTFB) South America (São Paulo): typical 685 ms (p50 TTFB)Nov 4, 09:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 416 ms (p50 TTFB) Asia (Tokyo): typical 418 ms (p50 TTFB) South America (São Paulo): typical 658 ms (p50 TTFB)Nov 4, 10:00 UTC Europe (Germany): typical 301 ms (p50 TTFB) US (Central): typical 423 ms (p50 TTFB) Asia (Tokyo): typical 268 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB)Nov 4, 11:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 407 ms (p50 TTFB) Asia (Tokyo): typical 273 ms (p50 TTFB) South America (São Paulo): typical 669 ms (p50 TTFB)Nov 4, 12:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 417 ms (p50 TTFB) Asia (Tokyo): typical 288 ms (p50 TTFB) South America (São Paulo): typical 672 ms (p50 TTFB)Nov 4, 13:00 UTC Europe (Germany): typical 307 ms (p50 TTFB) US (Central): typical 420 ms (p50 TTFB) Asia (Tokyo): typical 270 ms (p50 TTFB) South America (São Paulo): typical 658 ms (p50 TTFB)Nov 4, 14:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 416 ms (p50 TTFB) Asia (Tokyo): typical 497 ms (p50 TTFB) · 2 of 12 probes failed South America (São Paulo): typical 688 ms (p50 TTFB)Nov 4, 15:00 UTC Europe (Germany): typical 326 ms (p50 TTFB) US (Central): typical 1024 ms (p50 TTFB) Asia (Tokyo): typical 247 ms (p50 TTFB) South America (São Paulo): typical 661 ms (p50 TTFB)Nov 4, 16:00 UTC Europe (Germany): typical 301 ms (p50 TTFB) US (Central): typical 429 ms (p50 TTFB) Asia (Tokyo): typical 278 ms (p50 TTFB) South America (São Paulo): typical 656 ms (p50 TTFB)Nov 4, 17:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 409 ms (p50 TTFB) Asia (Tokyo): typical 250 ms (p50 TTFB) South America (São Paulo): typical 658 ms (p50 TTFB)Nov 4, 18:00 UTC Europe (Germany): typical 295 ms (p50 TTFB) US (Central): typical 406 ms (p50 TTFB) Asia (Tokyo): typical 222 ms (p50 TTFB) South America (São Paulo): typical 648 ms (p50 TTFB)Nov 4, 19:00 UTC Europe (Germany): typical 296 ms (p50 TTFB) US (Central): typical 400 ms (p50 TTFB) Asia (Tokyo): typical 222 ms (p50 TTFB) South America (São Paulo): typical 650 ms (p50 TTFB)Nov 4, 20:00 UTC Europe (Germany): typical 318 ms (p50 TTFB) US (Central): typical 412 ms (p50 TTFB) Asia (Tokyo): typical 216 ms (p50 TTFB) South America (São Paulo): typical 650 ms (p50 TTFB)Nov 4, 21:00 UTC Europe (Germany): typical 317 ms (p50 TTFB) US (Central): typical 397 ms (p50 TTFB) Asia (Tokyo): typical 211 ms (p50 TTFB) South America (São Paulo): typical 653 ms (p50 TTFB)Nov 4, 22:00 UTC Europe (Germany): typical 331 ms (p50 TTFB) US (Central): typical 401 ms (p50 TTFB) Asia (Tokyo): typical 223 ms (p50 TTFB) South America (São Paulo): typical 650 ms (p50 TTFB)Nov 4, 23:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 222 ms (p50 TTFB) South America (São Paulo): typical 656 ms (p50 TTFB)Nov 5, 00:00 UTC Europe (Germany): typical 333 ms (p50 TTFB) US (Central): typical 460 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 222 ms (p50 TTFB) South America (São Paulo): typical 1522 ms (p50 TTFB) · 1 of 12 probes failedNov 5, 01:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 1087 ms (p50 TTFB) · 2 of 12 probes failed Asia (Tokyo): typical 893 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 696 ms (p50 TTFB) · 2 of 12 probes failedNov 5, 02:00 UTC Europe (Germany): typical 348 ms (p50 TTFB) US (Central): typical 450 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 648 ms (p50 TTFB) South America (São Paulo): typical 1566 ms (p50 TTFB) · 2 of 12 probes failedNov 5, 03:00 UTC Europe (Germany): typical 327 ms (p50 TTFB) US (Central): typical 453 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 571 ms (p50 TTFB) South America (São Paulo): typical 718 ms (p50 TTFB) · 1 of 12 probes failedNov 5, 04:00 UTC Europe (Germany): typical 395 ms (p50 TTFB) US (Central): typical 1015 ms (p50 TTFB) Asia (Tokyo): typical 243 ms (p50 TTFB) South America (São Paulo): typical 691 ms (p50 TTFB) · 1 of 12 probes failedNov 5, 05:00 UTC Europe (Germany): typical 387 ms (p50 TTFB) US (Central): typical 1000 ms (p50 TTFB) Asia (Tokyo): typical 250 ms (p50 TTFB) South America (São Paulo): typical 1627 ms (p50 TTFB)Nov 5, 06:00 UTC Europe (Germany): typical 332 ms (p50 TTFB) US (Central): typical 454 ms (p50 TTFB) Asia (Tokyo): typical 420 ms (p50 TTFB) South America (São Paulo): typical 680 ms (p50 TTFB)Nov 5, 07:00 UTC Europe (Germany): typical 413 ms (p50 TTFB) US (Central): typical 434 ms (p50 TTFB) Asia (Tokyo): typical 535 ms (p50 TTFB) South America (São Paulo): typical 706 ms (p50 TTFB)Nov 5, 08:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 467 ms (p50 TTFB) Asia (Tokyo): typical 242 ms (p50 TTFB) South America (São Paulo): typical 684 ms (p50 TTFB)Nov 5, 09:00 UTC Europe (Germany): typical 318 ms (p50 TTFB) US (Central): typical 433 ms (p50 TTFB) Asia (Tokyo): typical 361 ms (p50 TTFB) South America (São Paulo): typical 710 ms (p50 TTFB)Nov 5, 10:00 UTC Europe (Germany): typical 300 ms (p50 TTFB) US (Central): typical 453 ms (p50 TTFB) Asia (Tokyo): typical 270 ms (p50 TTFB) South America (São Paulo): typical 1008 ms (p50 TTFB)Nov 5, 11:00 UTC Europe (Germany): typical 319 ms (p50 TTFB) US (Central): typical 443 ms (p50 TTFB) Asia (Tokyo): typical 274 ms (p50 TTFB) South America (São Paulo): typical 704 ms (p50 TTFB)Nov 5, 12:00 UTC Europe (Germany): typical 319 ms (p50 TTFB) US (Central): typical 446 ms (p50 TTFB) Asia (Tokyo): typical 386 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 716 ms (p50 TTFB)Nov 5, 13:00 UTC Europe (Germany): typical 324 ms (p50 TTFB) US (Central): typical 459 ms (p50 TTFB) Asia (Tokyo): typical 246 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 1014 ms (p50 TTFB)Nov 5, 14:00 UTC Europe (Germany): typical 320 ms (p50 TTFB) US (Central): typical 677 ms (p50 TTFB) Asia (Tokyo): typical 433 ms (p50 TTFB) South America (São Paulo): typical 1061 ms (p50 TTFB)Nov 5, 15:00 UTC Europe (Germany): typical 322 ms (p50 TTFB) US (Central): typical 452 ms (p50 TTFB) Asia (Tokyo): typical 241 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 696 ms (p50 TTFB)Nov 5, 16:00 UTC Europe (Germany): typical 299 ms (p50 TTFB) US (Central): typical 413 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 247 ms (p50 TTFB) South America (São Paulo): typical 706 ms (p50 TTFB)Nov 5, 17:00 UTC Europe (Germany): typical 315 ms (p50 TTFB) US (Central): typical 412 ms (p50 TTFB) Asia (Tokyo): typical 242 ms (p50 TTFB) South America (São Paulo): typical 697 ms (p50 TTFB)Nov 5, 18:00 UTC Europe (Germany): typical 300 ms (p50 TTFB) US (Central): typical 411 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 225 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB) · 1 of 12 probes failedNov 5, 19:00 UTC Europe (Germany): typical 314 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 194 ms (p50 TTFB) South America (São Paulo): typical 665 ms (p50 TTFB)Nov 5, 20:00 UTC Europe (Germany): typical 315 ms (p50 TTFB) US (Central): typical 407 ms (p50 TTFB) Asia (Tokyo): typical 197 ms (p50 TTFB) South America (São Paulo): typical 644 ms (p50 TTFB)Nov 5, 21:00 UTC Europe (Germany): typical 293 ms (p50 TTFB) US (Central): typical 412 ms (p50 TTFB) Asia (Tokyo): typical 216 ms (p50 TTFB) South America (São Paulo): typical 658 ms (p50 TTFB)Nov 5, 22:00 UTC Europe (Germany): typical 297 ms (p50 TTFB) US (Central): typical 422 ms (p50 TTFB) Asia (Tokyo): typical 218 ms (p50 TTFB) South America (São Paulo): typical 667 ms (p50 TTFB)Nov 5, 23:00 UTC Europe (Germany): typical 293 ms (p50 TTFB) US (Central): typical 423 ms (p50 TTFB) Asia (Tokyo): typical 220 ms (p50 TTFB) South America (São Paulo): typical 661 ms (p50 TTFB)Nov 6, 00:00 UTC Europe (Germany): typical 315 ms (p50 TTFB) US (Central): typical 418 ms (p50 TTFB) Asia (Tokyo): typical 247 ms (p50 TTFB) South America (São Paulo): typical 678 ms (p50 TTFB)Nov 6, 01:00 UTC Europe (Germany): typical 313 ms (p50 TTFB) US (Central): typical 401 ms (p50 TTFB) Asia (Tokyo): typical 270 ms (p50 TTFB) South America (São Paulo): typical 666 ms (p50 TTFB)Nov 6, 02:00 UTC Europe (Germany): typical 313 ms (p50 TTFB) US (Central): typical 413 ms (p50 TTFB) Asia (Tokyo): typical 252 ms (p50 TTFB) South America (São Paulo): typical 657 ms (p50 TTFB)Nov 6, 03:00 UTC Europe (Germany): typical 306 ms (p50 TTFB) US (Central): typical 424 ms (p50 TTFB) Asia (Tokyo): typical 240 ms (p50 TTFB) South America (São Paulo): typical 667 ms (p50 TTFB)Nov 6, 04:00 UTC Europe (Germany): typical 302 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 289 ms (p50 TTFB) South America (São Paulo): typical 665 ms (p50 TTFB)Nov 6, 05:00 UTC Europe (Germany): typical 304 ms (p50 TTFB) US (Central): typical 413 ms (p50 TTFB) Asia (Tokyo): typical 285 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB)Nov 6, 06:00 UTC Europe (Germany): typical 321 ms (p50 TTFB) US (Central): typical 419 ms (p50 TTFB) Asia (Tokyo): typical 246 ms (p50 TTFB) South America (São Paulo): typical 1521 ms (p50 TTFB)Nov 6, 07:00 UTC Europe (Germany): typical 307 ms (p50 TTFB) US (Central): typical 421 ms (p50 TTFB) Asia (Tokyo): typical 587 ms (p50 TTFB) South America (São Paulo): typical 662 ms (p50 TTFB)Nov 6, 08:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 444 ms (p50 TTFB) Asia (Tokyo): typical 282 ms (p50 TTFB) · 1 of 12 probes failed South America (São Paulo): typical 667 ms (p50 TTFB)Nov 6, 09:00 UTC Europe (Germany): typical 320 ms (p50 TTFB) US (Central): typical 432 ms (p50 TTFB) Asia (Tokyo): typical 249 ms (p50 TTFB) South America (São Paulo): typical 659 ms (p50 TTFB)Nov 6, 10:00 UTC Europe (Germany): typical 298 ms (p50 TTFB) US (Central): typical 417 ms (p50 TTFB) Asia (Tokyo): typical 287 ms (p50 TTFB) South America (São Paulo): typical 677 ms (p50 TTFB)Nov 6, 11:00 UTC Europe (Germany): typical 298 ms (p50 TTFB) US (Central): typical 1006 ms (p50 TTFB) Asia (Tokyo): typical 337 ms (p50 TTFB) South America (São Paulo): typical 658 ms (p50 TTFB)Nov 6, 12:00 UTC Europe (Germany): typical 322 ms (p50 TTFB) US (Central): typical 421 ms (p50 TTFB) · 1 of 12 probes failed Asia (Tokyo): typical 602 ms (p50 TTFB) South America (São Paulo): typical 667 ms (p50 TTFB)Nov 6, 13:00 UTC Europe (Germany): typical 322 ms (p50 TTFB) US (Central): typical 402 ms (p50 TTFB) Asia (Tokyo): typical 431 ms (p50 TTFB) South America (São Paulo): typical 654 ms (p50 TTFB)Nov 6, 14:00 UTC Europe (Germany): typical 319 ms (p50 TTFB) US (Central): typical 452 ms (p50 TTFB) Asia (Tokyo): typical 365 ms (p50 TTFB) South America (São Paulo): typical 663 ms (p50 TTFB)Nov 6, 15:00 UTC Europe (Germany): typical 303 ms (p50 TTFB) US (Central): typical 1038 ms (p50 TTFB) Asia (Tokyo): typical 592 ms (p50 TTFB) South America (São Paulo): typical 662 ms (p50 TTFB)Nov 6, 16:00 UTC Europe (Germany): typical 304 ms (p50 TTFB) US (Central): typical 436 ms (p50 TTFB) Asia (Tokyo): typical 273 ms (p50 TTFB) South America (São Paulo): typical 688 ms (p50 TTFB)Nov 6, 17:00 UTC Europe (Germany): typical 306 ms (p50 TTFB) US (Central): typical 417 ms (p50 TTFB) Asia (Tokyo): typical 269 ms (p50 TTFB) South America (São Paulo): typical 666 ms (p50 TTFB)Nov 6, 18:00 UTC Europe (Germany): typical 296 ms (p50 TTFB) US (Central): typical 410 ms (p50 TTFB) Asia (Tokyo): typical 221 ms (p50 TTFB) South America (São Paulo): typical 660 ms (p50 TTFB)Nov 6, 19:00 UTC Europe (Germany): typical 297 ms (p50 TTFB) US (Central): typical 407 ms (p50 TTFB) Asia (Tokyo): typical 224 ms (p50 TTFB) South America (São Paulo): typical 653 ms (p50 TTFB)Nov 6, 20:00 UTC Europe (Germany): typical 313 ms (p50 TTFB) US (Central): typical 393 ms (p50 TTFB) Asia (Tokyo): typical 217 ms (p50 TTFB) South America (São Paulo): typical 650 ms (p50 TTFB)Nov 6, 21:00 UTC Europe (Germany): typical 305 ms (p50 TTFB) US (Central): typical 402 ms (p50 TTFB) Asia (Tokyo): typical 217 ms (p50 TTFB) South America (São Paulo): typical 648 ms (p50 TTFB)Nov 6, 22:00 UTC Europe (Germany): typical 294 ms (p50 TTFB) US (Central): typical 411 ms (p50 TTFB) Asia (Tokyo): typical 218 ms (p50 TTFB) South America (São Paulo): typical 647 ms (p50 TTFB)20000Nov 3, 23:00 – Nov 6, 22:00 UTC: all 862 probes succeeded20000Nov 3, 23:00 – Nov 4, 23:00 UTC: all 300 probes succeededNov 5, 00:00 UTC: 1 of 12 probes failed — timeoutNov 5, 01:00 UTC: 2 of 12 probes failed — timeoutNov 5, 02:00 UTC: 1 of 12 probes failed — timeoutNov 5, 03:00 UTC: 1 of 12 probes failed — timeoutNov 5, 04:00 – Nov 5, 15:00 UTC: all 144 probes succeededNov 5, 16:00 UTC: 1 of 12 probes failed — [Errno 104] Connection reset by peerNov 5, 17:00 UTC: all 12 probes succeededNov 5, 18:00 UTC: 1 of 12 probes failed — timeoutNov 5, 19:00 – Nov 6, 11:00 UTC: all 204 probes succeededNov 6, 12:00 UTC: 1 of 12 probes failed — timeoutNov 6, 13:00 – Nov 6, 22:00 UTC: all 117 probes succeeded20000Nov 3, 23:00 – Nov 4, 01:00 UTC: all 36 probes succeededNov 4, 02:00 UTC: 1 of 12 probes failed — timeoutNov 4, 03:00 UTC: all 12 probes succeededNov 4, 04:00 UTC: 1 of 12 probes failed — timeoutNov 4, 05:00 UTC: all 12 probes succeededNov 4, 06:00 UTC: 1 of 12 probes failed — timeoutNov 4, 07:00 – Nov 4, 13:00 UTC: all 85 probes succeededNov 4, 14:00 UTC: 2 of 12 probes failed — timeoutNov 4, 15:00 – Nov 5, 00:00 UTC: all 120 probes succeededNov 5, 01:00 UTC: 1 of 12 probes failed — timeoutNov 5, 02:00 – Nov 5, 11:00 UTC: all 120 probes succeededNov 5, 12:00 UTC: 1 of 12 probes failed — timeoutNov 5, 13:00 UTC: 1 of 12 probes failed — [Errno 104] Connection reset by peerNov 5, 14:00 UTC: all 12 probes succeededNov 5, 15:00 UTC: 1 of 12 probes failed — timeoutNov 5, 16:00 – Nov 6, 07:00 UTC: all 192 probes succeededNov 6, 08:00 UTC: 1 of 12 probes failed — timeoutNov 6, 09:00 – Nov 6, 22:00 UTC: all 165 probes succeeded20000Nov 3, 23:00 – Nov 4, 23:00 UTC: all 300 probes succeededNov 5, 00:00 UTC: 1 of 12 probes failed — timeoutNov 5, 01:00 UTC: 2 of 12 probes failed — timeoutNov 5, 02:00 UTC: 2 of 12 probes failed — timeoutNov 5, 03:00 UTC: 1 of 12 probes failed — timeoutNov 5, 04:00 UTC: 1 of 12 probes failed — timeoutNov 5, 05:00 – Nov 5, 17:00 UTC: all 156 probes succeededNov 5, 18:00 UTC: 1 of 12 probes failed — timeoutNov 5, 19:00 – Nov 6, 22:00 UTC: all 333 probes succeeded
Europe (Germany)latest 294 · median 304 msUS (Central)latest 411 · median 420 msAsia (Tokyo)latest 218 · median 268 msSouth America (São Paulo)latest 647 · median 663 ms
Probe counts by region
Europe (Germany): 0 failed / 862 endpoint probesUS (Central): 8 failed / 861 endpoint probesAsia (Tokyo): 10 failed / 862 endpoint probesSouth America (São Paulo): 8 failed / 861 endpoint probes
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 iflytek 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)246 ms908 ms99.7%
Europe (Germany)302 ms793 ms100%
South America (São Paulo)660 ms1628 ms100%
US (Central)416 ms1076 ms99.7%

Measured from Asia (Tokyo), iflytek responds in 246 ms; from South America (São Paulo) the same API takes 660 ms — 2.7× 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 iflytek’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 iflytek’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 iflytek’s own reports are shown next to the measurements rather than folded into them.