Cloudflare Status & Incident History Scraper
Pricing
from $20.00 / 1,000 results
Cloudflare Status & Incident History Scraper
Scrapes the public Cloudflare status page history into structured incident and maintenance records. Each record includes the incident ID, title, impact classification, inferred status (resolved, monitoring, in-progress, identified, investigating, or active), status message, time-window text, and a c
Pricing
from $20.00 / 1,000 results
Rating
0.0
(0)
Developer
Wes Shields
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Scrapes the public Cloudflare status page history into structured incident and maintenance records. Each record includes the incident ID, title, impact classification, inferred status (resolved, monitoring, in-progress, identified, investigating, or active), status message, time-window text, and a canonical detail URL. Ideal for SRE teams, uptime monitoring, and incident-response automation.
Features
- Structured JSON output with recordType (incident or maintenance), impact, and inferred status
- Canonical detail URLs constructed from verified incident IDs
- robots.txt compliance check before every run
- Configurable caps: maxRecords, maxRequests, maxRunSeconds, maxResponseBytes
- Rate-limited requests with configurable minimum interval (default 1500 ms)
- Automatic retries on HTTP 429 and 5xx responses
- Run summary with metrics: requests, retries, bytes downloaded, records emitted
- Optional filtering: includeScheduled toggle to exclude planned maintenance
Use Cases
- SRE and DevOps incident monitoring and alerting pipelines
- Uptime and reliability tracking for Cloudflare-dependent services
- Historical incident analysis and post-mortem data enrichmentment
- Automated status-page aggregation across infrastructure providers
- Competitive intelligence on CDN and edge-network reliability
FAQ
Q: What data source does this actor use? A: The public Cloudflare status history page at cloudflarestatus.com/history. No authentication or API key is required.
Q: How are incidents vs. maintenance distinguished? A: The impact field from Cloudflare's structured data is used — entries marked 'maintenance' are classified as maintenance records; all others are incidents.
Q: Can I exclude scheduled maintenance? A: Yes — set includeScheduled to false in the input to receive only incident records.
Q: Is this scraper respectful of the source? A: Yes — it checks robots.txt before scraping, uses rate-limited requests, and caps response size and run duration.
