FTStatus
Menu
Home
Product

Monitoring coverage

Website uptimeAPI healthDNS and domain healthSSL certificatesResponse timeHeartbeat jobsTCP service checks

Status workflow

Customer status pagesIncident updatesPlanned maintenanceSubscriber notificationsService components
Solutions

Managed reliability

Managed monitoringHosting teamsAgenciesSupport teamsBusiness ownersEnterprise

Teams

GovernmentGovernment custom serverSovereign monitoringPublic service status pagesDevOpsDevelopersSupport teamsBusiness ownersAgenciesEnterprise
Resources

Learn

Knowledge hubBlogGetting startedMonitoring locationsDeveloper APIReliability guidesMonitoring playbooksIncident templatesCase studiesRoadmap

Compare

Monitoring alternativesSelf-serve vs managedStatus-page platforms
Tools

Diagnostic tools

Page change previewUptime/SLA calculatorDNS health checkMail record checkCron schedule helper

Alert routes

EmailSMSSlackDiscordMicrosoft TeamsTelegram
PricingDocsLog in

Reference Overview

This section is the source of truth for FTStatus configuration. Use it to look up exact field names, types, defaults, and behaviour — not to learn how to do something. For task-oriented walkthroughs, see the how-to guides; for learning paths, see the tutorials.

Monitors

How each monitor type runs checks and what you can configure on it.

  • HTTP monitor — URL, method, headers, body, assertions, regions.
  • TCP monitor — host:port checks for non-HTTP services.
  • DNS monitor — record-type assertions for A, AAAA, CNAME, MX, NS, TXT.

Status pages

Public surfaces for communicating service health.

  • Status page — page settings, custom domains, IP restrictions, themes, locales.
  • Page components — monitor-linked and static components, component groups, ordering.
  • Status report — incident updates and the state machine they drive.
  • Maintenance — scheduled maintenance windows.
  • Subscriber — email subscribers to a status page.

Alerting

  • Notification channels — Slack, Discord, Email, and generic webhooks.
  • Incident — auto-generated incident objects, trigger thresholds, and lifecycle states.

Probing infrastructure

  • Location — every public region, its provider, and the IPv4/IPv6 addresses to allowlist.
  • Private location — fields for a customer-deployed probe and the API surface that manages it.

Tooling

  • CLI — every command, subcommand, and flag in the openstatus CLI.
  • Terraform provider — resource and data source schemas for openstatusHQ/openstatus.
  • MCP server — tools and transport for the openstatus Model Context Protocol server.

HTTP API

A public HTTP API is planned but not yet available. Today, programmatic access is:

  • MCP server — the live, read-only Model Context Protocol endpoint at https://app.ftstatus.com/api/mcp, authenticated with a workspace read-only API key.
  • Talk to support — for integrations beyond the MCP endpoint, contact Faciotech support and we will scope it with you.