Data Availability Commitment
County GIS endpoints go stale, move, or quietly stop answering queries. Most parcel-data vendors serve a cached copy and hope you don't notice. We do the opposite: we check every endpoint daily and tell you the moment one breaks.
01 — What we commit to
- Detect within 24 hours. An automated check probes all 134 counties' endpoints every day — not just whether the layer loads, but whether it still answers real queries.
- Flag immediately. A degraded or down endpoint is marked in every API response (
endpoint_status) and on the public status page while it's being fixed. - Repair or retire within 7 business days. We investigate, find the replacement layer, and restore it. If we can't, the county is marked down and its atlas page says so — no silent dead links.
02 — What it is not
This is not an application-uptime SLA. It covers the third-party county endpoints the atlas indexes, not our own servers. We don't run the county's ArcGIS server and can't promise it stays up — only that we'll catch it within a day and be honest about it. For website and API uptime (99.5%, with service credits on Team and Enterprise), see the Enterprise SLA.
03 — Check it yourself
The status page is public and live — no account, no sales call. See which endpoints are healthy right now.
View current endpoint health →04 — By plan
| Plan | Data Availability | Application uptime SLA |
|---|---|---|
| Free · Individual · Pro | Daily check, public status, repair commitment | — |
| Team · Enterprise | Same + named contact for repair escalation | 99.5% + service credits |
Enterprise service credits: 10% for missing 99.5%, 25% for 95–98.9%, 50% below 95% — capped at 50% of the monthly fee, claimed within 30 days of the incident.
05 — Questions
What exactly do you commit to?
We check every county REST endpoint in the atlas once a day. If one stops answering queries, we detect it within 24 hours, flag it in the API response and on the public status page, and investigate or replace it within 7 business days. If we can't restore it in that window, we mark the county down and update its atlas page so you're never quietly handed a dead endpoint.
Is this an uptime SLA?
No. This is about the county data endpoints we index, not our own servers. Application uptime — the website and the Parcel Data API — is a separate 99.5% SLA available to Team and Enterprise plans, with service credits. The Data Availability Commitment covers the third-party county layers the atlas points at.
What if the county takes their own server down?
We don't control the county's ArcGIS server, and we don't pretend to. The commitment is that we'll notice within a day and tell you — in the API response and here — instead of serving a cached or broken layer as if it were live. The repair clock starts when our check detects the problem.
Which endpoints does it cover?
Endpoints in the atlas that returned a healthy result on the previous check. A county we've never been able to verify is listed honestly as such; the commitment applies to keeping working endpoints working, and to flagging the ones that break.