Skip to main content
Operator
Scan free
Status

Operator service status and dependencies.

This is a static but truthful status page for the services Operator depends on. It is not a real-time monitoring dashboard and does not aggregate uptime yet. Operator.fyi is generally healthy when the providers below are healthy, the app deploy smoke test passes, and scheduled substrate jobs continue to refresh the public business and market pages.

External dependencies

Web hosting, edge routing, serverless functions, and preview deployments.

Operator.fyi is healthy when this dependency is healthy. We do not currently aggregate uptime in real time.

Substrate Postgres, auth, and data access patterns used by app workflows.

Operator.fyi is healthy when this dependency is healthy. We do not currently aggregate uptime in real time.

Billing, checkout, subscription state, and payment webhooks.

Operator.fyi is healthy when this dependency is healthy. We do not currently aggregate uptime in real time.

SMS delivery and callback infrastructure for communication workflows.

Operator.fyi is healthy when this dependency is healthy. We do not currently aggregate uptime in real time.

Transactional email delivery for account, billing, and product notifications.

Operator.fyi is healthy when this dependency is healthy. We do not currently aggregate uptime in real time.

Key cron heartbeats

Operator also relies on scheduled jobs that keep the public substrate current. The user-facing signal is freshness: pages should load, sitemap files should emit, and business or market data should avoid empty fallback content. These jobs are checked during deploy and operational review rather than exposed as live gauges here.

Sitemap generation

Keeps core, content, trades, and business sitemap feeds current for crawlers.

Market refresh

Updates city and category data used by public market pages and agent reads.

Business snapshot checks

Rejects underpopulated or malformed snapshots before they reach public pages.

Deploy smoke test

Confirms the production app responds after automatic deploys from main.

Need to report a problem?

If a public page is stale, an API response is malformed, billing looks wrong, or an agent action did something unexpected, contact Operator with the URL, timestamp, browser or client, and any request id you received. For API users, include whether the issue appeared through REST, MCP, or a webhook callback.

Contact Operator