Last updated: July 19, 2026
This SLA applies to paid ParseAPI subscriptions. It describes what we aim to deliver and how credits work if we miss uptime targets. Free plans are best-effort and not covered here.
“Service” means the public API at api.parseapi.com for documented endpoints (postal, IP, email, user agent, country, state, city, continent, and related health checks). Dashboard and billing are separate — outages there don’t count against API uptime unless we say otherwise.
We target 99.9% monthly uptime for the API, measured as successful responses (non-5xx) on core lookup routes, excluding scheduled maintenance we announce in advance.
Uptime is calculated per calendar month. If we don’t hit 99.9%, eligible customers can request a service credit (see section 5).
We optimize for speed — that’s the product. Where we publish numbers, they’re measured from US infrastructure against production. We don’t guarantee global p95 latency in this SLA; regional performance varies with distance and routing.
Paid plans include email support at support@parseapi.com.
“Business day” means Monday–Friday, excluding US federal holidays. Support covers account, billing, and API usage questions — not building your app for you.
If monthly API uptime falls below 99.9% and you’re on a paid plan, you may request a credit equal to 10% of that month’s subscription fee for the affected ParseAPI product. Credits apply to future invoices — not cash refunds unless required by law.
To claim: email support@parseapi.com within 30 days after the month ends, with the dates/times you saw failures. We’ll verify against our logs and apply credits if the SLA was missed.
This SLA doesn’t apply when downtime or errors are caused by:
We may update this SLA. The date at the top changes when we do. Material changes won’t reduce credits for an already-paid month retroactively.
Part of your paid subscription under our Terms of Service. Custom uptime or support terms: enterprise@parseapi.com.