MERLONIX

First-party monitoring data

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

Between Aug 7, 2026 and Sep 6, 2026, Merlonix's independent monitoring recorded 124 vendor-posted incidents (17 major, 82 minor, 25 unlabelled) and 232 scheduled maintenance windows across the 6 of 11 monitored vendors with enough history. Cloudflare posted the most incidents (52). Stripe posted none.

Source: Merlonix monitoring data, Aug 7, 2026 to Sep 6, 2026, generated Sep 6, 2026, 01:32 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-09-06). 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
Amazon Web Services250 / 0 / 250Sep 3, 202633
Anthropic157 / 8 / 00Sep 3, 202643
Cloudflare522 / 50 / 0122Sep 4, 2026374
GitHub197 / 12 / 00Sep 4, 202658
OpenAI131 / 12 / 00Sep 4, 202650
Stripe00 / 0 / 0110—229
Google Cloudlimited history (17 of 30 days)22 / 0 / 00Sep 1, 202611
Microsoft Azurelimited history (23 of 30 days)20 / 0 / 20Aug 25, 20264
Shopifylimited history (18 of 30 days)21 / 1 / 00Sep 2, 20267
Slacklimited history (24 of 30 days)11 / 0 / 00Aug 13, 202610
Vercellimited history (20 of 30 days)63 / 3 / 00Sep 4, 202616

Totals across the 6 vendors with enough history: 124 incidents (17 major, 82 minor, 25 unlabelled) and 232 maintenance windows.

Most recent incidents, as posted by each vendor

Amazon Web Services25 in window
Anthropic15 in window
Cloudflare52 in window
GitHub19 in window
Google Cloud2 in window
Microsoft Azure2 in window
OpenAI13 in window
Shopify2 in window
Slack1 in window
Vercel6 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-09-06.
  • 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 52 vendor-posted incidents between Aug 7, 2026 and Sep 6, 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 Aug 7, 2026 and Sep 6, 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 Sep 6, 2026, 01:32 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.