Know before the ticket comes in.
Pingtier checks every client’s websites, portals and mail hosts from 8 probes in Europe, the US and Asia, confirms an outage with 2 probes on 2 providers, and drafts the message you send the client.
Today, as you see it
One screen. Every client. Nothing to configure.
Down, blocked and expiring certificates at the top, grouped by what needs you. Open one and the evidence is already there.
shop.example.com
DownThe server answers 503 to every probe since 17:02. DNS and TLS are fine.Check the app behind the shop, or its last deploy. The client message is drafted below.
503Service Unavailable212 ms503Service Unavailable318 ms503Service Unavailable402 ms503Service Unavailable201 msWhy Pingtier
Built for the person who answers the phone.
Your clients do not care which server failed. They care who noticed first and what you told them. Pingtier gives you both.
Confirmed, not guessed
One probe never declares an outage. A Down needs 2 probes on 2 different providers within one round, so a flaky route does not page you at 3 a.m.
17:02:33 503 New York · provider B
17:02:33 Down confirmed · alerts sent
Blocked is not Down
When Cloudflare or a WAF answers the probes with a bot challenge, you get one email with the addresses and the User-Agent to allow. No false outage, no uptime penalty.
Allow Pingtier-Probe/1 and 8 addresses
Uptime: this time is unknown, not down
The client message, written
Every incident comes with an English draft for that client: what broke, since when, what you are doing. Copy it, open it in email, mark the client as told.
Since 17:02 CET your online shop at shop.example.com does not load for visitors. We are on it…
Told at 17:05 by Anna M.
How it works
From a domain to a told client in five steps.
Nothing to install. The first result from every probe arrives within a minute of adding a hostname.
What you get
Small on purpose, exact where it matters.
HTTP and TLS checks with the evidence to act on. No dashboards to build.
Pricing
One price. Per client, not per check.
Free during beta. Then EUR 4 per client a month, excl. VAT. Move the slider to see your number.
Per client
For agencies and MSPs with a client list. Pay for clients, not for checks.
- As many clients as you need, 10 hostnames each
- Checks every 30 s, 60 s, 3 or 5 minutes
- Unlimited team with roles, 1 year of history
- Nothing charged before the beta ends and you confirm with a card
Every beta account starts on Free. You choose Per client after the beta.
Free
For a first look, or your own few sites.
- 3 clients, 5 hostnames each
- Checks every 3 or 5 minutes from all regions
- Email and Slack alerts
- Client messages, 30 days of history
- –One member
Clients are counted on the invoice date, paused included. VAT is added by your country’s rules. Nothing is charged during the beta; 30 days before it ends you get an email and decide.
Questions
Straight answers.
Where do the checks come from?
8 probes in Europe, the US and Asia on 4 hosting providers. The list of addresses and the User-Agent will be public on a Probes page before sign-up opens, so you can allow them in Cloudflare or a WAF.
What counts as Down?
Two probes on two different providers failing within one round. A single failed probe starts a second round instead of an alert. A bot challenge is Blocked, a separate state that never counts as Down.
Do you contact my clients?
No. Pingtier drafts the message in English with the evidence; you copy it or open it in your email client and send it yourself. “Mark as told” records who told the client and when.
Where is my data?
Raw check results are kept 7 days, rollups for your plan’s history. Where the service stores your data goes into the product privacy policy, published before sign-up opens.
What is not in the beta?
Public status pages, SMS and phone alerts, a public API and PDF reports. The beta covers HTTP and TLS checks, Slack and email alerts, and client messages.
Every client, one Today.
When sign-up opens, sign in with an email link, Google or GitHub. Add a client, send a test alert, done.