Api Status Dashboard Scraper
Pricing
Pay per usage
Go to Apify Store
Api Status Dashboard Scraper
Pricing
Pay per usage
Rating
0.0
(0)
Developer

Donny Nguyen
Maintained by Community
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Scrape status pages for multiple services to build a unified monitoring dashboard. Supports Statuspage.io, Instatus, and other common status page platforms used by SaaS companies.
Features
- Multi-service monitoring across any number of status page URLs simultaneously
- Overall status extraction with indicator detection (operational, degraded, major outage)
- Component-level status for individual service components and subsystems
- Active incident tracking with incident titles, severity, and update history
- Uptime data extraction when available from the status page
- Automatic platform detection for Statuspage.io, Instatus, and generic HTML pages
Use Cases
- Build a unified status dashboard for all third-party APIs your application depends on
- Monitor SLA compliance for service providers and vendor management
- Create automated alerting workflows when services experience outages
- Track historical uptime and incident frequency for vendor evaluation
- Feed status data into DevOps monitoring tools and incident management platforms
Input Configuration
| Parameter | Type | Default | Description |
|---|---|---|---|
statusPages | array | ["https://status.openai.com", "https://www.githubstatus.com"] | Status page URLs to scrape |
Output Format
Each status page produces a dataset item containing:
serviceName- Name of the service from the status pageoverallStatus- Current overall status (operational, degraded, outage)statusUrl- The status page URLcomponents- Array of components with individual statusactiveIncidents- Array of current active incidentsincidentCount- Number of active incidentsscrapedAt- ISO timestamp of the scrape
Supported Platforms
This actor works with Statuspage.io (used by GitHub, Stripe, Twilio), Instatus, and most HTML-based status pages with standard markup.
Limitations
- Some status pages use heavy JavaScript rendering and may not be fully parseable
- Real-time status updates require periodic scheduling of the actor
- Historical uptime data availability depends on the status page provider