Operations

Public Status

Live component states, vendor passthrough, incident communication path, and service-area scope.

Effective
May 28, 2026
Last reviewed
May 28, 2026
Status feed
Live (first-party + vendor)
SLA
Not promised here
Support
support@macrobymark.com

Operational policy text for Macro by Mark. Not a substitute for advice from counsel.

Live

Live components

Status unavailable

Generated Sat, 11 Jul 2026 04:27:33 GMT

First-party probes

  • Website edge

    Operational
  • macrobymark.com/api/health?strict=1

    Operational
  • macrobymark.com/api/health/auth?strict=1

    Operational
  • macrobymark.com/api/indicators/summary/health?strict=1

    Operational
  • macrobymark.com/api/providers/health

    Operational
  • macrobymark.com/api/chat/health?strict=1

    Operational

Vendor passthrough

  • Vercel (hosting)

    All Systems Operational

    Operational
  • Stripe (billing)

    All Systems Operational

    Operational
  • Supabase (auth + database)

    All Systems Operational

    Operational
  • Anthropic (Marco backend)

    All Systems Operational

    Operational
  • Trigger.dev (background jobs)

    Status unavailable
  • Resend (email delivery)

    All Systems Operational

    Operational

Active incidents

  • Project status change failures in multiple regions

    supabase · monitoring · major

    Started Tue, 30 Jun 2026 02:38:13 GMT

Live data is pulled from the configured monitoring source (first-party) vendor status feeds (vercel, stripe, supabase, anthropic, trigger, resend). Cached at the edge for 60 seconds.

Posture

Hybrid status surface

The components above are pulled from the connected monitoring source and vendor status feeds. When no live source is configured, only the manual sections below apply.

Live data is server-cached for 60 seconds. Vendor passthrough reflects what the vendor itself reports; Macro by Mark cannot override a vendor's status.

Components

Service areas tracked for incidents

Customer-impacting incidents are tracked across the following service areas when relevant:

  • Website and public pages.
  • Account sign-in, sessions, MFA, and passkeys.
  • Billing and customer portal access through Stripe.
  • Dashboards, watchlists, alerts, and saved workspace records.
  • Macro indicators, provider-backed data pages, and import surfaces.
  • Macro Lab, models, forecasts, and notebook execution surfaces.
  • Marco assistant routing and saved conversation history.
  • Email delivery for account, billing, security, support, and alerts.

Incidents

Communication path

For confirmed customer-impacting incidents, Macro by Mark may update this page, email affected users, post in-product notices, or respond through support depending on severity and scope. The incident-response runbook controls internal handling.

Support questions can be sent to support@macrobymark.com. Vulnerability reports should go to security@macrobymark.com.

Current note

Source-of-truth note

The live components board is the source of truth for current state. The manual sections above, components and communications, describe scope and process; they don't override what the live board reports. If the live board is empty, no monitoring sources are currently configured and the manual posture applies.

Primary references

Sources that informed the current posture. Included for transparency; this doesn't turn the page into legal advice.

Related policies

The other pages that round out the trust posture for Macro by Mark.