Skip to main content
By the end of this guide, you’ll know how to query uptime data for third-party services, select the right periods and granularity, and build uptime reports.
For conceptual background, see Uptime data.

​
Query service uptime

devhelm status-data uptime github --period 30d --granularity daily
The response includes the overall uptime percentage and time-bucketed data: 
{
  "overallUptimePct": 99.95,
  "period": "30d",
  "granularity": "daily",
  "source": "vendor_reported",
  "buckets": [
    { "timestamp": "2026-03-14T00:00:00Z", "uptimePct": 100.0, "totalPolls": 288 },
    { "timestamp": "2026-03-15T00:00:00Z", "uptimePct": 99.8, "totalPolls": 288 }
  ]
}

​
Choose the right period and granularity

Use casePeriodGranularity
Ops dashboard (real-time)24hhourly
Weekly team review7ddaily
Monthly SLA report30ddaily
Quarterly business review90ddaily or monthly
Annual vendor evaluation1ymonthly
Hourly granularity is not available for periods of 1 year or longer.

​
Component-level uptime

Drill into specific components for more granular reporting: 
devhelm status-data services components github

curl "https://api.devhelm.io/api/v1/services/github/components/<component-id>/uptime?period=30d" \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN"
Components also include inline uptime summaries (24h, 7d, 30d) in the component listing, so you can get a quick overview without separate queries.

​
Build a dependency uptime report

Query uptime for all your dependencies to build a report:
1

List your dependencies

devhelm status-data dependencies list
2

Query uptime for each

for slug in github stripe aws vercel; do
  echo "=== $slug ==="
  curl -s "https://api.devhelm.io/api/v1/services/$slug/uptime?period=30d&granularity=daily" \
    -H "Authorization: Bearer $DEVHELM_API_TOKEN" | jq '.overallUptimePct'
done
3

Correlate with incidents

For services with low uptime, check their incident history:
curl "https://api.devhelm.io/api/v1/services/github/incidents?status=resolved" \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN"

​
Data access tiers

Historical data depth depends on your plan:
PlanMax aggregated dataMax incident history
Free90 days90 days
Pro365 daysUnlimited
Team730 daysUnlimited
Business+UnlimitedUnlimited
Requesting data beyond your plan’s limit returns only available data — no error, just fewer buckets.

​
Next steps

Uptime data reference

Full period/granularity matrix and response format.

Service incidents

View outages that caused uptime dips.

Status Data guide

Full Status Data system overview.