PULSE

Operational

checked just now

US

38ms

median response time

EU

56ms

median response time

APAC

140ms

median response time

LatAm

18ms

median response time

ME

122ms

median response time

AF

192ms

median response time

APIOperational
Parsebotdata freshnessOperational

UNDER THE HOOD

What keeps the data fresh. A live dot means it ran on schedule.

Rain radarmoments ago
Latency probesmoments ago
Weather9 minutes ago
Forecasts4 hours ago
US forecast detail25 minutes ago
Air quality3 hours ago
Weather history14 hours ago
IP data9 hours ago
Currency rates22 hours ago
Tariff schedule23 hours ago
Disposable domains2 days ago
City data10 hours ago
Provider registry8 hours ago
Population23 days ago

BY ENDPOINT

Median response time per endpoint over the last 7 days, from the same 21 cities. A dash means not enough samples in that region yet.

ENDPOINTUSEUAPACLatAmMEAF
/address59ms79ms145ms
/bloc
/caller110ms310ms423ms
/carrier113ms324ms500ms
/city20ms31ms40ms15ms122ms176ms
/continent10ms12ms50ms9ms86ms8ms
/country10ms10ms42ms14ms121ms9ms
/currency11ms12ms39ms9ms119ms8ms
/currency/{from}/{to}17ms32ms44ms17ms113ms176ms
/date
/district11ms12ms47ms11ms120ms8ms
/domain19ms35ms42ms16ms104ms174ms
/elevation17ms32ms40ms12ms118ms179ms
/email26ms39ms48ms16ms180ms
/emoji11ms12ms46ms11ms122ms9ms
/hlr134ms336ms432ms
/holiday11ms12ms49ms9ms107ms9ms
/hts
/iban
/ip59ms154ms198ms145ms338ms451ms
/language11ms11ms39ms10ms96ms8ms
/mx16ms31ms46ms16ms115ms177ms
/name13ms15ms44ms15ms98ms12ms
/npi
/phone16ms17ms43ms107ms
/point18ms28ms39ms16ms94ms173ms
/postal14ms18ms54ms14ms116ms13ms
/state11ms12ms42ms10ms90ms9ms
/timezone61ms66ms73ms79ms114ms42ms
/useragent17ms27ms37ms14ms122ms174ms
/vat
/vin
/weather20ms30ms38ms18ms179ms

UPTIME

100.00% uptime

Jun 4, 2026Today

How this works

  • p50, not average
    The number in each region is the median response time. Half the requests from that region were faster, half slower. That is what a typical request feels like.
  • The whole trip, not just our server
    Measured from a real city to api.parseapi.com over the open internet, on a warm connection. The wire there, our server doing the work, the first byte back. Connection setup (DNS, TLS) is excluded because your client pays it once, not per request.
  • Close to you
    The API answers from nearby. A request from Chicago should not wait on another continent. Most of these milliseconds are the internet. We keep our part short.
  • Always current
    Parsebot re-measures from all 21 cities every 30 minutes.

PROBED FROM

NA

  • New York
  • Ashburn
  • Chicago
  • San Francisco
  • Los Angeles
  • Dallas
  • Toronto

EU

  • London
  • Frankfurt
  • Amsterdam
  • Zurich
  • Stockholm

APAC

  • Mumbai
  • Singapore
  • Hong Kong
  • Seoul
  • Tokyo
  • Sydney

LatAm

  • São Paulo

ME

  • Dubai

AF

  • Johannesburg