Availability

Service & Uptime Monitoring

Continuously monitors whether your critical services are up.

7/24: continuous monitoring
Periodic: check intervals
Multi: protocol support
Instant: outage alerts

Why it matters

Every closed port is a business outage.

Your servers may run 7/24, but the services inside them are constantly changing state. A library conflict, memory issue, misconfiguration or bad restart script can shut down a critical service. Your customers see the site is down — but you do not know until they complain. Monitoring stands guard in your place and alerts you before customer complaints arrive.

How many minutes late do I learn when a service goes down? If customers find out first, you have an SLA breach.
Are my critical ports (HTTP, SMTP, API, DB) always open? One staying closed is an hour of lost productivity.
Can I measure outages? Can I prove how fast I fixed the problem?

What it does

What it does.

Port and service monitoring

Monitor critical ports like web server (TCP 80, 443), email (SMTP 25, 587), API (HTTPS 443), database (TCP 5432, 3306).

Periodic check intervals

Define how often to check: most frequent (10 seconds), least frequent (hours). Short intervals for critical services, longer for low-priority ports.

Multi-protocol support

HTTP/HTTPS web checks, SMTP email service, TCP raw socket connection, DNS resolution checks — different test per protocol.

Target definition

Simply define the IP or domain, port number, protocol and check interval for each monitored system.

Instant outage alert

When an outage is detected you get an email alert. On the panel it is marked with a red warning by status color.

Uptime percentage and trend

Uptime percentage is calculated per target; outage history and recovery time are retained for SLA tracking.

Response time monitoring

Response time (latency) is logged after each check, not just connectivity. Performance trend becomes visible.

How it works

From setup to report.

01
Add target system

Define the server IP or domain name, port number and protocol (HTTP, HTTPS, SMTP, TCP, DNS) to monitor.
02
Set check interval

Choose how many seconds between checks; assign short intervals for critical services (10-60 seconds), longer for others.
03
Define alert

Enter the email address to receive notification if an outage is detected.
04
Start monitoring

Once settings are saved, ThreatChaser automatically checks targets at the intervals you specified.
05
Report and fix

Monitor outages and response time trends on the panel; respond quickly to prevent SLA breaches.

Technical details

The specifics.

Protocol support: HTTP, HTTPS, SMTP, TCP, DNS
Target definition: IP address, FQDN, port (1-65535), protocol
Check interval: Customizable in seconds (10 seconds and above)
Measured metrics: Connection status (open/closed), response time (latency in ms), uptime percentage
Alert: Email notification on outage detection
Monitoring history: Every check is logged with timestamp, status and response time; uptime calculation and trend
SLA tracking: Monthly uptime percentage, outage count, average recovery time

FAQ

Frequently asked questions.

If I set the check interval very short (10 seconds), is there a false alarm risk?

A single failed response at very short intervals might not trigger an alarm. ThreatChaser sends alerts after consecutive failures, so temporary network hiccups do not cause false alerts. Interval should match criticality level.

What if a service is open but responds very slowly?

Response time is logged. If you set a threshold (e.g., fail if over 5 seconds), slow responses can also trigger alerts. Response time trend is visible on the panel so you can catch performance issues early.

Can I monitor from multiple regions?

Monitoring is centralized from the ThreatChaser panel; all checks start from the same source. If you need checks from different geographies, special architecture is required.

Related services