bng2latlong vs PostcodeData.nl
Same instrument, two spec sheets — measured, not claimed.
bng2latlong vs PostcodeData.nl: common questions
Which is more reliable, bng2latlong or PostcodeData.nl?
On our scheduled checks, PostcodeData.nl leads on measured uptime — bng2latlong at 95.1% versus PostcodeData.nl 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, bng2latlong or PostcodeData.nl?
bng2latlong has the lower median latency in our checks — bng2latlong responds in 524 ms versus PostcodeData.nl at 692 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 bng2latlong and PostcodeData.nl need an API key?
Neither needs a paid key — bng2latlong is callable with no signup, and PostcodeData.nl is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call bng2latlong and PostcodeData.nl from the browser?
Only bng2latlong is browser-friendly — it returns CORS headers over HTTPS. PostcodeData.nl needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are bng2latlong and PostcodeData.nl free for commercial use?
bng2latlong has unclear commercial terms, and PostcodeData.nl 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.