GrünstromIndex vs openSenseMap

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

Uptime · 30d
Uptime · 90d73.5%90.2%
Uptime · 30d73.3%90.0%
P50 · ms1072655
P95 · ms41194139
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen data (license set per senseBox; often public domain)
Free tierFree under fair-use policyFree (open-source citizen-science platform)
Rate limitFair-use (paid tiers for higher limits)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GrünstromIndex vs openSenseMap: common questions

Which is more reliable, GrünstromIndex or openSenseMap?

On our scheduled checks, openSenseMap leads on measured uptime — GrünstromIndex at 73.5% versus openSenseMap at 90.2% 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, GrünstromIndex or openSenseMap?

openSenseMap has the lower median latency in our checks — GrünstromIndex responds in 1072 ms versus openSenseMap at 655 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 GrünstromIndex and openSenseMap need an API key?

Neither needs a paid key — GrünstromIndex is callable with no signup, and openSenseMap is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GrünstromIndex and openSenseMap from the browser?

Yes — both GrünstromIndex and openSenseMap send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are GrünstromIndex and openSenseMap free for commercial use?

GrünstromIndex has unclear commercial terms, and openSenseMap 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.