May’d It

WORKFLOW / Service operations

Build a vendor incident review timeline

Collect official status-feed observations from Apify, Reddit and Cloudflare while keeping scheduled maintenance separate from incident history.

Start with the sample ↓Actor details
9 saved observationsObserved October 18, 2026 UTCManual execution

REAL RECORDS / DATED EVIDENCE

What do our vendors’ public status feeds actually report?

Saved at 2026-10-18T13:05:23.904Z from build 1.0.5. This preview makes no live requests.

Selected fields from the saved bounded sample
Vendor NameTitleLatest Update LabelSource Published At
ApifyElevated errors in Actor runsResolved2026-09-22T16:30:00+02:00
ApifyDegraded Actor performanceResolved2026-08-20T18:14:23+02:00
ApifyDegraded performance of SHADER proxy groupResolved2026-08-14T16:05:05+02:00
RedditInvestigating elevated errors across reddit.com and native appsResolved2026-10-07T13:55:28-07:00
RedditMods Unable to Approve ContentResolved2026-09-22T18:27:11-07:00
RedditElevated site errorsResolved2026-09-01T14:24:05-07:00
CloudflareKTM (Kathmandu) on 2026-11-02Scheduled2026-11-02T21:00:00Z
CloudflareAMD (Ahmedabad) on 2026-11-02Scheduled2026-11-02T21:00:00Z
CloudflareDAC (Dhaka) on 2026-11-02Scheduled2026-11-02T20:00:00Z
Sample CSV ↓Sample JSON ↓Exact input ↓Method & coverage

FROM DATA TO A REVIEW QUEUE

Five practical steps

  1. Choose the vendors used by your services. The example takes three publisher-ordered entries per feed.
  2. Separate Scheduled entries from Resolved or other incident updates. In our sample, Cloudflare’s three entries describe future maintenance.
  3. Preserve sourcePublishedAt, sourceUpdatedAt and observedAt separately; they answer different timing questions.
  4. Upsert by vendorName and incidentId. Add your affected internal service and investigation notes only after checking your own monitoring.
  5. For sequential repeat monitoring, set comparePrevious and your own snapshotName. Retain previous rows when a feed entry falls outside the bounded window.

Destination key: vendorName + incidentId. Keep an audit trail and preserve prior rows when a later sample is empty.

TWO WAYS TO START

Run in Apify or download the starter

Use Apify Console

  1. Open the Actor, switch to JSON input and paste the example below.
  2. Review current pricing, use your own account, and set a $0.05 maximum run charge.
  3. Run manually. Review SUMMARY and results before exporting CSV into your review sheet.
Open Actor on Apify ↗

Exact sample input

{
  "vendors": [
    "apify",
    "reddit",
    "cloudflare"
  ],
  "maxItemsPerSource": 3,
  "maxResults": 9,
  "maxRunSeconds": 120
}

Download a repeatable runner

Save these three files in one folder. The Node.js 22+ starter needs no npm packages. Add your own Apify token through your environment; the downloads contain no credentials.

Runner ↓Configuration ↓Setup guide ↓
node run-workflow.mjs --run

Execution is explicit and can incur charges. The starter saves local CSV/JSON, checks run status and coverage, and supports resuming an existing run. Connect your own spreadsheet after reviewing the output. It does not enable a schedule or send notifications.

A SMALL, EXPLAINED START

What this sample would cost at listed event rates

$0.01805

9 results × $0.002 per result, plus $0.00005 Actor Start at the FREE-tier rates observed October 18, 2026. This is a modeled event charge, not a bill or a complete account-cost estimate. Platform/API/storage usage and plan rates may differ.

The runner requests a $0.05 maximum charge. A cap can stop collection early. Check current pricing ↗.

Keep the source’s meaning

  • Feed order is publisher-defined and can include future-dated maintenance.
  • The public feed is not a live uptime probe or a complete incident archive.
  • A vendor update does not prove your service was affected or has recovered.

Read the full Actor guide for fields and scope.