Vendor status digest — the last 30 days across 11 monitored vendors

Most recent incidents, as posted by each vendor

Methodology

• Merlonix independent monitoring of each vendor’s published status page, polled around the clock; every figure is a fold over the status snapshots Merlonix recorded in the window.
• Window: the 30 UTC days ending 2026-10-17.
• incidents_total counts distinct vendor-posted incidents whose start time falls in the window, excluding scheduled maintenance and "operating normally" resolution notices. by_impact.unknown holds incidents the vendor posted without a severity label.
• maintenance_windows counts vendor-posted scheduled maintenance entries starting in the window.
• observed_days counts distinct UTC days with at least one recorded snapshot; the fetcher records only when the vendor’s status page content changes, so a quiet vendor has few snapshot days. coverage_days runs from the first in-window observation to the end of the window.
• enough_history is true when a vendor has at least 20 coverage days and 24 observations; only those vendors feed the aggregate.
• Day-level status availability (the share of days a status page was not fully operational) is deliberately not published in this version: the AWS feed reader mis-read stale RSS items as open incidents until 2026-09-05 (TD-2619), and the affected snapshots remain in the window until early October.
• Nothing is interpolated: a day without a recorded snapshot is simply not counted.

Frequently asked questions

Which vendor posted the most status-page incidents in the last 30 days?

Cloudflare, with 55 vendor-posted incidents between Sep 17, 2026 and Oct 17, 2026, according to Merlonix's monitoring of its published status page. Scheduled maintenance is counted separately.

Which monitored vendors posted no incidents in the last 30 days?

Stripe posted no incidents on their status pages between Sep 17, 2026 and Oct 17, 2026, based on Merlonix's recorded observations. Scheduled maintenance windows are not counted as incidents.

How does Merlonix count an incident?

Merlonix polls each vendor's published status page around the clock and records a snapshot whenever the content changes. An incident is counted once, keyed by the vendor's own incident id, when its start time falls inside the 30-day window. Scheduled maintenance and "operating normally" notices are excluded from the incident count and reported separately. Nothing is interpolated: a day without a recorded snapshot is simply not counted.

Is this page real-time?

No. This page is a dated snapshot generated Oct 17, 2026, 07:58 AM UTC and rebuilt on a schedule. The live board at https://merlonix.com/vendors/ refreshes every minute, and the machine-readable dataset at https://api.merlonix.com/v1/public/datasets/vendor-status-digest is recomputed hourly.

Reduce alert noise when a vendor you have declared as a dependency reports degradation or an outage. See vendor-aware alerting or check the free live vendor board.