Querying service uptime
Response format
Periods and granularity
Available periods
Granularity options
Period × granularity compatibility
Not all combinations are available:
Hourly granularity is not available for periods of 1 year or longer due to data volume.
Uptime data sources
Thesource field indicates how uptime data is derived:
Component uptime
Query uptime for a specific component of a service:devhelm services components github.
Components also include inline uptime summaries (24h, 7d, 30d) in the component listing response, so you can get a quick overview without separate uptime queries.
Inline uptime summary
When listing components, each includes anuptime object:
Data access tiers
Historical data depth depends on your plan:
Requesting a period that exceeds your plan’s limit returns only the available data within your tier. No error is returned — the response simply contains fewer buckets.
Uptime response fields
Bucket fields
Service catalog browsing is public, but uptime data requires authentication and respects your plan’s data access tier.
Next steps
Services
Browse the catalog and view component-level detail.
Service incidents
View outages that caused uptime dips.
Dependencies
Track services and get alerted on status changes.
API Reference
Full Status Data API endpoint reference.