Status
Overall
Checking…
- API base
https://api.staging.agrovisio.ai- Last checked
- -
- Next check
- every 60 s while this page is open
| Component | State | Detail |
|---|---|---|
Data API (/v1/health) | checking |
Historical uptime and incident notices are published on status.agrovisio.ai. Report anything that looks wrong to support@agrovisio.aiwith the X-Request-Id of the failing call.
How this page works
Section titled “How this page works”The checks run in your browser, not on a server, so they show whether the API
is reachable from where you are - the same path your integration will use.
GET /v1/health needs no key and is not rate limited; the OpenAPI document is
fetched to confirm the reference is being served; GET /v1/status, when
present, adds per-component detail (database, queue, satellite providers).
An “unreachable” row can also mean that this site’s origin is not on the API’s
CORS list. A plain curl from the same machine tells the two apart:
curl -s -i "$BASE/health"Service levels
Section titled “Service levels”| Starter / Growth | Scale / Enterprise | |
|---|---|---|
| Availability (monthly) | 99.0 % | 99.5 % with SLA credits |
| p95 latency, standard reads | < 800 ms | < 400 ms |
| Sentinel-2 / Sentinel-1 freshness | < 48 h after the scene | < 24 h |
Historical uptime, scheduled maintenance and incident post-mortems are
published on status.agrovisio.ai. During maintenance the API answers
503 service_unavailable with a Retry-After header.