Skip to content

Uptime Monitoring

Monitoring 12 min read
On this page

An uptime monitor checks one target on a schedule from the probes you choose, and it opens an incident when enough of them agree the target is failing. The target can be a web URL, a mail server, or a network host and port.

For the detection mechanism itself (probes, backup checks, recovery), read How Uptimia Monitoring Works. Keyword Checks covers text matching on the page body.

Before You Start #

  • You need the Owner, Admin or Editor role. A Read-only member can open a monitor but not create or edit one.
  • Your account email must be verified. Until it is, Uptimia blocks the create, and the editor tells you so before you press save.
  • The Free plan allows 1 uptime monitor and a fastest check interval of 5 minutes. Both apply at once.

Creating an Uptime Monitor #

  1. Click Add Monitor on the dashboard and pick Uptime. On an account with no uptime monitor yet, you can instead open Monitoring → Uptime in the sidebar and click Create Uptime Monitor. Once you have one, the Add Monitor button sits at the foot of the monitors panel beside any monitor page.
  2. On the Main tab, choose what to check with the What should we check? control: Web, Email or Network.
  3. Enter the target. For Web that is Website URL; for Email and Network it is IP / Domain plus Port.
  4. Check the Monitor Name. Typing the URL auto-fills the name from the hostname until you edit the field yourself.
  5. Set Check frequency and Alert delay in the Notification Settings card.
  6. Pick your recipients in the Alerting card. At least one is required.
  7. Open the Advanced, Groups and Locations tabs if you need anything beyond the defaults.
  8. Click Save Monitor. Uptimia begins checking immediately.
The uptime monitor editor's Main tab, showing the Web/Email/Network selector, the Website URL field, and the summary rail reading the whole monitor back in plain language with a Ready to save verdict.Enlarge

The editor has four tabs (Main, Advanced, Groups, Locations), but it saves as one form. The summary rail on the right reads the whole monitor back in plain language, and each line jumps to the section that owns it. Below the read-back, Before you can save lists every blocking issue live and turns into Ready to save when there are none; after a blocked save, each tab label also carries a red count. The save bar shows the dirty state. Leaving with unsaved edits prompts you first.

To create many monitors at once, click Add Bulk beside the target field. The textarea takes one quoted URL and name per line, comma-separated:

Code
"https://www.website1.com/","Website name 1"
"https://www.website2.com/","Website name 2"

Add Single takes you back to the one-monitor form. Notes and Unique ID are per-monitor, so bulk mode does not send them. Every other setting applies to the whole batch.

Web, Email and Network #

The What should we check? segment picks the sub-type. Web has no second picker: Uptimia reads the protocol from the start of the URL (http:// or https://). Email and Network each add a Protocol segment.

Sub-typeProtocolTarget fieldsWhat the check does
Web—Website URLRequests the URL over HTTPS, or HTTP if the URL starts with http://
EmailSMTPIP / Domain, Port, optional String to send / String to expect, Use StartTLSChecks that your outgoing mail server accepts connections and answers correctly
EmailPOP3IP / Domain, Port, optional String to expect, Use SSL/TLSChecks that your POP3 mailbox server accepts connections and answers
EmailIMAPIP / Domain, Port, optional String to expect, Use SSL/TLSChecks that your IMAP mailbox server accepts connections and answers
NetworkTCPIP / Domain, Port, optional String to send / String to expectOpens a TCP connection to the port and optionally checks the response
NetworkPingIP / DomainSends an ICMP ping to check the host is reachable
NetworkDNSIP / Domain, Expected ResponseResolves the domain and compares the answer to the expected response
NetworkUDPIP / Domain, Port, optional String to send / String to expectSends a UDP packet and checks the response

The port placeholders name the usual values: SMTP 25, 465, or 587, POP3 110 or 995, IMAP 143 or 993.

Content matching (the Check if a specific content is on your website toggle) appears on the Web sub-type only. See Keyword Checks.

Notification Settings #

FieldWhat it doesDefaultLimits
Check frequencySlider setting how often the monitor runs. Reads back as a sentence: "Check for problems every 5 minutes".5 minutesPlan-dependent floor (5 minutes on Free), up to every 24 hours
Alert delayHow long a confirmed failure must persist before the down alert is sent. The incident is confirmed once it elapses; with an escalation policy attached, the ladder's timers start from that moment.5 minutes0–30 minutes
Alert when the website comes back upSends a recovery alert when the monitor returns to up.OnOn / off
Hold alerts for repeated short outagesFrom the 4th outage within an hour with the same error, the outage alert waits a few minutes and is not sent if the monitor recovers first. A new error, or a monitor that is down more than half the time, is alerted as usual. Webhooks, status pages and on-call tools such as PagerDuty always get the alert. Uptimia is still rolling the hold out: until it is active on your account, the switch is saved but every outage alerts as before.OnOn / off. Needs the recovery alert switched on, and is not used while an escalation policy handles the monitor.
The Notification Settings card of the uptime editor: the check-frequency slider reading back Check for problems every 5 minutes, the alert-delay slider set to 5 minutes, the recovery-alert toggle and the Hold alerts for repeated short outages switch, both on.Enlarge

The fastest interval you can select is 5 minutes on Free, 1 minute on Basic, and 30 seconds on Professional, Enterprise and Trial. Every other family's floor is in Plan Limits and Quotas. Above 1 minute the slider steps through every whole minute to 60, and beyond an hour the steps get coarser until it reaches its ceiling of 24 hours.

The Alerting card sits last on the Main tab and holds the recipients. Once your account has at least one escalation policy, the card also shows a mode segment: All at once or Escalate over time. In escalate mode the people paged come from the policy, and Uptimia works out who they are at the moment each step fires. You must still fill in the monitor's own list. It is the fallback (see Escalation Policies).

The Alerting card of the uptime editor: teams, people and contacts to tick on the left, and on the right the resolved list of all 13 contacts, with the SMS contact flagged not verified, counted as 1 won't deliver, and a note to resend its verification.Enlarge

Advanced Settings #

The Advanced tab is a stack of cards. Any card whose settings differ from the defaults carries an edited chip with a one-click reset.

The Advanced tab of the uptime editor as one scrolling stack of cards (Notes, Unique ID, Outage confirmation, HTTP Settings, Timeout settings, Error types to be reported and Email Branding Style), with an edited pill marking the cards changed from their defaults.Enlarge

Notes #

A free-text note of up to 500 characters: "Context for whoever picks up the alert". Monitor Notes covers where it surfaces.

Unique ID #

An optional identifier you choose yourself. It has to be unique inside the account, and it travels with the monitor into alert payloads (see Webhook Payload Reference), so your own systems can match an alert to their own record for this monitor.

Unique ID, HTTP Settings, Timeout Settings and Error Types to Be Reported are uptime-only cards, while Outage confirmation also appears on SSL, Speed, Domain, Transaction, API and DNS monitors. Notes appears on every family. Email Branding Style appears on every family except Server.

Outage Confirmation #

Confirmations required sets how many distinct backup probes must also report the target down before Uptimia opens an incident and sends the alert. The origin probe is not counted.

OptionBehavior
3 backup checks (recommended)The outage is confirmed only after 3 independent backup checks also fail
2 backup checksFaster, with one fewer independent opinion
1 backup checkFastest, and the most exposed to a single flaky probe

Recovery is asymmetric: a single "up" backup recovers the monitor whatever the threshold is. Lowering the number speeds up down confirmation only.

HTTP Settings #

These fields shape the HTTP request, so they apply to the Web sub-type.

FieldWhat it doesDefaultLimits
HTTP MethodThe request method the probe sendsGETGET, POST, HEAD
POST BodyRaw body content sent with the request. Appears when the method is POST.emptyFree text, e.g. {"key": "value"}
Username / PasswordHTTP Basic Auth credentials; leave blank for noneempty—
Custom HeadersHeader name and value pairs sent with every check. Click Add Header for each.none—

Uptimia never shows a stored Basic Auth password back, and on edit the field hints "A password is set — leave blank to keep it, or type a new one to replace it." The editor has no control that clears it. Leaving it blank keeps the stored password, and typing a new one over it is the only change the editor can make. Put bearer tokens and API keys in Custom Headers instead of the Basic Auth pair.

Timeout Settings #

FieldWhat it doesDefaultLimits
Timeout (seconds)How long probes wait before timing out301–100 seconds
Follow HTTP redirects (recommended)Follows 3xx redirects instead of treating the redirect as the answerOnOn / off

Leaving the timeout box empty saves 30 seconds. A value outside 1–100 blocks the save with Timeout must be between 1 and 100 seconds.

Error Types to Be Reported #

Downtime reports include only the error classes you tick. All seven are on by default.

Error typeWhat it covers
Connection errorsServer unreachable, connection refused
TimeoutsNo response inside the timeout
Unknown errorsUnclassified failures
HTTP errorsStatus codes in the ranges you select under Rejected HTTP response types
Redirect errorsUnexpected redirect behavior
Keyword / expected response errorsA keyword or expected-response rule failed
SSL errorsCertificate and TLS handshake failures

Note: Every uptime monitor reports SSL errors by default. This checkbox decides one thing: whether a TLS failure during an uptime check counts as downtime. Certificate expiry, chain and issuer tracking is a separate SSL monitor.

Ticking HTTP errors reveals Rejected HTTP response types:

RangeDefault
1xx InformationalOff
2xx SuccessOff
3xx RedirectionOff
4xx Client ErrorOn
5xx Server ErrorOn

Email Branding Style #

Selects the branding theme used for this monitor's alert emails. Every monitor family except Server has this card; server monitors have no Advanced tab.

Groups and Locations #

On the Groups tab, tick the groups this monitor belongs to. Create new group adds one inline with a name and a color.

The Locations tab card is Probe Locations, with three modes: All probes (recommended), Saved profile and Custom selection. Location Profiles covers what each one does, the built-in profiles and how a profile edit propagates.

A custom selection needs at least 6 probes. The panel counts as you pick, and blocks the save below that floor. How Uptimia Monitoring Works explains why 6 is the minimum.

If your account region is Europe, Uptimia pre-selects the Europe probe set on a new uptime monitor. A dismissible banner says so and points at All probes. The pre-selection is a default; you can change it.

The Probe Locations card with Custom selection active, showing the minimum-six-probe counter warning that three more probes must be picked before the monitor can be saved.Enlarge

Reading the Monitor Page #

The monitor page is one scrolling card stack, with no tabs. Top to bottom:

Stat strip. Four cells, each with a context sub-line:

CellValueSub-line
Current StatusThe status badge"for 3h 12m · since 04:18"
AvailabilityPercentage for the selected rangeDowntime in the range, the range length, and a "±N% vs prev" chip against the previous period
IncidentsCount in the rangeThe latest incident's time, or "none in this range"
Last CheckHow long agoThe configured interval. The cell hides at middling window widths so the other three fit on one row, and returns on narrow and very wide ones.

The availability figure is green at 99% and above, amber from 95%, red below. How Uptime Is Calculated explains how it is computed, and why the number can differ between two screens.

Charts. An Availability donut beside a Response Time line chart split into DNS lookup, connect, send, wait and receive.

Timeline. A bar of up, down and maintenance segments. Clicking a down segment opens that incident.

Incidents card. The 8 most recent incidents in the range, with View all incidents linking into the history pre-filtered to this monitor.

Check log card. Captioned "latest checks, newest first", with columns When, Result, Location and Response time. A backup check reads Backup check in the Response time column. Clicking a row opens the check detail drawer. The drawer carries the probe, the status, the response time, the URL, any expected strings and the error text, and View all logs opens the full log page.

An uptime monitor page: the stat strip with current status, availability, incident count and last check, the availability donut beside the response-time breakdown chart, and the timeline with the incident list below it.Enlarge

A brand-new monitor refreshes every 5 seconds until its first check lands, then every 60 seconds. Until the account has its first uptime monitor, Monitoring → Uptime shows a three-step explainer. Once one exists, that link opens the monitor itself, and the panel beside it lists the other monitors.

Saving a Monitor as a Template #

A template snapshots a monitor's whole configuration, so the next monitor takes only a name and a URL.

  1. Open the monitor page, click the ⋯ Actions menu and choose Save as Template.
  2. Enter a Template Name and, if useful, a Description, then click Save Template.
  3. To use it, go to Configuration → Monitor Templates, click Use on the row, then Create Monitor.

Editing a template later never touches the monitors already created from it.

Editing, Copying, Pausing and Deleting #

The same ⋯ Actions menu carries Edit, Copy, Pause / Resume, Open manual incident, Schedule Maintenance and Delete. A paused monitor runs no checks and sends no alerts.

Open manual incident raises an incident yourself when you know the service is broken but the checks still pass. Choose Critical (the monitor shows Down and the time counts as downtime) or Degraded (it shows Degraded and does not count), describe it under What's wrong, and tick Also post to status pages (offered when a status page shows the monitor) if visitors should see it. While it is open, the automatic checks do not change the monitor's status. Close it with Resolve manual incident in the same menu. A paused monitor, or one in maintenance, cannot get a manual incident. Incidents and Monitoring Logs covers the rest.

The monitor actions menu open on an uptime monitor page, listing Edit, Copy, Pause, Save as Template, Open manual incident, Schedule Maintenance and Delete.Enlarge

Warning: Deleting a monitor cannot be undone. Pause it instead if you only need the checks to stop.

Was this helpful?

Your answer helps the team improve this article.

Still need help?

Uptimia Bot answers right away and passes you to the team when it can't.

Source: https://help.uptimia.com/help/a/uptime-monitoring