A public status page that answers before support does.

When something breaks, everyone asks at once — and someone has to answer while also fixing it. Uptimia runs a status page on your own domain that updates itself from the monitors already watching your site, so customers see what's happening without anyone writing a word.

Create your status page → View pricing
Included on the free plan Custom domain + automatic SSL No credit card
Live in under
5min
Extra cost
0
Certificates to buy
0
Free plan includes
1
Status pages

Your status page, on your domain.

When something goes wrong, your status page is how you communicate with confidence. Beautiful, branded, and it updates itself.

This demo is live — click it
Brand
The day
status.caldmont.com/
Caldmont History

Get status updates

We'll notify you when an incident is created, updated, or resolved.
Degraded Performance
Updated just nowLive

Checkout processing intermittentSee details ↓

Since last incident
37days
90-day uptime
99.98%
90 days ago99.98% uptimeToday
IncidentMinor
Checkout processing intermittent
Identified14:24 UTC
Upstream payment provider is degraded. We're failing over to the secondary lane — most checkouts will complete on retry.
Components
90 days agoToday
90 days agoToday
90 days agoToday
Operational Degraded Outage Maintenance
Update history
View full history →
July 20262 events
API elevated error ratesResolved42m
Jul 12, 2026 · 09:14 UTC
Database maintenance — read replicasCompleted30m
Jul 5, 2026 · 02:00 UTC
Your own domainstatus.yourbrand.com
Subscriber alertsEmail on every incident update
Your logoOn the page and in subscriber email
Embeddable widgetLive status on your own site

The hour nobody had to ask

What your status page does during a real incident.

14:32:18 The page flips first — automaticallyMonitors confirm from three regions; the service shows Degraded on its own page: Degraded
14:39 One update, everyone toldYou post once — 1,284 subscribers emailed, every visitor sees it live page: Investigating
meanwhile Support answers with a linkCustomers refresh the page, not your ticket queue page: Investigating
15:42 Resolved — on the recordHistory keeps the incident; the 90-day bars record the day page: Operational
1 postanswers everyone
Already handled.15:42
Everyone who wondered got the answer from the page — before they asked. And the incident didn't vanish when it ended: it's in the history, proof you handle things in the open.
flips with your monitorssubscribers emailed90-day bars + historyyour domain · your logo
And without the page? Every curious customer becomes a ticket, and every ticket gets a hand-typed "we're aware". The ones who don't write just refresh, wonder, and remember the silence. ticket per person

Fed by your own monitors

The same checks that alert your team feed the page — every uptime, page-speed and SSL monitor you run, each with live state and uptime bars.

Uptime checksChecked as often as every 30 s
Page speedFull-page load time, charted
SSL certificatesExpiry caught weeks early
Ports & TCP servicesAny port on any host
7 check types every one of them page-ready
Mail serversSMTP, POP3 and IMAP
Ping & DNSReachability and resolution
Full page loadReal browser, every asset
Every service on the page shows its live state, 90-day uptime bars, incident history and scheduled maintenance — fed by the same checks that alert your team. auto-updated
Explore website uptime monitoring →

Everything a status page needs

Live from your monitors

Built from real checks, not promises

The page is wired to your monitors. When a check confirms trouble, the service flips to degraded or down on its own; when it recovers, the page recovers with it.

  • Automatic states — operational, degraded, outage and maintenance derive from live monitor results
  • 90-day uptime bars — per service and page-wide, with an exact uptime percentage
  • Sections you control — group services the way customers think about them, in the order you choose
How status pages work →
HTTPCheckout monitor200 OK · 142 msoperational
HTTPPayments API monitorerrors · confirmed ×3degraded
HTTPWebhooks monitor200 OK · 89 msoperational
autofrom live
checks
Payments — public pagelive
Checkoutoperational
Payments APIdegraded
Webhooksoperational
Flipped the moment the check confirmed — nobody remembered to flip a switch, and recovery flips it back.
90-day uptime bars under every service — and page-wide — with the exact percentage, not a vague green row. 99.87%
Incident communication

Post updates people actually see

Post staged updates — investigating, identified, monitoring, resolved — and every subscriber gets each one by email. Maintenance goes up in advance, so planned work never looks like an outage.

  • Staged incident timelines — a clean, timestamped story instead of one vague banner
  • Scheduled maintenance & announcements — upcoming windows shown ahead of time, notices with minor/major severity
  • Email subscribers, done right — double opt-in, one-click unsubscribe, no per-plan subscriber caps
Incident updates docs →
1
Investigating
14:39 · elevated card errors
posted
cause found 12 minutes later
2
Identified → Monitoring
14:51 · fix deployed 15:20
2 updates
watched until stable
✓
Resolved
15:42 · total impact 70 min
closed
Every update, emailed4 sent
Each stage reached every subscriber the moment it posted — a timestamped story, not one vague banner.
double opt-in1-click unsubno caps
Planned work never looks like an outage — scheduled maintenance goes up on the page in advance, with minor or major severity. Sun 02:00
Access control

Private status pages — password or IP allowlist

Client dashboards, internal tools, staging — flip one setting and the same page turns private. Wrong password or unlisted IP gets the same quiet denial, and search engines are told to stay away.

  • Password protection — one shared password unlocks the page for 12 hours; brute force is rate-limited
  • IP allowlist — restrict the page to your office or VPN ranges (CIDR supported); anything else is denied, fail-closed
  • Invisible to search engines — protected views are sent with noindex and never cached
Private pages docs →
pwTeammatecorrect password12 h pass
ipOffice VPN10.8.0.0/24 · allowlistedallowed
?Unknown visitorwrong password · unlisted IPdenied
authpassword
or IP
Private page served12 h
status.caldmont.com unlocks with a signed, HttpOnly cookie. Wrong password or unlisted IP gets the same quiet denial — fail-closed.
noindexnever cachedrate-limited
One page, three visibility modes — public, password or IP-private; switch any time without changing the URL. same URL
Your domain, your brand

status.yourdomain.com — SSL handled for you

Point one DNS record at Uptimia: the certificate is issued and renewed automatically, and your page serves over HTTPS on your own domain. No certificate files, no renewal calendar.

  • CNAME or apex — use a subdomain like status.yourdomain.com, or an A record for a bare domain
  • Your logo, their comfort — custom logo, light and dark themes, custom CSS if you want to go further
  • "Powered by Uptimia" is optional — one toggle removes it from the page, on every plan
Custom domain setup →
LIVEhttps://status.caldmont.com
your domain · your logo · served by Uptimia
CNAME status → status.uptimia.comverified
TLS — Let's Encryptauto-renews
"Powered by Uptimia"removed
Hosted on Uptimia's infrastructure — the page stays reachable even when your own servers are down.
One DNS record 
status.yourdomain.com
CNAME → status.uptimia.com
Certificate — automatic 
issued & renewed for you
no files, no renewal calendar
Branding 
logo · light & dark themes · custom CSS
"Powered by" is a toggle, on every plan
Bare domain instead? An A record at the apex serves yourdomain.com just as well — same automatic certificate. A record

Your status page should update itself.Before the tickets pile up.

Every page, every subscriber, every monitor behind it — free for 30 days, and none of it is a paid add-on.

Start your free 30-day trial →
30 days free no credit card cancel anytime

Your status page in three steps

If your monitors already exist, the page is mostly done before you start.

Step 12 minutes

Pick what the page shows

Choose monitors, group them into sections, drag them into the order your customers think in.

Services on the page
WebsiteCheckout pageMail serverSSL cert+ 8 more
grouped into 2 sections · live preview updates as you build
Step 22 minutes

Set domain & visibility

Add your domain — SSL is issued for you. Leave the page public, or protect it with a password or IP allowlist.

Custom domain
status.caldmont.com
CNAME verified · certificate issued automatically
Visibility
PublicPasswordPrivate · IP
Step 3automatic

Share it once

Put the link in your footer and support replies. Visitors subscribe themselves — the page does the informing from then on.

Subscribe for updates
anna@example.com
confirmation email sent · double opt-in
Live
status.caldmont.com · every incident update now emails 1,284 people

Also included

Manage pages from the API

Create and update status pages from scripts or CI with per-user API keys.

POST /api/v2/status-pages → 201 · page created · status-client-acme

Incident history

Past incidents stay on the page, month by month, with their full update timelines.

July · 2 incidents · 1 maintenance

UTC or local time

Visitors flip every timestamp between UTC and their own timezone with one toggle.

14:39 UTC ⇄ 16:39 local

Light & dark theme

Follows each visitor's system preference, with a manual toggle on the page.

system · light · dark

Response-time chart

Optionally show average response times on the page — off by default, on with one toggle.

412 ms · avg response · optional

More pages as you grow

Run one page per product, per region, or per client — up to ten status pages on team plans, and effectively unlimited on the largest plan.

status.caldmont.comPUBLIC status-internal.caldmont.comPRIVATE · IP acme.caldmont-status.ioPASSWORD

What is a public status page?

A public status page is a web page where a company shows the live health of its services — what's operational, what's degraded, and what's being fixed — along with incident updates and planned maintenance. During an outage, customers check the page instead of opening support tickets, and the published history becomes a track record.

Without a status page

Every visitor asks support

Outage
14:32 · confirmed
same question × everyone
Support inbox
"is it down?" · one reply each

The team firefights the outage and the inbox at the same time.

With a status page

Everyone checks one page

Outage
14:32 · confirmed
one update · everyone
status.yourdomain.com
live states · updates · history

One public page answers every visitor at once — and subscribers hear from you before they think to ask.

Public · password · private

Three visibility modes, one page

The same page can face the world, a client, or only your team — switch modes without changing the URL; protected pages are noindexed and never cached.

How access control works →
PublicPasswordPrivate
Who can viewAnyoneAnyone with the shared passwordOnly allowlisted IPs
How access worksOpen linkPassword → signed 12-hour cookieIP / CIDR match, fail-closed
Search enginesIndexednoindex · never cachednoindex · never cached
Best forCustomers & prospectsClients & stakeholdersInternal teams · office / VPN

Status page FAQ

01What is a status page and why do I need one?+
A status page shows the live health of your services — current state per service, incident updates, and planned maintenance. During an outage it answers "is it down?" once for everyone, and its visible history becomes proof of how reliably you operate.
02Does the status page update automatically?+
The states do. Each service is a real Uptimia monitor, so operational, degraded, outage and maintenance flip automatically from live check results. Incident updates are yours to write: investigating → identified → monitoring → resolved.
03Can I password-protect my status page?+
Yes. A password-protected status page uses one shared password (10+ characters); entering it grants 12 hours of access through a signed, HttpOnly cookie — no visitor accounts to manage. Wrong passwords are rate-limited and get the same generic response, so the gate leaks nothing.
04Can I restrict my status page to office or VPN IPs?+
Yes — that's the private mode. List the IP addresses or CIDR ranges that may view the page; every other visitor is denied. The check fails closed: if the allowlist can't be evaluated, nobody gets in.
05Do private status pages support SSO or per-user logins?+
Not today. Private pages use a shared password or an IP allowlist — simple mechanisms with no directory to manage. If your security policy requires SAML SSO with per-viewer identities, a dedicated enterprise status-page product is a better fit for that page.
06Can I use my own domain for the status page?+
Yes. Point a CNAME like status.yourdomain.com at Uptimia (or an A record for an apex domain). The SSL certificate is issued automatically and renews itself — you never handle certificate files or renewal dates.
07How do subscribers get updates?+
By email — visitors subscribe on the page, confirm via double opt-in, and receive every update you publish, with one-click unsubscribe. Email is currently the only subscriber channel, and there are no per-plan subscriber limits.
08Will search engines index my status page?+
Public pages: yes — they're normal, indexable pages. Password-protected and private pages: no — every protected view is sent with noindex and never cached, so protected content stays out of search results.
09Is a status page included in the free plan?+
Yes — you get a real free status page: email subscribers, a custom domain and automatic SSL, no credit card required. Password protection and IP allowlisting come with the paid plans — part of every one of them, never a paid add-on — and the 30-day free trial unlocks them too. Basic includes one page, Professional ten, and Enterprise is effectively unlimited.
10Will the status page stay online when my site is down?+
Yes. It runs on Uptimia's infrastructure, separate from your servers, so when your stack is down the page that explains it stays up. Even on a custom domain, DNS points at Uptimia.
11Which of my monitors can go on the status page?+
Uptime, SSL and page-speed monitors. Uptime covers more ground than the name suggests — websites and APIs over HTTP or HTTPS, any TCP port, ping, DNS, and SMTP, POP3 or IMAP mail servers all count, so most of what customers care about is already eligible. Transaction, server, domain-expiry, virus, blacklist, heartbeat and real-user monitors keep alerting your team, but they do not appear as components on a status page, and the monitor picker will not offer them. If you want a checkout flow represented publicly, put the uptime monitor for the checkout page on the page instead.

Downtime happens. Going silent is optional.

Put up one public page — and the next outage makes you look prepared instead of absent.

Create your status page →
Included on the free plan Custom domain + automatic SSL Password & IP protection No credit card
Status pages are part of every Uptimia account — live monitor states, incident updates, subscribers and custom domains included.