Source
Alerting, escalation & on-call — found from sitemap — Uptimia
Checked for Uptimia on 14 Nov 2026
- Page
- https://help.uptimia.com/articles/escalation-policies
- Checked
- 14 Nov 2026, 09:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:cbdb4d7138b682120db56c285fe227a5471c96526059b5555410e682dc0aec9f
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy definition Report an error
“An escalation policy is a reusable, named ladder of alert steps you attach to monitors. Step 1 pages a first responder the moment an incident is confirmed, later steps pull in more people while the incident stays open, and recovery cancels everything still pending.”
-
Escalation policy create plan gate Report an error
“Creating a policy needs the Professional plan or above. The trial clears the gate; existing policies keep firing on every plan, including Free.”
-
Escalation steps limits Report an error
“Steps The rungs, fired top to bottom. Step 1 is always t+0. 2 steps 1–10 steps”
-
Escalation wait limits Report an error
“If still down after … more The wait before the next step, counted from when the previous step fired, not from t+0. 15 minutes A fixed list, 5 minutes up to 2 hours”
-
Escalation recipients per step limit Report an error
“Recipients (per step) Who that rung pages. none Up to 30 entries per step”
-
Escalation recipient types Report an error
“Teams: every member, through each member's own contacts.”
-
Escalation repeat feature Report an error
“Once the last step has fired the ladder is finished, unless you turn on Repeat while the incident stays open. It is off by default.”
-
Escalation repeat limits Report an error
“every The gap between rounds, counted from the last thing the ladder fired. 30 minutes A fixed list, every 10 minutes up to every 2 hours”
-
Escalation no unlimited repeat Report an error
“There is no unlimited re-notification setting. If a ladder finishes without reaching anyone, the break-glass rule below pages the account owner.”
-
Escalation preview pane Report an error
“The right side of the editor is a Preview of an example incident confirmed at 09:41. It resolves every step to real contact names from your account, with the clock time each one fires, and shows the repeat rounds and the recovery row.”
-
Escalation monitor attachment modes Report an error
“The All at once | Escalate over time switch appears only once the account has at least one policy; until then the card shows the recipients panel and one nudge linking to the escalations page.”
-
Escalation monitor fallback recipients Report an error
“Uptimia falls back to that list when alert grouping or the escalation policy cannot handle the incident. A monitor whose policy was deleted, has no steps, or whose ladder could not start falls straight through to alerting its own recipients all at once.”
-
Escalation break glass ignores hours Report an error
“Uptimia then pages the account owner's contacts immediately, ignoring the owner's alerting hours and blocked days. The owner also joins the recovery list.”
-
Escalation recovery behavior Report an error
“Uptimia cancels every pending step and repeat round the moment the monitor recovers. The monitor's recovery toggle is Alert when the website comes back up, worded differently per family.”
-
Escalation acknowledgment behavior Report an error
“Acknowledging pauses the ladder rather than ending it: no further rungs fire, the incident stays open, and un-acknowledging re-arms it where it stopped.”
-
Escalation incident merging Report an error
“Monitors that share a policy and fail inside the join window merge into one incident with one ladder and one recovery alert.”
-
Escalation policy count cap Report an error
“There is no cap on how many policies an account can hold.”
-
Escalation readonly role Report an error
“A Read-only seat sees no create or edit controls at all. There is no New policy button, only View policy in a card's menu.”
-
Escalation billing role access Report an error
“An Accounting / Billing seat never reaches the page at all. Every control-panel route outside billing and their own Settings redirects it to Subscription, and the same refusal applies wherever the page is reached:”
-
Escalation downgrade behavior Report an error
“After a downgrade, existing policies stay attached, stay editable and keep paging. You cannot create another.”
-
Escalation policy account level Report an error
“A policy is an account-level object, like a monitor group or a location profile. Build it once and attach it to any number of monitors across all 12 families”
-
Escalation check frequency Report an error
“Uptimia checks open ladders once a minute, so a rung after step 1 can land up to a minute late. It never lands early.”
-
Escalation required role Report an error
“Your role needs the Manage contacts, teams & escalations capability: Owner, Admin and Editor.”
-
Escalation contact requirement Report an error
“Everyone you put on a step needs at least one confirmed contact. A person with none is flagged in the editor and skipped at fire time.”
-
Escalation recipients resolved at fire time Report an error
“A step stores the selection. Uptimia resolves it into concrete contacts the moment the step fires”
-
Escalation empty step saves Report an error
“A step with no recipients saves. The editor flags it ("This step alerts nobody — add recipients."), and at fire time the step pages nobody and moves on.”
-
Escalation delete behavior Report an error
“Warning: Deleting a policy cancels the ladders it is running right now. Rungs that had not fired never fire, and those monitors revert to their own recipient lists.”
-
Escalation duplicate behavior Report an error
“Duplicate copies the name with " (copy)", the steps and the repeat block; monitor attachments are not carried over.”
-
Escalation empty recipient blocks save Report an error
“That is why an empty selection blocks the save in both modes, with "At least one alert recipient is required". A monitor with no fallback recipients can go silent.”
-
Escalation policy name limits Report an error
“Policy name Names the ladder in the list, the monitor's policy select and the delete confirmation. New escalation policy Up to 100 characters; the rename box accepts 80”
-
Escalation reached nobody cases Report an error
“Three cases count as reaching nobody: a step with no recipients a step whose recipients are all outside their alerting hours a step whose recipients all have that day blocked”
-
Escalation manual save Report an error
“The editor never auto-saves. The bar reads Unsaved changes until you save”
-
Monitor template carries policy Report an error
“A monitor template can carry a policy into every monitor created from it.”
-
Escalation step wait skipped when nobody Report an error
“If a rung pages nobody reachable right now, there is nothing to wait for, so it does not consume its wait. The next rung comes due a minute later, at the next once-a-minute check.”
-
Escalation recovery respects alerting hours Report an error
“Recovery alerts respect each recipient's alerting hours, so a person whose down alert was held overnight gets the down alert and the recovery in order when their window opens.”
Scores citing this record
- The Agency Developer Alerting, escalation & on-call
- The Customer Support Lead Alerting, escalation & on-call
- The E-Commerce Operations Manager Alerting, escalation & on-call
- The SaaS Platform Engineer Alerting, escalation & on-call
- The Information Security Officer Alerting, escalation & on-call
- The Skeptic Alerting, escalation & on-call