Multi-site monitoring organized by client
Uptimia adds a client's sites in one paste and files them under that client. When one of them fails, the alert reaches that client's account manager, and the outage shows on their status page and in their next report.
Overview
Last 7 DaysSee which client is affected
The dashboard shows 2 of 87 monitors down. On a flat list you get no further than that, and you scroll to find out whose sites they are.
Give each client a group and both failures land in one lane. Uptimia alerts that client's account manager, marks the outage on their status page and lists it in their next report. People who look after the other clients get no alert, and those clients' status pages stay green.
Where a client's group appears
You make the group once, then pick it in maintenance windows, reports and team seats.
A maintenance window per client
Point a window at a whole group to mute one client's sites during their migration and leave every other client alone. Probes skip those sites until the window ends or you end it early.
Explore maintenance windows →A scheduled report per client
Send it daily, weekly, monthly, quarterly or yearly to the people you name, with PDF, HTML or CSV attached. Add group puts a client's monitors in the report in one click.
Explore scheduled reports →A seat limited to one client
Limit an Editor or Read-only seat to named groups. That person sees those monitors only, on every list, detail page, search and export.
Explore team roles →Your logo on reports and alert e-mails
Set up a branding theme and the report and alert e-mails from a client's monitors arrive with your logo and colors.
See white-label monitoring →A status page per client
Each client gets a public page that lists only their sites, with live state and uptime, and nobody needs a login to read it. It can be served from the client's own domain. Your logo can sit in the corner if you want it there.
- Their own domain. Point a DNS record at Uptimia and the HTTPS certificate is issued and renewed for you.
- Only the sites you pick. The page lists the monitors you choose for that client and nothing else.
- Logo and footer link. Upload your logo or the client's, and switch the Powered by Uptimia footer link off.
Components
Expand allAdd a client's sites from one pasted list.Each client gets a group and a status page.
A scheduled report per client can pick up the same group in one click.
Adding and organizing client sites
Make a template or a group once and reuse it for every site the client adds later.
A client's sites in one paste
Paste the list, one site per line, with a name if you want one. Every line becomes a monitor with the settings you chose once for the batch, so adding a client with 40 sites means pasting the list and confirming the preview.
- Preview before anything exists. Every row is marked ready or invalid, and nothing is created until you confirm.
- One bad row never blocks the batch. A site you already monitor is refused with the reason on its row, and the rest are created.
- Uptime, SSL, domain, speed and virus. Each of these monitor types takes the same paste.
New client sites from a template
Save a monitor you have already set up as a template. Interval, locations, recipients, groups and branding carry over to every monitor made from it, so a client's new site alerts the same people as the rest of their sites.
- A template per client or site type. Keep a production template for each client and one for internal staging.
- Monitors already made stay as they are. Editing or deleting a template never touches them.
- Usage counts. The templates page shows how many monitors each one produced and when it was last used.
One dashboard tab per client
Click a client's tab and the dashboard stats and monitor list narrow to their sites. Each tab shows a monitor count and a red badge when something in it is down.
- Several groups per monitor. A staging site sits in its client's group and in a Staging group at once.
- A view you can bookmark. The group is part of the dashboard address, so a saved or shared link opens straight to that client's sites.
- No limit on groups. Make one for every client you take on.
Alerts routed to each client's contacts
Recipients are set on each monitor. A template or a bulk paste sets them for a client's whole batch in one go.
Recipients per monitor
Pick people, teams or channels for each monitor. Put a client's account manager on that client's sites, and outages there go to that person.
Outage confirmation from other locations
A failed check is re-run from up to 3 other locations before anyone is paged. This keeps a network fault at a single probe from raising false alarms across a large fleet.
Alert delay per monitor
Hold the alert for up to 30 minutes for sites where a short blip is not worth a page, and keep it at zero for checkout and login.
- Confirmed before anyone is paged. A failed uptime, SSL or speed check is re-run from other locations, and they have to agree first.
- Routed by the monitor's own recipients. The incident goes to the people named on that site, so one client's outage never lands in another client's channel.
- The all-clear goes to the same people. Everyone who was alerted gets it, with the duration, and the client's status page turns green again.
Also included
Bulk actions
Tick monitors of any type and pause, resume, schedule maintenance or delete them together. History stays when you pause, and every action asks before it runs.
Copy a monitor
When a client adds one page, copy an existing uptime monitor and change only the URL. Interval, locations, keyword checks and recipients come with it.
Recovery notices
A recovery notice goes only to the people who got that monitor's outage alert.
Full REST API
A provisioning script with an API key can create a client's group and monitors through the REST API on the day the contract is signed.
{ "name": "Harbour Lane", "color": "#2166ad" }
Your brand on client pages
Your logo and a custom domain on client status pages, with the Uptimia footer link switched off. See white-label monitoring →
One dashboard for everything
Uptime, SSL, domain, speed and server monitors for every client live in one account and share the same alerting setup.
Worked examples by fleet type
Each example follows a single event through the monitor's settings to the dashboard and the people who get the alert.
Onboarding a new agency client
The agency looks after 10 clients with 6 sites each. When an 11th client signs, its 6 URLs go in as one paste with a keyword check on the footer text, so a white screen that still answers 200 counts as down.
On the dashboard and what happens →
- On the dashboard
- A tab for the new client appears in the scope bar with 6 monitors, and the All count goes from 60 to 66.
- What happens
- Each site pages the client's account manager and the agency channel from the first check. Pick the 6 sites for the client's own status page, and Add group puts all 6 in a monthly report.
Muting one region during a failover drill
The product runs from 3 regions with 4 endpoints each. The team drills APAC failover at night and expects those 4 endpoints to fail for up to an hour. Anything that breaks in the EU or the US meanwhile still has to page someone.
On the dashboard and what happens →
- On the dashboard
- The 4 APAC endpoints show as in maintenance. The EU and US tabs stay green and keep their own counts.
- What happens
- Probes skip the 4 endpoints and their alerts are muted for the window, while the other 8 keep checking and paging as usual. If the drill finishes early, select the 4 and end maintenance in one bulk action.
One shop loses its add-to-cart button
8 storefronts run on one platform, 3 of them under one brand. A theme update on one of the 3 drops the add-to-cart button. The page still answers 200, so a plain up-or-down check would report the shop as up.
On the dashboard and what happens →
- On the dashboard
- The shop turns red in the Shops tab and in the brand's own tab. The marketing lead's Read-only seat shows the same red row and nothing outside that brand.
- What happens
- Backup locations confirm the failure, then the alert goes to the dev team's Slack channel. Nobody in marketing is paged. They read about it in the weekly report, and when the button is back, the recovery notice closes the incident with the duration.
Sort every site by clientin one account.
Maintenance windows, reports and team seats all pick from the same groups.
How multi-site monitoring works
Uptimia monitors every site in your fleet from locations you pick out of 171+, one location per check, with sites added in bulk from a pasted list and filed into a group per client. A group narrows the dashboard to one client and picks their monitors for maintenance windows and reports. It can also limit a team seat to exactly their sites. Each client's status page shows the sites you choose for it.
01What format does the bulk import take?+
02What happens to a bad line?+
03Can each client see only their own sites?+
04Can a client's status page sit on their own domain?+
05How do alerts work across a fleet?+
06Can I pause monitoring for one client at once?+
07How do the per-client reports work?+
08Which team roles are there?+
09Is there a limit on groups or templates?+
10Can I automate onboarding with the API?+
11Which plans include multi-site monitoring?+
Group every monitor by client
Paste in a client's sites and file them under that client. Their status page lists only those sites.