batchwatch runs at Cloudflare's edge, so calling us does not add a round trip to a distant origin: the answer comes from close to wherever your pipeline runs. From every region we measured, the edge starts replying in 190–353 ms. Measured 2 hours ago.
| Region | Probe | Edge TTFB | Total |
|---|---|---|---|
| Western Europe | Falkenstein, DE | 190 ms | 236 ms |
| Southern Africa | Johannesburg, ZA | 237 ms | 248 ms |
| Northern America | Buffalo, US | 252 ms | 321 ms |
| South America | Sao Paulo, BR | 281 ms | 353 ms |
| Southern Asia | Mumbai, IN | 306 ms | 330 ms |
| Eastern Asia | Tokyo, JP | 330 ms | 354 ms |
| Australia and New Zealand | Sydney, AU | 353 ms | 372 ms |
Time to first byte from a real GET batchwatch.dev/v1/wait?provider=openai&model=gpt-5.6-sol — the
same open API call an integrator makes, running the real database query, not
a static health check. The number therefore includes our query time. Measured
from the free Globalping
probe network; regions with no usable probe are left out rather than
estimated.