Website monitoring, twelve types, one pipeline.

Website monitoring means continuously checking a website from the outside — the way a visitor experiences it — and alerting you when something goes wrong. That starts with availability (is the site up?) but extends to everything that can quietly fail: user flows like checkout, API endpoints, page speed, TLS certificates, DNS answers, mail reputation, domain renewals, the servers underneath and the scheduled jobs behind the scenes. Uptimia covers each of these as its own monitor type, in one account, on one alerting pipeline.

Almost everyone starts with uptime and SSL monitoring — they cover the two most visible failures. From there, add what would hurt most tonight: transaction monitoring if you sell online, API monitoring if other software depends on your endpoints, heartbeat monitoring if cron jobs or backups run on a schedule, server monitoring if you manage your own machines. You can add and remove types any time — they're all in the same plan.

Every paid plan includes every monitor type — none is reserved for a higher tier. What the plans change is volume, cadence and two capabilities: how many monitors of each type you can create, how many teammates you can invite, how fast the fastest check may run (30-second uptime checks start on Professional; Basic and the trial run from one minute), and whether you get escalation ladders and white-label branding — both of which begin on Professional. The 30-day trial unlocks every monitor type. The free plan is a slice: one uptime monitor, one API monitor and one status page.

For most types, nothing. Uptime, transaction, API, SSL, speed, DNS, domain and blacklist checks all run from our side — the checkpoint network, or a direct query to the authoritative nameservers and blacklists; malware monitoring asks Google's Web Risk API about your URL. Three types need something from you by design: server monitoring installs an agent with one bash line, real user monitoring adds a small script to your pages, and heartbeat monitoring runs the other way round — your job calls a ping URL when it finishes.

Yes — that's the point of one platform. Contacts, the 12 alert channels and maintenance windows are configured once and shared by every monitor type, on every plan: a failing cron job pages your team exactly the way a failing checkout does. Escalation ladders — with incident grouping and one-tap acknowledgement — are the one alerting piece tied to a plan; they come with Professional and above, and below that every alert goes to everyone at once.

From 171+ checkpoints in 70+ countries. You choose the locations per monitor — or save a reusable location profile — and outages are confirmed from multiple regions before an alert goes out, so a single flaky route never pages you.

Uptime monitoring checks that a URL responds correctly — fast, frequent, from many locations. Transaction monitoring drives a real Chrome browser through a multi-step flow — log in, add to cart, pay — and verifies each step works. A site can be perfectly "up" while its checkout is broken; you want uptime monitoring for the first signal and transaction monitoring for the flows that earn money.

Yes. Invite teammates and give each one a role — owner, admin, editor, viewer or billing — enforced on the server, not just in the interface. How many seats you get depends on your plan. Alerts, escalation ladders and acknowledgements are per person, so the right people are paged and you can see who answered.