HTTP(S) monitoring
Continuously check website and API status and response time.
GET / POST · expected status codes · latency threshold
Website monitoring
Know your website is down before your users do
Monitor websites, APIs, ports, DNS and SSL certificates from distributed probes in China and overseas. Consecutive failure and recovery thresholds filter transient noise before an incident enters your alert workflow.
- 5monitor protocols
- 1 minfastest interval
- 10alert channels
Monitoring center
See uptime, response time and incident scope at once
Monitor details combine probe results, carrier and regional impact, check history and incident records.
Chahu Monitor
Operational
Website availability
Operationalhttps://www.example.com
- 24-hour uptime
- 99.98%
- Average response
- 128 ms
- Open incidents
- 0
- Recent checks
- 212 / 212
24-hour uptime
00:00 - 24:00
99.98%
Incident status
No unresolved incidents
An incident is created and notifications are sent only after the failure threshold is reached.
China Telecom
116 msChina Unicom
132 msRecent checksOperationalAverage responseRecent checks
China TelecomHealthy116 msNow
China UnicomHealthy132 msNow
Overseas probesHealthy184 msNow
Monitoring capabilities
HTTP, Ping, TCP, DNS and SSL website monitoring
Protocol-specific configuration keeps website, network, port, DNS and certificate failures distinct.
Ping monitoring
Track host reachability and latency from distributed probes.
Multi-probe checks · carrier and regional impact
TCP monitoring
Verify that a TCP connection can be established on a selected port.
Ports 1-65535 · connection failure detection
DNS monitoring
Continuously verify critical public DNS records.
A / AAAA / CNAME / MX / NS / TXT / SRV / PTR
SSL certificate monitoring
Track certificate health and reduce expiration risk.
Certificate status · independent schedule
Create your first monitor
Choose a protocol and target. Configure frequency, probe scope, incident thresholds and alerts on the next screen.
Incident workflow
Verify across probes, reduce noise and locate impact
Scheduled monitoring runs independently and separates transient network noise, regional anomalies and real incidents.
- 01
Distributed checks
Run across all probes, China, overseas or selected regions.
- 02
Incident decision
Evaluate consecutive failures, response status and latency thresholds.
- 03
Event delivery
An independent alert process sends failure and recovery events.
- 04
Review and share
Review checks, SLA, impact and incidents, then share status when needed.
Bring incident alerts into your daily workflow
Each monitor keeps the configuration, evidence and collaboration surfaces your team needs from detection through recovery.
Probe health breakdown
Compare success rate, average latency and P95 by carrier, region and province.
SLA and check history
Review 24-hour uptime, recent-state strips and individual check results.
Failure and recovery records
Track impact, cause, start time, acknowledgement and recovery state.
Public status sharing
Create a controlled public status link and decide whether the target is visible.
Available alert channels
- Telegram
- Phone
- SMS
- WeCom
- DingTalk
- Feishu
- Slack
- Discord
- Webhook
Alert timeline
Incident decision
Evaluate consecutive failures, response status and latency thresholds.
Event delivery
An independent alert process sends failure and recovery events.
Review and share
Review checks, SLA, impact and incidents, then share status when needed.
Website monitoring FAQ
Key details about protocols, intervals, probes, alerts and reporting.
What can Chahu monitor?
Chahu currently supports HTTP(S), Ping, TCP, DNS and SSL certificate monitoring. HTTP(S) covers websites and public APIs, TCP checks a selected port, and DNS supports A, AAAA, CNAME, MX, NS, TXT, SRV and PTR records.
How often can a monitor run?
Available intervals are 1, 2, 5, 10 and 30 minutes, or 1 hour. The free plan starts at 5 minutes; other plans can run as often as once per minute.
How are transient network issues handled?
Each monitor has consecutive failure, consecutive recovery and latency thresholds. Incidents and recoveries are created only after those thresholds are met, with probe, carrier and regional results used to show impact.
Where can checks run from?
Except for SSL certificate monitors, tasks can use all probes, China probes, overseas probes or selected regions, with carrier filters for China Telecom, China Unicom, China Mobile and overseas networks.
Which alert channels are available?
Email, Telegram, phone, SMS, WeCom, DingTalk, Feishu, Slack, Discord and custom webhooks are supported. A dedicated alert process delivers failure and recovery events.
How is monitoring different from a manual speed test?
A manual test is launched on demand for one-time diagnosis. Monitoring runs independently on a fixed schedule and produces SLA, check history, incident records and alert events.
Turn occasional checks into continuous visibility
Create your first monitor and bring uptime, response time and incident scope into one operational view.