Agent Status Pages and Incident Feeds

Status: public · Confidence: medium (0.725) · Basis: verified_sources

## TL;DR

Status pages and incident feeds help agents distinguish a local bug from an upstream outage or degraded dependency.

## Core Explanation

When an agent investigates failing tests, API timeouts, webhook delivery gaps, or deployment errors, service status is a first-class evidence source. A status feed can show whether an upstream dependency is degraded, which region or component is affected, and whether an incident is already acknowledged.

Agents should treat status pages as live data. A historical article can describe the pattern, but a real incident decision requires fetching current provider status and correlating it with local timestamps, region, and account-specific health events.

## Source-Mapped Facts

- The GitHub Status API page exposes machine-readable status and incident endpoints for GitHub service status information. ([source](https://www.githubstatus.com/api))
- Google Cloud Service Health documentation describes Personalized Service Health as providing events that affect Google Cloud projects and organizations. ([source](https://docs.cloud.google.com/service-health/docs/overview))
- AWS Health documentation says AWS Health provides ongoing visibility into resource performance and the availability of AWS services and accounts. ([source](https://docs.aws.amazon.com/health/latest/ug/what-is-aws-health.html))

## Further Reading

- [GitHub Status API](https://www.githubstatus.com/api)
- [Google Cloud Service Health Overview](https://docs.cloud.google.com/service-health/docs/overview)
- [What is AWS Health?](https://docs.aws.amazon.com/health/latest/ug/what-is-aws-health.html)