HTTP, DNS, SSL, and content checks
Track websites, APIs, DNS records, SSL expiry, and response assertions from one console as each check type is configured.
FTStatus monitors websites, APIs, SSL certificates, domains, DNS, ports, and cron jobs from multiple locations, then gives your team a clear status page when customers need answers.
Demo monitoring workspace
Example monitors across web, portal, API, and hosting
212 ms
99.99%
184 ms
99.98%
246 ms
Collecting
Healthy
Collecting
Built for teams who keep customer services running.
Protect client sites, prove uptime, and send calm updates when providers or plugins fail.
Track control panels, DNS, SSL, ports, and customer-facing service health from one place.
Monitor apps, APIs, queues, and scheduled jobs while keeping incident history tidy.
Show customers you know what is happening before they need to open a support ticket.
Monitoring coverage
FTStatus focuses on the workflows that matter first: create checks, alert quickly, publish status, and explain incidents clearly.
Track websites, APIs, DNS records, SSL expiry, and response assertions from one console as each check type is configured.
Use 5-minute Starter checks or 1-minute Team checks, with confirmation retries to reduce noisy alerts.
Email is the default path. Webhook, Slack, and SMS routes can be enabled where the client environment is configured for them.
Publish branded pages with component status, subscriptions, incident updates, maintenance windows, and feeds where enabled.
Show uptime and response history when real data exists. New pages clearly show when history is still being collected.
Add setup help, monitor tuning, incident coordination, and reliability summaries without promising fix times outside the support agreement.
Product console
The dashboard gives teams a self-serve control room for monitors, alert policies, incidents, subscribers, reports, and public status pages.
Create uptime checks for websites, APIs, ports, DNS, SSL expiry, keywords, and heartbeat jobs.
Track detection, acknowledgement, status updates, affected services, and final resolution notes.
Let customers subscribe to service updates and receive incident or maintenance notifications.
Route alerts into email, webhooks, configured SMS or Slack channels, and managed Faciotech support.
Monitor dashboard
Example workspace · 18 monitors · 4 alert routes
99.98%
30 day uptime
214 ms
median latency
0
active incidents
| Monitor | Type | Regions | Cadence | Status |
|---|---|---|---|---|
| Main website | HTTPS | AMS, IAD, LHR | 1 min | 212 ms |
| Client portal | Keyword | AMS, IAD, LHR | 1 min | 184 ms |
| Application API | HTTP JSON | IAD, LHR | 1 min | 246 ms |
| Hosting Edge | TCP + SSL | AMS, LHR | 5 min | Healthy |
Monitoring center
FTStatus starts with the day-one surface clients expect while staying useful for Faciotech hosting and custom-development support workflows.
Add URL, method, expected status, timeout, keyword, regions, and frequency.
Choose escalation channels and only notify after confirmation retries.
Expose real uptime history when available, incident updates, maintenance windows, RSS, and JSON.
Alert paths
What FTStatus monitors
FTStatus focuses on practical monitoring that helps support teams catch outages, verify customer-impacting pages, and reduce uncertainty during incidents.
Monitor public pages, app routes, and HTTP endpoints for status code, timeout, and response changes.
Confirm that important text remains present on a page, or alert when unexpected wording appears.
Check whether a server or network service is reachable before customers report an outage.
Check critical TCP services such as SMTP, control panels, APIs, and custom application daemons.
Use heartbeat checks to know when backups, sync jobs, or scheduled business tasks stop reporting.
Detect unexpected DNS record changes early and verify public answers from more than one location.
Track certificate expiry, domain renewal windows, and configuration drift before customers see warnings.
Watch health endpoints and JSON APIs with clear pass/fail checks for production services.
Track latency trends and alert when services become slow before they fail outright.
Incident workflow
FTStatus helps the team move from detection to explanation: retry the check, alert the owner, publish updates, and leave a clean record for customers.
Two regions confirm the issue before anyone gets paged.
Email, webhook, configured SMS or Slack policies notify the right owner.
Affected components and customer-facing incident notes go live.
The incident closes with uptime impact and a timeline for review.
Status pages
Publish a branded page with components, uptime history, maintenance notices, subscriber updates, and incident timelines. Internal notes stay private while public updates stay simple.
Example public status
Customer-facing uptime page
Scheduled maintenance
Infrastructure upgrade window: Jun 23, 2026, 01:00 UTC.
Simple pricing
For small teams validating a few critical endpoints.
GHS 0/mo
For production services that need fast alerts and reporting.
GHS 149/mo
For Faciotech clients who want monitoring run by our team.
Custom
| Feature | Starter | Team | Managed |
|---|---|---|---|
| Monitors | 10 | 50 | Scoped by quote |
| Check cadence | 5 minutes | 1 minute | 1 minute or agreed cadence |
| Public pages | 1 | 5 | Client-specific |
| Alerts | Email plus configured routes | Routed through Faciotech support | |
| Response help | Self-serve | Support-assisted | Faciotech incident coordination |
Questions
FTStatus is Faciotech's uptime monitoring and status-page product for websites, portals, APIs, DNS, SSL, and critical hosted services.
Checks use confirmation retries and multi-location evidence where configured, so a single route issue does not automatically become a public outage.
Yes. FTStatus supports branded public status pages, component groups, maintenance notices, subscriber updates, and incident timelines.
Yes. Managed plans let Faciotech configure monitors, tune alerts, maintain status pages, and coordinate incident updates with your team.
Use the dashboard for internal response, then publish a clean status page so customers see what is happening without opening a ticket.