The vocabulary below comes from the Uptimia control panel and the rest of this help center. Each entry is one paragraph plus a link to the article that owns the subject in full, grouped by where you meet the term and alphabetical inside each group. The last section takes apart the words that mean more than one thing.
Monitoring #
Check #
One execution of a monitor: one probe loading your URL, one WHOIS lookup, one spam-blocklist sweep, one incoming heartbeat ping. A check produces one row in the check log. An incident spans many checks.
Check Frequency #
How often a monitor runs. Most families set it on the Check frequency slider in the Notification Settings card of the editor's Main tab, while three have their own control: Report interval for Server, Expected ping interval for Heartbeat, Sweep every for Blacklist. DNS sweeps on a fixed cadence, and Real User has no setting. The fastest setting is plan-bound: Free 5 minutes, Basic 1 minute, Professional and Enterprise 30 seconds. Several families floor higher. See Plan Limits and Quotas.
Check Log #
The record of individual check results: one row per check per probe, with the response time, the status code and the probe that ran it. On a monitor's detail page it is the Check log card. Account-wide it is the Logs item in the sidebar, which opens the Monitoring Logs page. See Monitoring Logs.
Location Profile #
A reusable, named probe set: one of seven built-ins (including Europe and EU / GDPR), a hand-picked list, a geographic rule, or "all". Applying one writes its probes onto the monitor, and editing the profile later rewrites the monitors that still match its previous set. See Location Profiles.
Monitor #
One configured thing Uptimia watches: one URL, one certificate, one zone, one cron job. Monitors count against your plan per family, so an uptime monitor and an SSL monitor draw on different pools; Speed and Transaction are the one exception, sharing a single pool.
Monitor Family #
One of the twelve kinds of monitor Uptimia ships: Availability (Uptime, Transaction, API, Heartbeat and Server), Experience (Speed and Real User), or Domain & Trust (SSL, Domain, DNS, Security and Blacklist). The control panel groups them under Monitoring in the sidebar in exactly that order, and Server appears only on plans that include server monitoring. See Monitoring Overview.
Monitor Group #
A named set of monitors, created at Configuration → Groups, that filters the dashboard, scopes reports and maintenance, and limits what a team member can see. It is an enforced access boundary, not a filing convention. See Monitor Groups.
Monitor Note #
A note of up to 500 characters attached to a monitor, carrying runbook context. It appears on the incident page, in the alert email, and in the data Uptimia sends to a webhook. See Monitor Notes.
Monitor Template #
A saved snapshot of a configured monitor, used to create new ones by typing only a name and a URL. Editing or deleting a template never changes monitors already created from it. Ten of the twelve families can be templated; Server and Transaction cannot. See Monitor Templates.
Probe (Checkpoint) #
One of Uptimia's monitoring locations, a server that runs your check on a schedule and reports back. "Probe" and "checkpoint" are the same thing. Six families let you choose probes on a Locations tab, and a custom selection must contain at least 6. See Monitoring Locations and Coverage.
Detection and Incidents #
Availability Impact #
How much of an incident counts as downtime: full (the default), none, or partial, where only a stretch you pick counts. You set it from Availability impact in the incident's More actions menu, or for many incidents at once from the history list, on the Professional plan or above. The incident, its alerts and its logs stay as recorded. Only the downtime on dashboards, reports and public status pages changes. See Incidents.
Backup Check #
A confirming check queued from a different probe after the first one reports a failure. Uptimia queues as many as the monitor's Confirmations required setting, and confirms the outage once that many distinct backup probes also report down. See How Uptimia Monitoring Works.
Consensus #
The agreement between probes that a monitor is genuinely down. You set the outage-confirmation threshold per monitor. At 1, one backup check from a different probe still has to agree, while on an API monitor the first failing run alerts on its own and on a DNS monitor the first probe does. The exception on DNS is a record marked dynamic: when it appears or disappears, the monitor's other locations confirm that before anything opens.
Critical and Degraded #
The two severity levels an incident carries. Critical means the service stopped answering, and Degraded means it answered badly: slow, partly failing, expiring, or over a budget. Only critical incidents count as downtime in your availability percentage, and an automatic Security incident never does. The word an incident shows is per family: a Blacklist incident reads Listed, a Security one Warning with the finding named below it, a Domain one Expiry warning, a DNS one Alert active, and "Down" appears only where something stopped answering. See Monitor Statuses.
Incident #
A confirmed problem with a start time, an end time once recovered, an error code and a severity. Most incidents open automatically from failed checks, and a person can also open one by hand (see Manual Incident). Where a check log row is one data point, an incident spans the whole continuous period. Incident detail opens as its own page. See Incidents.
Maintenance Window #
A scheduled period during which selected monitors leave the check queue: a probe result that arrives during a window is dropped on arrival, with no log row, no incident and no alert. Heartbeat pings and server-agent samples are the exception (they keep being recorded, and only the alerting stops). The window's seconds leave both sides of the availability fraction. See Maintenance Windows.
Manual Incident #
An incident a person opens on a monitor with Open manual incident, for a problem the probes cannot see or have not caught yet. An Owner, Admin or Editor can open one on every family except Real User, as Critical or Degraded. While it is open, Uptimia stops judging that monitor automatically and the checks keep running. It alerts at once, ignoring the alert delay, and only resolving it, in the control panel or through the API, closes it. See Incidents.
Outage Confirmation #
The per-monitor control that decides how many confirming failures are needed before an incident opens: the Confirmations required dropdown on the editor's Advanced tab, where every plan offers 3, 2 or 1. A new monitor starts at 3. Recovery is asymmetric: one "up" backup check recovers the monitor whatever the threshold. See How Uptimia Monitoring Works.
Uptime (Availability) #
The share of a date range a monitor spent outside a critical incident, expressed as a percentage. Downtime is every second spent inside an open critical incident; degraded incidents, automatic Security incidents and SSL or domain expiry warnings add none, an incident set to an availability impact of none or partial adds only what it counts, and maintenance seconds leave both sides of the fraction, so a window neither helps nor hurts the number. See How Uptime Is Calculated.
Alerting #
Acknowledgment and MTTA #
Acknowledging an alert says "I've got it". It pauses the escalation ladder without closing the incident, and you can acknowledge from the control panel or from a signed no-login link in the alert. MTTA, or mean time to acknowledge, is the gap between the alert and that click, and Uptimia records it in minutes on the incident and in history. See Acknowledging Incidents and MTTA.
Alert Delay #
How long a confirmed problem must persist before the alert is sent. Set on the Alert delay slider in the Notification Settings card, 0–30 minutes, default 5; if the monitor recovers inside the delay, the queued alert is canceled. See Notifications and Alerting Overview.
Alert Group #
Monitors sharing an escalation policy that fail inside a join window are merged into one group: one digest, one ladder, one recovery alert. Grouping is on by default, and applies only to monitors with an escalation policy attached. See Alert Groups.
Alerting Schedule (Quiet Hours) #
The days and hours on which a given recipient may be paged, set per recipient on that recipient's own clock. The card reads Alert on these days. An alert due outside the window is held and delivered when the window opens, though a recipient with every day switched off gets nothing at all. See Alerting Schedules, Quiet Hours and Time Zones.
Contact #
One destination an alert can reach. You can create twelve types: Email, SMS, Slack, WhatsApp, PagerDuty, MS Teams, Status Page, Discord, Telegram, Mattermost, Twilio and Webhook, of which Email and SMS take a typed value and the other ten attach an integration profile. Uptimia no longer offers Twitter/X: the type cannot be created, and legacy rows never deliver. See Contacts and Alerting.
Escalation Policy #
A reusable named ladder. Step 1 pages one set of people. If nobody responds, step 2 pages the next, up to 10 steps with 1–1,440-minute waits and a bounded repeat. Attach one to a monitor by switching its Alerting card from All at once to Escalate over time; creating a policy requires the Professional plan or above. See Escalation Policies.
Integration #
A stored connection to an external service: a Slack webhook URL, a PagerDuty routing key, a Telegram bot. An integration is not itself a recipient. You attach it to a contact, and one integration can back many contacts. See Integrations Overview.
Recipient #
Who is paged when an alert fires. Uptimia works the list out at that moment rather than when you save, so an auto-include selection picks up contacts created later. A selected contact still will not deliver if it is unconfirmed, opted out, or a duplicate of another selected destination. See Who Gets Alerted.
Recovery Alert #
The "back up" message sent when an incident resolves, on by default. Its label is per family: Alert when the website comes back up for uptime, Alert when the job recovers for heartbeat, and so on. See Notifications and Alerting Overview.
Accounts, Roles and Plans #
Accounting / Billing Seat #
A role that sees invoices, plan and payment details and nothing else: no monitors, no contacts, no alerts. It does not consume a paid seat. See The Accounting and Billing Seat.
Monitor-Group Scoping #
Restricting an Editor or Read-only member to named monitor groups. Uptimia enforces the scope on the server: an out-of-scope monitor behaves as if it does not exist, and a monitor in no group is invisible to a scoped member. See Limiting a Member to Monitor Groups.
Owner #
The account holder: exactly one per account, with full control including billing, plan changes and account deletion. The roles picker cannot assign that role to anyone else.
Retention Window #
How far back your account can read its own history: Free 7 days, Trial 30, Basic 90, Professional 365, Enterprise 730. Uptimia deletes nothing to enforce this window. A request for a longer range is raised to your plan's floor, and upgrading widens what you can read instantly and retroactively, though it cannot surface rows the nightly prune has already removed. See Data and Log Retention.
Role #
One of five fixed access levels: Owner, Admin, Editor, Read-only and Accounting / Billing. A new invite defaults to Read-only. That role sees dashboards, monitors, incidents and reports and can still receive alerts, but it cannot change anything, and the Roles & permissions page lists what each of the five can do. See User Roles and Permissions.
Team Member #
Anyone with their own sign-in on your account other than the Owner. Each carries one role, has their own contacts and their own alerting schedule, and can be scoped to monitor groups. An invited member who has not activated their seat is still alertable. See Inviting Team Members.
Trial #
A 30-day evaluation that needs no card and ranks as the top plan: it gets the fastest check cadence and clears the Professional-and-above capability gates. When it ends, Uptimia downgrades the account to Free rather than canceling it. See When Your Trial Ends.
Two-Factor Authentication #
A second sign-in factor, held per identity. Each person turns on their own and chooses codes sent to their own mailbox or codes from an authenticator app, which also comes with one-time recovery codes for a lost phone. Uptimia offers no hardware-key or SAML option. See Two-Factor Authentication.
Words With More Than One Meaning #
DNS #
- The DNS monitor family. Queries your zone at its own authoritative nameservers, checks each server's health, and compares the records with a saved baseline so you see any change. See DNS Monitoring.
- The DNS sub-type of an uptime monitor. Under Main → Network, alongside TCP, Ping and UDP. It resolves the domain and compares the answer to the expected response. One record, one expectation. See Uptime Monitoring.
- Plain DNS records you edit at your registrar: the CNAME or A record that points your own domain at an Uptimia status page. See Status Pages.
API #
- The API monitor family. A set of HTTP requests run in order. Each step checks the answer it gets back and can pass values to the next step. Uptimia watches the chain on a schedule like any other monitor. See API Monitoring.
- The Uptimia REST API. The v2 interface you call to drive your own account: creating monitors, opening maintenance windows, reading incidents. See Getting Started with the Uptimia API.
Blacklist #
- The Blacklist monitor family. Sweeps spam blocklists for your domain and sending IPs. See Blacklist Monitoring.
- Browser safety flagging. Google Web Risk marking a site as unsafe, which is what the malware check of a Security monitor watches. See Security Monitoring.
- Your own firewall's allow or block list, where you permit Uptimia's probe addresses. See Whitelisting Uptimia's Probe IPs.
Logs — Two Screens #
The Check log card on a monitor's detail page and the account-wide Monitoring Logs page both hold check results. The Audit Log is a different record entirely: who changed what in your account, and every sign-in and failed sign-in attempt on its Sign-in & 2FA tab. See The Account Activity Log.