City, Berlin vs Japan Neighborhoods

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms861117
P95 · ms3231732
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseVaries per dataset (many CC-BY / dl-de-by-2.0)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Berlin vs Japan Neighborhoods: common questions

Which is more reliable, City, Berlin or Japan Neighborhoods?

On our scheduled checks, Japan Neighborhoods leads on measured uptime — City, Berlin at 99.02% versus Japan Neighborhoods at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, City, Berlin or Japan Neighborhoods?

Japan Neighborhoods has the lower median latency in our checks — City, Berlin responds in 861 ms versus Japan Neighborhoods at 117 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do City, Berlin and Japan Neighborhoods need an API key?

Neither needs a paid key — City, Berlin is callable with no signup, and Japan Neighborhoods is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Berlin and Japan Neighborhoods from the browser?

Only Japan Neighborhoods is browser-friendly — it returns CORS headers over HTTPS. City, Berlin needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are City, Berlin and Japan Neighborhoods free for commercial use?

City, Berlin has unclear commercial terms, and Japan Neighborhoods has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.