Any server, any port
Check that a host answers on the port that matters: SIP 5060, HTTPS 443, mail 25, SSH 22 or any other.
Know when a server
or website goes down
CommsAlert checks your servers and websites on a schedule, confirms a problem before alerting, and tells you by email, SMS or webhook when something stops responding.
ANY HOST + PORTHTTP / HTTPSRESPONSE CODERESPONSE TIMEUPTIME HISTORYRE-CHECKED BEFORE ALERTING
Free for 3 monthsNo credit card needed
What we watch
Everything that matters, checked around the clock
Add a server by its address and port, or a website by its URL and the response code you expect. CommsAlert checks each one on your schedule and records the response time.
Website checks
Load a page over HTTP or HTTPS and confirm it returns the response code you expect.
Response times
Every check records how long the server or page took, with averages and history.
No false alarms
A failed check is tried again twice before anyone is alerted, so a single blip stays quiet.
Alerts and reporting
What happens when something goes down
Who gets told, what your customers see, and the tools for running dozens of monitors.
Alerts your way
Email, SMS and webhooks (Slack and more) when something goes down, and again when it is back.
Still-down reminders
Optional reminders while an outage lasts, spaced further apart over time, so a long outage isn’t forgotten.
Incidents and status pages
Outages open incidents automatically, and any monitor can appear on a branded public status page.
Public monitor pages
Share a simple uptime page for any server or website with your customers.
Bulk add from CSV
Add many servers or websites at once from a CSV file.
Monthly report
A monthly email with uptime per system and every alert sent.
Every monitor in one list
Status, response time and quick links for every server and website, with search.
Phone systems too
Check SIP servers alongside your websites, and monitor 3CX and Yeastar from the same account.
Inside the portal
What your team sees
Real screens from CommsAlert server and website monitoring. Click any of them to see it full size.
Names, hosts, URLs and email addresses shown are examples; every figure and screen is real.
Alarms
You decide what counts as a problem
Each monitor has its own settings. Together they decide what counts as down, how sure we are before saying so, and who hears about it.
| Port (servers) | The port that must answer: SIP 5060, HTTPS 443, mail 25, SSH 22 or any other. |
|---|---|
| Expected response code (websites) | The HTTP status the page must return, for example 200. Anything else counts as down. |
| Check interval | Every 10, 20, 30, 45 or 60 minutes, set per monitor. |
| Re-check before alerting | A monitor that was up and fails is checked twice more, three seconds apart, before a down alert is sent. |
| Down and back-up alerts | One alert when it goes down, and another when it is back. |
| Still-down reminders | Optional reminders while an outage lasts, spaced further apart over time. |
| Alert email | Send a monitor’s alerts to its own email address, or leave it empty to use your account’s. |
Alerts go by email, SMS and webhooks (Slack included), and every outage opens an incident automatically.
Setup
Nothing to install
Adding a monitor takes under a minute, and nothing is installed on your servers.
- 1
Add a server or website
A server by its address and port, or a website by its URL and the response code you expect.
- 2
Choose the interval and alerts
Pick how often to check it, from every 10 minutes to once an hour, and where its alerts should go.
- 3
Get alerted, and share it
Hear when it goes down and when it is back, and share its status with your customers.
Monitoring a 3CX? Adding it to 3CX monitoring creates its server, webpage and SSL monitors for you automatically.
Questions
Frequently asked
What is the difference between a server and a website monitor?
A server monitor checks that a host answers on a port (for example SIP on 5060). A website monitor loads a page and checks the response code (for example 200).
How often are checks run?
You choose for each monitor: every 10, 20, 30, 45 or 60 minutes.
Will I get alerts for short blips?
A failed check is tried again twice, a few seconds apart, before an alert is sent. Only a problem that is still there gets reported.
How am I alerted?
By email, SMS and webhooks (for example Slack). You get one alert when it goes down and another when it is back, plus optional reminders during a long outage.
Can my customers see the status?
Yes. Every monitor has a public page, and monitors can appear on a branded status page with incidents.
Can I add lots of monitors at once?
Yes, with bulk add from a CSV file.
Try it free for 3 months
The trial covers 15 servers, 15 webpages, 15 SSL certificates and 10 phone systems — the full feature set, at no cost. No credit card needed.