Vendor Status Watch

Watch Cloudflare, Datadog, GitHub, and Stripe's own published status feeds. When a disruption intersects something your Architecture Map says you depend on, Landfall tells you — naming the affected dependency, never just the vendor's name — and links straight to the vendor's own advisory.

What it is, and what it is not

A background watch, not a webhook: Landfall polls each vendor's own public status page every 5 minutes. There is nothing to configure on the vendor's side — no webhook, no API key, because the feeds are public. What you configure is which providers to watch and how aggressively to respond.

A published disruption is raised to you only where it intersects your Architecture Map. An org with no map content receives no alerts from this feature, under any advisory volume — this is a precision tool, not a firehose of every vendor's every incident.

What you'll need

• An Architecture Map with at least one external dependency mapped (Cloudflare CDN, your Datadog agent, and so on).
• An admin on your Landfall organization, to choose which providers to watch and configure the response.
• A plan that includes the Vendor Status Watch entitlement — visible and explained even if yours does not.

Configuring a watch

1. Settings → Integrations → Vendor Status Watch

   For each provider, choose Notify only (the default) or Open incident automatically above a severity threshold. Nothing opens automatically until you explicitly choose that response — the safe behavior is the default.

   Settings → Integrations → Vendor Status Watch

   

2. Notify-only: one action to declare

   A match under Notify only appears in your organization's "notified" inbox with the affected dependency, its confidence (confirmed or inferred), the vendor's own advisory link, and a single Declare incident button. Nothing opens until a person clicks it.

What Beacon sees once a watch is configured

Once your organization has at least one watch configured, the current status of every watched provider is reachable by Beacon through the same dynamic signal catalog every other source uses — no vendor-specific agent tooling. An agent can ask "is Cloudflare currently reporting an incident?" during any investigation, not only one this feature opened.

Opening an incident automatically

Choosing Open incident automatically above (rather than Notify only) is the whole configuration — see Triggering Integrations → Vendor Status Watch for how that trigger actually reaches the incident pipeline.

Reference