Public Status Page & Incident Signal Agent
Pricing
from $5.00 / 1,000 useful status signal results
Public Status Page & Incident Signal Agent
Summarize public status pages into overall status, component hints, incidents, maintenance windows, impact terms, evidence URLs, and change hashes.
Pricing
from $5.00 / 1,000 useful status signal results
Rating
0.0
(0)
Developer
jack su
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Turn public SaaS status pages or public incident pages into compact operational-risk signals for AI agents, vendor review, customer support triage, sales research, and monitoring workflows.
The Actor fetches public HTTP/HTTPS pages with lightweight requests and returns one source-linked record per input page:
- overall status, such as
operational,degraded,partial_outage,major_outage, ormaintenance - component/status hints
- active and recent incident snippets
- maintenance-window hints
- impact terms such as outage, degraded performance, latency, errors, or maintenance
- matched focus components
- evidence URLs
- stable
incidentHashandchangeStatus - confidence, completeness, missing fields, and diagnostics
How To Use It
For a first-pass status signal, provide public status or incident page URLs and leave focus components empty:
{"statusPageUrls": ["https://status.openai.com/"],"focusComponents": [],"previousIncidentRecords": [],"maxIncidents": 10,"requestTimeoutSecs": 20}
For targeted checks, add focusComponents such as API, dashboard,
database, payments, login, or a named product area. If focus components
are supplied, useful-result charging requires at least one matched component or
service term in the public status evidence.
For repeat monitoring, pass previous dataset records from this Actor in
previousIncidentRecords. If the incident hash is unchanged, the record is
written as changeStatus: "unchanged" without the useful event charge.
Good Fits
- Check whether a public vendor status page currently shows operational issues.
- Feed AI agents a small evidence-backed status signal before contacting customers or escalating support.
- Compare a current status page result with a previous record and avoid paying for unchanged results.
- Review public incident pages during vendor diligence without running a broad crawler.
Not A Fit
- This is not an SLA verifier, uptime monitor, vulnerability scanner, private trust-portal downloader, or legal compliance certification.
- It does not log in, use cookies, bypass paywalls, render JavaScript, submit forms, or crawl private systems.
- It does not guarantee official availability or incident severity. It organizes public page evidence.
Example Input
{"statusPageUrls": ["https://status.openai.com/"],"focusComponents": ["API"],"previousIncidentRecords": [],"maxIncidents": 10,"requestTimeoutSecs": 20}
statusPageUrls must be public HTTP/HTTPS pages. URLs containing credentials, path parameters, query parameters, fragments, localhost, private-network hosts, .local names, or token-like account paths are rejected.
Output
{"status": "ok","inputUrl": "https://status.example.com","finalUrl": "https://status.example.com","siteOriginUrl": "https://status.example.com","changeStatus": "new","pageTitle": "Example Status","overallStatus": "degraded","overallStatusText": "Dashboard Degraded Performance","components": [{"name": "API","status": "operational","evidenceSnippet": "API Operational"}],"componentCount": 1,"activeIncidents": [{"title": "Investigating API elevated errors","status": "investigating","impact": "degraded","date": "2026-06-10","summarySnippet": "Investigating API elevated errors - Degraded performance - Jun 10, 2026"}],"recentIncidents": [],"incidentCount": 1,"maintenanceHints": [],"maintenanceCount": 0,"impactTerms": ["degraded performance", "degraded", "errors", "incident"],"matchedFocusComponents": ["API"],"incidentHash": "stable-sha256","previousIncidentHash": "","evidenceUrls": ["https://status.example.com"],"confidenceScore": 0.86,"completenessScore": 0.93,"diagnostics": []}
Pricing Behavior
The intended Apify pricing model is pay-per-event:
apify-actor-start: small run-start eventuseful-status-signal-result: charged only for useful public status/incident signal records
The useful event is not charged for failed fetches, private-network inputs, query-token inputs, unsupported URLs, unchanged records, pages without useful public status evidence, or focus-component misses.
Do not configure apify-default-dataset-item for this Actor.
Safety
- Public HTTP/HTTPS pages only.
- Same-site redirects only.
- HTML/text response size is capped at 3 MB, including gzip decompression.
- Credentials, query strings, fragments, path params, sensitive account paths, token-like path segments, localhost, private IPs, non-global IPs, and
.localhosts are rejected or redacted. - Error messages are generic and do not persist exception details.