Feature · Features

TCP service checks for critical services

Verify that an important TCP service accepts connections from outside your environment.

status.ftstatus.com
Live status board99.98% uptime
Marketing siteftstatus.com182ms
API gatewayapi.ftstatus.com96ms
Checkout servicedegraded · recovering+413ms
Auth & sessionsauth.ftstatus.com54ms
Background jobsworker poolOK
HTTP · DNS · TCP
live checks
1 min
Team cadence
Real
uptime history
Public
status page
  • Check public TCP reachability and connection timeout.

  • Use private/internal labels for sensitive service details.

  • Attach only customer-facing impact to public status pages.

Monitor

What it checks

FTStatus turns the target into a monitored service with clear success rules, timeout behavior, and optional customer-facing status-page impact.

Response time · 24h

182 ms
AMSIADLHR

Alerting

How alerts work

A single noisy check should not become a public incident. FTStatus is designed around retries, multi-location evidence, and controlled escalation.

Status pages

What customers see

Public pages show service impact and plain-language updates. Internal endpoints, provider details, and infrastructure notes stay private.

Looks right either way

Light or dark, your status page stays on-brand.

Match what your customers expect with a clean light or dark public page — same components, same clarity.

AAcme CloudAll systems operational
WebsiteOperational
APIOperational
PaymentsOperational
Email deliveryOperational

Last 90 days · 99.98% uptime

Safe for public status pages

  • Website and application availability
  • API health endpoint status
  • DNS and SSL issues affecting customer access
  • Maintenance windows and incident timelines
  • High-level region coverage

Internal operations only

  • SSH, admin panels, databases, queues, and backups
  • Server names, origin IPs, provider IDs, and ports
  • Firewall rules, file paths, and secret-related config
  • Primary or backup probe node details
  • Customer-specific private control panels

Setup workflow

From first check to customer-ready status.

1

Choose the service or endpoint to watch.

2

Set the check cadence, timeout, locations, and pass/fail rule.

3

Attach the monitor to alert routes and a public status component.

Set up monitoring your customers can trust.

Start free with the checks that matter — sites, APIs, DNS, and hosted services — then add status pages and alert routing as you grow. No credit card, and local Faciotech support when you need it.

Start free