Status Page Incident Intel Extractor

Extract incident history, affected services, severity, timestamps, status updates, and customer-impact signals from public status pages.

Why This Actor Is Useful

This actor turns public status-page incident updates into reliability intelligence. Instead of reading incident timelines by hand, users get rows with vendor, affected service, status, timestamps, customer impact, and latest update.

It works best on public incident summaries, status-page exports, or pasted status update text.

What It Extracts

• vendorName - Vendor.
• incidentTitle - Incident title.
• incidentStatus - Status.
• severity - Severity.
• affectedService - Affected service.
• startedAt - Started at.
• resolvedAt - Resolved at.
• customerImpact - Customer impact.
• latestUpdate - Latest update.
• sourceUrl - Source URL.
• evidenceText - Evidence.

Practical Workflows

• Monitor SaaS vendors for outage patterns.
• Prepare vendor-risk notes before renewal.
• Track affected services and customer-impact statements.
• Build reliability dashboards from public incident text.

Input

Paste one or more public status pages, incident history pages, postmortems, or incident update URLs. The actor extracts incident title, status, severity, affected service, start and resolution time, customer impact, and latest update.

• startUrls - Add public status pages, incident history pages, or incident update URLs from SaaS vendors and service providers.
• sourceText - Optional: paste incident summaries, status updates, outage timelines, or customer-impact messages from public status pages.
• maxResults - Stop after this many useful rows. Most users can leave this at 100.
• requestTimeoutSecs - How long to wait for each URL. Increase only for slow public pages.

Example Input

{
    "sourceText": [
        "AcmeCloud Status: Investigating elevated API error rates affecting Payments API. Incident started August 8, 2026 14:05 UTC. Customers may see failed checkout requests. Latest update: engineers identified database failover latency. Status: monitoring. Resolved August 8, 2026 15:40 UTC.",
        "NimbusCRM incident report - Partial outage for email sync service. Started 2026-08-07 09:20 UTC. Major impact for EU customers. Update: queued messages are being replayed. Current status: resolved."
    ],
    "maxResults": 10,
    "requestTimeoutSecs": 20
}

Example Output

{
    "vendorName": "AcmeCloud",
    "incidentTitle": "Investigating elevated API error rates affecting Payments API",
    "incidentStatus": "Investigating",
    "severity": "elevated",
    "affectedService": "Payments API",
    "startedAt": "August 8, 2026 14:05 UTC",
    "resolvedAt": "August 8, 2026 15:40 UTC",
    "customerImpact": "Customers may see failed checkout requests",
    "latestUpdate": "engineers identified database failover latency",
    "sourceUrl": "pasted://source-1",
    "evidenceText": "AcmeCloud Status: Investigating elevated API error rates affecting Payments API. Incident started August 8, 2026 14:05 UTC. Customers may see failed checkout requests. Latest update: engineers identified database failover latency. Status: monitoring. Resolved"
}

Reliability Notes

The actor is intentionally lightweight and fast. It does not try to bypass captcha systems, private pages, paywalls, or login walls. When a site blocks direct fetching, paste the public visible text into sourceText; the same actor-specific parser will still produce structured rows.

Limitations

• The actor extracts only information present in the supplied source.
• Missing source details remain blank instead of being guessed.
• Highly unusual wording may require pasted text or cleaner source snippets for best results.

Output

Rows are written to the default Apify dataset with actor-specific fields and source evidence. The output is designed for spreadsheets, dashboards, client audits, procurement notes, SEO reports, developer research, and other marketplace buyer workflows.