HomeOverview
Data API

AI API latency

Compare endpoint response times and availability across regions.

Download JSON
Overview LatencyUptime IncidentsLast probe · 18 Nov, 12:13 UTC
Fastest typical response
20ms

Fireworks AI · Asia (Tokyo)

Endpoint availability
99.8%

51,809 network probes · last 24h

Providers
45

API endpoints monitored

Regions
4

Independent probe locations

Response time over 24 hours

Typical response (p50 TTFB) · Europe (Germany)

Lower is faster
Hourly p50 edge latency; missing observations are gapsResponse time · ms08817526235013:0019:0001:0007:0012:00OpenAI · 2026-11-17T13:00 UTC · 226 ms p50OpenAI · 2026-11-17T14:00 UTC · 215 ms p50OpenAI · 2026-11-17T15:00 UTC · 208 ms p50OpenAI · 2026-11-17T16:00 UTC · 331 ms p50OpenAI · 2026-11-17T17:00 UTC · 333 ms p50OpenAI · 2026-11-17T18:00 UTC · 224 ms p50OpenAI · 2026-11-17T19:00 UTC · 217 ms p50OpenAI · 2026-11-17T20:00 UTC · 208 ms p50OpenAI · 2026-11-17T21:00 UTC · 212 ms p50OpenAI · 2026-11-17T22:00 UTC · 209 ms p50OpenAI · 2026-11-17T23:00 UTC · 214 ms p50OpenAI · 2026-11-18T00:00 UTC · 209 ms p50OpenAI · 2026-11-18T01:00 UTC · 331 ms p50OpenAI · 2026-11-18T02:00 UTC · 208 ms p50OpenAI · 2026-11-18T03:00 UTC · 323 ms p50OpenAI · 2026-11-18T04:00 UTC · 207 ms p50OpenAI · 2026-11-18T05:00 UTC · 326 ms p50OpenAI · 2026-11-18T06:00 UTC · 321 ms p50OpenAI · 2026-11-18T07:00 UTC · 213 ms p50OpenAI · 2026-11-18T08:00 UTC · 222 ms p50OpenAI · 2026-11-18T09:00 UTC · 232 ms p50OpenAI · 2026-11-18T10:00 UTC · 277 ms p50OpenAI · 2026-11-18T11:00 UTC · 331 ms p50OpenAI · 2026-11-18T12:00 UTC · 212 ms p50Anthropic · 2026-11-17T13:00 UTC · 200 ms p50Anthropic · 2026-11-17T14:00 UTC · 198 ms p50Anthropic · 2026-11-17T15:00 UTC · 198 ms p50Anthropic · 2026-11-17T16:00 UTC · 197 ms p50Anthropic · 2026-11-17T17:00 UTC · 202 ms p50Anthropic · 2026-11-17T18:00 UTC · 200 ms p50Anthropic · 2026-11-17T19:00 UTC · 196 ms p50Anthropic · 2026-11-17T20:00 UTC · 200 ms p50Anthropic · 2026-11-17T21:00 UTC · 198 ms p50Anthropic · 2026-11-17T22:00 UTC · 199 ms p50Anthropic · 2026-11-17T23:00 UTC · 198 ms p50Anthropic · 2026-11-18T00:00 UTC · 198 ms p50Anthropic · 2026-11-18T01:00 UTC · 196 ms p50Anthropic · 2026-11-18T02:00 UTC · 196 ms p50Anthropic · 2026-11-18T03:00 UTC · 197 ms p50Anthropic · 2026-11-18T04:00 UTC · 197 ms p50Anthropic · 2026-11-18T05:00 UTC · 198 ms p50Anthropic · 2026-11-18T06:00 UTC · 198 ms p50Anthropic · 2026-11-18T07:00 UTC · 188 ms p50Anthropic · 2026-11-18T08:00 UTC · 200 ms p50Anthropic · 2026-11-18T09:00 UTC · 202 ms p50Anthropic · 2026-11-18T10:00 UTC · 199 ms p50Anthropic · 2026-11-18T11:00 UTC · 201 ms p50Anthropic · 2026-11-18T12:00 UTC · 195 ms p50Google · 2026-11-17T13:00 UTC · 96 ms p50Google · 2026-11-17T14:00 UTC · 98 ms p50Google · 2026-11-17T15:00 UTC · 94 ms p50Google · 2026-11-17T16:00 UTC · 94 ms p50Google · 2026-11-17T17:00 UTC · 95 ms p50Google · 2026-11-17T18:00 UTC · 89 ms p50Google · 2026-11-17T19:00 UTC · 91 ms p50Google · 2026-11-17T20:00 UTC · 86 ms p50Google · 2026-11-17T21:00 UTC · 87 ms p50Google · 2026-11-17T22:00 UTC · 94 ms p50Google · 2026-11-17T23:00 UTC · 80 ms p50Google · 2026-11-18T00:00 UTC · 89 ms p50Google · 2026-11-18T01:00 UTC · 30 ms p50Google · 2026-11-18T02:00 UTC · 78 ms p50Google · 2026-11-18T03:00 UTC · 94 ms p50Google · 2026-11-18T04:00 UTC · 96 ms p50Google · 2026-11-18T05:00 UTC · 95 ms p50Google · 2026-11-18T06:00 UTC · 76 ms p50Google · 2026-11-18T07:00 UTC · 95 ms p50Google · 2026-11-18T08:00 UTC · 97 ms p50Google · 2026-11-18T09:00 UTC · 98 ms p50Google · 2026-11-18T10:00 UTC · 96 ms p50Google · 2026-11-18T11:00 UTC · 95 ms p50Google · 2026-11-18T12:00 UTC · 96 ms p50
OpenAIAnthropicGoogleUTC · lower is faster
View hourly values

Hourly median (p50), in milliseconds. Times are UTC. A dash means no measurement.

Hourly endpoint response times
Date · UTCOpenAIAnthropicGoogle
11-18 12:0021219596
11-18 11:0033120195
11-18 10:0027719996
11-18 09:0023220298
11-18 08:0022220097
11-18 07:0021318895
11-18 06:0032119876
11-18 05:0032619895
11-18 04:0020719796
11-18 03:0032319794
11-18 02:0020819678
11-18 01:0033119630
11-18 00:0020919889
11-17 23:0021419880
11-17 22:0020919994
11-17 21:0021219887
11-17 20:0020820086
11-17 19:0021719691
11-17 18:0022420089
11-17 17:0033320295
11-17 16:0033119794
11-17 15:0020819894
11-17 14:0021519898
11-17 13:0022620096
Looking for model response time? View time to first token (TTFT)

Speed index

Relative endpoint speed · 4 measured regions

Higher is faster

100 matches the fastest endpoint in every measured region. 50 means twice the latency in a region; scores are averaged across regions.

Full rankings & scoring method

Provider rankings

Choose the region closest to your application’s server · last 24 hours

Endpoint latency
How to read these metrics

Typical response · p50Half of successful timed probes were this fast or faster. Lower is better.

Slower responses · p9595% of successful timed probes were this fast or faster. This shows how latency behaves on slower requests.

AvailabilityThe share of successful network probes. Higher is better. Samples show how many probes were made.

TTFB measures the network and API endpoint, before a model generates an answer. It does not measure answer quality or generation speed. Compare model TTFT or read the measurement method. A dash means no timing data.

Fastest typical response first

Asia (Tokyo)

RankProviderTypical responsep50 TTFB · msSlower responsesp95 TTFB · msAvailabilitySuccessful probesSamplesLast 24 hours
01Fireworks AI20 ms65 ms100%288
02SambaNova26 ms80 ms100%289
03OpenRouter55 ms110 ms100%288
04upstage59 ms84 ms100%288
05Google68 ms124 ms100%289
06glm92 ms149 ms100%288
07meta-llama118 ms292 ms100%288
08kimi125 ms187 ms100%289
09ernie135 ms144 ms100%288
10TypeSafe145 ms153 ms100%288
11baichuan146 ms877 ms98.6%288
12novita151 ms234 ms100%288
13QwenCloud158 ms218 ms100%288
14Groq159 ms218 ms100%289
15Together AI160 ms289 ms100%289
16baseten163 ms190 ms100%288
17qwen165 ms234 ms100%288
18minimax167 ms218 ms100%288
19Cohere176 ms217 ms100%288
20xAI180 ms254 ms100%288
21DeepSeek183 ms253 ms100%288
22OpenAI209 ms294 ms100%289
23Cerebras209 ms271 ms100%289
24Anthropic225 ms292 ms100%289
25Perplexity232 ms305 ms100%288
26writer234 ms281 ms100%288
27reka239 ms577 ms100%288
28sarvam247 ms280 ms100%288
29Tencent TokenHub249 ms296 ms100%288
30iflytek271 ms1,724 ms98.3%288
31friendli276 ms455 ms100%288
32Mistral313 ms393 ms100%289
33stepfun325 ms819 ms100%288
34ai21328 ms439 ms100%288
35replicate329 ms426 ms99.7%288
36inference-net344 ms664 ms100%288
37hyperbolic372 ms450 ms100%288
38siliconflow373 ms405 ms100%288
39featherless374 ms461 ms100%288
40sensenova439 ms1,220 ms99.0%288
41deepinfra451 ms818 ms100%288
42nebius477 ms532 ms100%288
43doubao490 ms1,902 ms99.7%288
44nscale537 ms546 ms100%288
45aleph-alpha548 ms579 ms100%288
45 providersRegion report

Europe (Germany)

RankProviderTypical responsep50 TTFB · msSlower responsesp95 TTFB · msAvailabilitySuccessful probesSamplesLast 24 hours
01nebius33 ms96 ms100%288
02aleph-alpha56 ms90 ms100%288
03nscale70 ms73 ms100%288
04meta-llama90 ms152 ms100%288
05Fireworks AI91 ms339 ms100%288
06Google92 ms102 ms100%288
07OpenRouter97 ms107 ms100%288
08Mistral116 ms193 ms100%288
09baseten123 ms136 ms100%288
10Cohere132 ms194 ms100%288
11glm145 ms200 ms100%288
12inference-net146 ms390 ms100%288
13TypeSafe158 ms164 ms100%288
14reka176 ms212 ms100%288
15baichuan183 ms606 ms100%288
16Cerebras189 ms206 ms100%288
17Perplexity192 ms217 ms100%288
18Anthropic198 ms216 ms100%288
19replicate211 ms350 ms97.2%288
20OpenAI215 ms351 ms100%288
21Groq219 ms246 ms100%288
22writer223 ms295 ms100%288
23novita231 ms257 ms100%288
24Together AI234 ms283 ms100%288
25friendli245 ms385 ms99.3%288
26siliconflow248 ms275 ms100%288
27minimax254 ms282 ms100%288
28sarvam265 ms274 ms100%288
29hyperbolic272 ms632 ms100%288
30ernie282 ms310 ms100%288
31DeepSeek284 ms336 ms100%288
32iflytek286 ms760 ms99.7%288
33xAI307 ms325 ms100%288
34kimi312 ms404 ms100%288
35SambaNova331 ms370 ms99.7%288
36ai21336 ms471 ms100%288
37doubao350 ms808 ms99.7%288
38QwenCloud356 ms408 ms100%288
39qwen393 ms445 ms100%288
40sensenova397 ms1,160 ms99.0%288
41stepfun432 ms1,203 ms100%288
42Tencent TokenHub467 ms638 ms100%288
43deepinfra509 ms922 ms100%288
44upstage517 ms575 ms100%288
45featherless536 ms600 ms100%288
45 providersRegion report

South America (Santiago)

RankProviderTypical responsep50 TTFB · msSlower responsesp95 TTFB · msAvailabilitySuccessful probesSamplesLast 24 hours
01OpenRouter58 ms102 ms100%288
02baseten168 ms196 ms100%288
03TypeSafe175 ms187 ms100%288
04Cohere188 ms230 ms100%288
05Groq189 ms232 ms100%288
06xAI197 ms283 ms100%288
07Cerebras199 ms251 ms100%288
08Anthropic203 ms265 ms100%288
09OpenAI209 ms292 ms100%288
10inference-net220 ms418 ms100%288
11novita227 ms310 ms100%288
12Perplexity230 ms487 ms100%288
13Together AI249 ms643 ms100%288
14reka255 ms554 ms100%288
15meta-llama263 ms318 ms100%288
16Fireworks AI265 ms284 ms100%288
17writer268 ms367 ms100%288
18friendli269 ms402 ms100%288
19siliconflow280 ms285 ms100%288
20Mistral291 ms362 ms100%288
21kimi363 ms509 ms100%288
22SambaNova383 ms404 ms100%288
23baichuan396 ms1,383 ms99.3%288
24ai21404 ms513 ms99.3%288
25ernie426 ms607 ms100%288
26replicate433 ms629 ms99.0%288
27nebius435 ms479 ms100%288
28nscale440 ms446 ms100%288
29minimax444 ms621 ms100%288
30DeepSeek455 ms519 ms100%288
31aleph-alpha466 ms491 ms99.7%288
32glm533 ms548 ms100%288
33deepinfra570 ms944 ms100%288
34sarvam673 ms697 ms100%288
35sensenova693 ms1,914 ms98.3%288
36stepfun696 ms1,758 ms99.3%288
37featherless708 ms1,182 ms99.7%288
38upstage709 ms1,314 ms99.3%288
39iflytek735 ms1,766 ms99.7%288
40QwenCloud738 ms1,079 ms100%288
41qwen754 ms1,106 ms100%288
42doubao768 ms1,856 ms99.0%288
43hyperbolic770 ms810 ms100%288
44Tencent TokenHub793 ms1,077 ms100%288
45Google949 ms1,090 ms100%288
45 providersRegion report

US (Central)

RankProviderTypical responsep50 TTFB · msSlower responsesp95 TTFB · msAvailabilitySuccessful probesSamplesLast 24 hours
01Fireworks AI29 ms88 ms100%288
02Google44 ms106 ms100%287
03baseten48 ms61 ms100%288
04OpenRouter59 ms129 ms100%288
05Cohere63 ms111 ms100%288
06Cerebras74 ms145 ms100%288
07replicate78 ms153 ms99.3%288
08TypeSafe79 ms94 ms100%288
09siliconflow82 ms119 ms100%288
10novita91 ms163 ms100%288
11Perplexity91 ms151 ms100%288
12reka93 ms174 ms100%288
13Anthropic93 ms156 ms100%287
14inference-net100 ms445 ms100%288
15xAI105 ms193 ms100%287
16Together AI118 ms206 ms100%288
17writer124 ms184 ms100%288
18Groq126 ms201 ms100%288
19OpenAI136 ms211 ms100%287
20meta-llama141 ms237 ms100%288
21friendli162 ms220 ms100%288
22deepinfra176 ms373 ms100%288
23SambaNova179 ms237 ms100%288
24nebius179 ms222 ms100%288
25Mistral187 ms268 ms100%287
26nscale237 ms249 ms100%288
27featherless242 ms441 ms100%288
28baichuan245 ms1,005 ms98.3%288
29glm251 ms318 ms100%288
30ai21257 ms380 ms100%288
31aleph-alpha264 ms347 ms100%288
32ernie271 ms292 ms100%288
33hyperbolic275 ms460 ms100%288
34kimi286 ms497 ms100%288
35minimax286 ms305 ms100%288
36DeepSeek321 ms387 ms100%287
37upstage369 ms919 ms99.7%288
38sensenova403 ms1,167 ms98.6%288
39iflytek405 ms1,561 ms98.3%288
40qwen420 ms467 ms100%288
41QwenCloud422 ms458 ms100%288
42doubao448 ms1,496 ms98.3%288
43stepfun456 ms1,738 ms99.7%288
44sarvam478 ms520 ms100%288
45Tencent TokenHub581 ms631 ms100%288
45 providersRegion report

Is any AI API down right now?

2 confirmed outage(s) in the last 24 hours: sensenova, iflytek

45 providers · probed every 5 minutes from 4 regions · last probe Nov 18, 12:13 UTC

Status pages currently reporting an open incident: Anthropic (minor “Claude unable to join meetings”), OpenAI (minor “Costs API data is delayed”) — self-reported by the provider, checked Nov 18, 11:17 UTC. Our probes test the API host; errors limited to individual models are visible only to the provider.

Live status per provider: OpenAI API · Claude API (Anthropic) · Gemini API (Google) · Mistral API · DeepSeek API · xAI API · Groq API · Cerebras API · SambaNova API · Together AI API · Fireworks AI API · OpenRouter API · TypeSafe API

Endpoint availability · hourly probe results

Last 72 hours · UTC · newest time on the right · current hour is incomplete.

One row per provider. Each block shows the results of one hour’s endpoint probes, combined across regions. Adjacent hours with all successes or no data are joined.

all probes succeededsome failed (under half)half or more failedno probes recorded

Probe outcomes per provider, hour by hour, last 72 hours (all regions combined)Each row is a provider. Blocks show the outcome of hourly endpoint probes across all regions: all succeeded, some failed, half or more failed, or no data. Text counts follow the chart; a failed probe alone does not establish a provider outage.Nov 16Nov 17Nov 18nowNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3421 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3421 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 16, 08:00 UTC: all 960 probes succeededNov 16, 09:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Nov 16, 10:00 – Nov 16, 15:00 UTC: all 288 probes succeededNov 16, 16:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Nov 16, 17:00 – Nov 18, 05:00 UTC: all 1778 probes succeededNov 18, 06:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Nov 18, 07:00 – Nov 18, 12:00 UTC: all 252 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3422 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3421 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3421 probes succeededNov 15, 13:00 – Nov 18, 12:00 UTC: all 3421 probes succeededNov 15, 13:00 – Nov 16, 06:00 UTC: all 864 probes succeededNov 16, 07:00 UTC: 1 of 48 probes failed — South America (Santiago) (timeout)Nov 16, 08:00 – Nov 16, 16:00 UTC: all 432 probes succeededNov 16, 17:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout); South America (Santiago) (timeout); US (Central) (timeout)Nov 16, 18:00 – Nov 16, 23:00 UTC: all 289 probes succeededNov 17, 00:00 UTC: 5 of 48 probes failed — Asia (Tokyo) (timeout); South America (Santiago) (timeout); US (Central) (timeout)Nov 17, 01:00 UTC: all 48 probes succeededNov 17, 02:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout); US (Central) (timeout)Nov 17, 03:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout); Europe (Germany) (timeout); US (Central) (timeout)Nov 17, 04:00 – Nov 17, 12:00 UTC: all 432 probes succeededNov 17, 13:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Nov 17, 14:00 UTC: 1 of 48 probes failed — South America (Santiago) (timeout)Nov 17, 15:00 – Nov 17, 19:00 UTC: all 240 probes succeededNov 17, 20:00 UTC: 2 of 48 probes failed — Europe (Germany) (timeout); South America (Santiago) (timeout)Nov 17, 21:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout); Europe (Germany) (timeout); South America (Santiago) (timeout); US (Central) (timeout)Nov 17, 22:00 UTC: all 48 probes succeededNov 17, 23:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout); Europe (Germany) (timeout); South America (Santiago) (timeout); US (Central) (timeout)Nov 18, 00:00 – Nov 18, 09:00 UTC: all 480 probes succeededNov 18, 10:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout); South America (Santiago) (timeout); US (Central) (timeout)Nov 18, 11:00 – Nov 18, 12:00 UTC: all 60 probes succeededNov 15, 13:00 – Nov 15, 21:00 UTC: all 432 probes succeededNov 15, 22:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 15, 23:00 – Nov 16, 01:00 UTC: all 144 probes succeededNov 16, 02:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 16, 03:00 UTC: all 48 probes succeededNov 16, 04:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Nov 16, 05:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 16, 06:00 UTC: all 48 probes succeededNov 16, 07:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Nov 16, 08:00 UTC: all 48 probes succeededNov 16, 09:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 16, 10:00 – Nov 16, 16:00 UTC: all 336 probes succeededNov 16, 17:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 16, 18:00 UTC: 1 of 48 probes failed — South America (Santiago) ([Errno 104] Connection reset by peer)Nov 16, 19:00 – Nov 16, 22:00 UTC: all 192 probes succeededNov 16, 23:00 UTC: 1 of 49 probes failed — Asia (Tokyo) (timeout)Nov 17, 00:00 – Nov 17, 03:00 UTC: all 192 probes succeededNov 17, 04:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 17, 05:00 UTC: 6 of 48 probes failed — Asia (Tokyo) (timeout); US (Central) (timeout)Nov 17, 06:00 UTC: 6 of 48 probes failed — Asia (Tokyo) (timeout)Nov 17, 07:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Nov 17, 08:00 – Nov 17, 09:00 UTC: all 96 probes succeededNov 17, 10:00 UTC: 2 of 48 probes failed — South America (Santiago) (timeout); US (Central) (timeout)Nov 17, 11:00 – Nov 17, 14:00 UTC: all 192 probes succeededNov 17, 15:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout); Europe (Germany) (timeout); South America (Santiago) (timeout); US (Central) ([Errno 104] Connection reset by peer)Nov 17, 16:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Nov 17, 17:00 – Nov 18, 00:00 UTC: all 384 probes succeededNov 18, 01:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 18, 02:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 18, 03:00 – Nov 18, 06:00 UTC: all 192 probes succeededNov 18, 07:00 UTC: 2 of 48 probes failed — US (Central) (timeout)Nov 18, 08:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Nov 18, 09:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 18, 10:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Nov 18, 11:00 – Nov 18, 12:00 UTC: all 60 probes succeeded
openaianthropicgooglemistraldeepseekxaigroqcerebrassambanovatogetherfireworksopenroutertypesafesensenovaiflytek
Probe counts by provider
OpenAI: 0 failed / 3,422 endpoint probesAnthropic: 0 failed / 3,422 endpoint probesGoogle: 0 failed / 3,422 endpoint probesMistral: 0 failed / 3,422 endpoint probesDeepSeek: 0 failed / 3,421 endpoint probesxAI: 0 failed / 3,421 endpoint probesGroq: 0 failed / 3,422 endpoint probesCerebras: 0 failed / 3,422 endpoint probesSambaNova: 3 failed / 3,422 endpoint probesTogether AI: 0 failed / 3,422 endpoint probesFireworks AI: 0 failed / 3,421 endpoint probesOpenRouter: 0 failed / 3,421 endpoint probesTypeSafe: 0 failed / 3,421 endpoint probessensenova: 29 failed / 3,421 endpoint probesiflytek: 40 failed / 3,421 endpoint probes

Full incident log

Fastest by region

Lowest typical response (p50 TTFB) · last 24 hours

Methodology

Which AI API is fastest right now?

As of November 18, 2026, the fastest-responding AI inference API by edge latency (time-to-first-byte) is fireworks at 20 ms p50, measured from Asia (Tokyo) (100% uptime, n=288). Rankings differ by region.

Edge latency (TTFB) measures the network and API endpoint; inference TTFT is measured separately. Methodology

All 45 providers