MERLONIX

First-party monitoring data

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

Between Sep 7, 2026 and Oct 7, 2026, Merlonix's independent monitoring recorded 96 vendor-posted incidents (12 major, 84 minor, 0 unlabelled) and 379 scheduled maintenance windows across the 4 of 11 monitored vendors with enough history. Cloudflare posted the most incidents (50).

Source: Merlonix monitoring data, Sep 7, 2026 to Oct 7, 2026, generated Oct 7, 2026, 08:31 AM UTC. Machine-readable dataset (JSON, recomputed hourly): api.merlonix.com/v1/public/datasets/vendor-status-digest. Cite as: Merlonix, “Vendor status digest — last 30 days” (2026-10-07). https://merlonix.com/vendors/digest/ — dataset: https://api.merlonix.com/v1/public/datasets/vendor-status-digest

Not affiliated with any vendor listed here. Every count is Merlonix's own observation of each vendor's published status page; the vendors' official pages remain the authoritative record.

Incidents and maintenance by vendor

Incidents are distinct vendor-posted entries whose start time falls in the window, excluding scheduled maintenance and "operating normally" notices. Vendors marked limited history are listed but excluded from the cross-vendor totals.

VendorIncidentsMajor / minor / unlabelledMaintenance windowsLatest incidentObservations
Cloudflare501 / 49 / 0248Oct 7, 2026405
GitHub146 / 8 / 00Oct 6, 202651
OpenAI315 / 26 / 00Oct 7, 202697
Stripe10 / 1 / 0131Sep 16, 2026262
Amazon Web Serviceslimited history (22 of 30 days)102 / 0 / 80Oct 4, 20269
Anthropiclimited history (27 of 30 days)75 / 2 / 00Oct 7, 202621
Google Cloudlimited history (27 of 30 days)00 / 0 / 00—2
Microsoft Azurelimited history (8 of 30 days)50 / 0 / 50Sep 30, 202610
Shopifylimited history (22 of 30 days)31 / 2 / 00Sep 18, 202611
Slacklimited history (29 of 30 days)33 / 0 / 00Oct 1, 202615
Vercellimited history (27 of 30 days)42 / 2 / 00Sep 28, 20268

Totals across the 4 vendors with enough history: 96 incidents (12 major, 84 minor, 0 unlabelled) and 379 maintenance windows.

Most recent incidents, as posted by each vendor

Amazon Web Services10 in window
Anthropic7 in window
Cloudflare50 in window
GitHub14 in window
Microsoft Azure5 in window
OpenAI31 in window
Shopify3 in window
Slack3 in window
Stripe1 in window
Vercel4 in window

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-07.
  • 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 50 vendor-posted incidents between Sep 7, 2026 and Oct 7, 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?
Every vendor with enough history posted at least one incident between Sep 7, 2026 and Oct 7, 2026, based on Merlonix's recorded observations.
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 7, 2026, 08:31 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.

Want to be paged when one of these vendors posts an incident that affects your stack? See vendor-aware alerting or try the free vendor watch tool.