Status Pages

Your services.
A clearer status for everyone.

  • Give customers and teammates one place to check status.
  • Connect your checks and vendor status.
  • Publish updates that explain what’s happening.
status.your-domain.comExample
a

Acme status

All systems operational

System status

Last 30 days

API

Operational

Owner-reported status history

Oct 19, 2026Today · UTC

Nov 17, 2026 · Operational · 100% recorded. Operational: 9h 30m.

Dashboard

Operational

Owner-reported status history

Oct 19, 2026Today · UTC

Nov 17, 2026 · Operational · 100% recorded. Operational: 9h 30m.

Daily color shows the worst recorded status. Gray marks time without recorded status.

status.your-domain.com

Fictional snapshot ·

Interactive example · fictional service data.

Services people recognize

Show “Website” and “API.”
Connect the checks behind them.

Name each row after a service people use. Map each one to selected vendor sources and your own checks, or manage its status manually.

  • Use names your customers and teammates recognize.
  • Choose the checks behind each automatic service.
  • Set status manually when that fits your workflow.

Try changing the inputs in the example.

From your monitors to your status page

API uptime check

200 OK

Selected vendor service

Operational

Your customer sees

API

Operational

One named component on your page.

Both selected sources are operational.

Fictional inputs. A vendor report does not establish the cause of an issue.

From first report to resolution

Explain what’s happening.
Keep the history useful.

Publish updates as your investigation progresses. Choose the pages that receive each update and whether to notify their email subscribers.

  • Tell readers what’s affected and what you know.
  • Choose which pages receive each update.
  • Keep earlier updates in a timeline people can revisit.

Step through an incident. Preview the page and email together.

Subscriber email is available from Starter. Viewing permission and email subscriptions are managed separately.

One incident, from first report to resolution

Acme service status

Elevated API response times

Degraded
  1. Investigating09:12 UTC

    We’re investigating slower API responses. The website and dashboard remain available.

Subscriber email preview

Investigating: elevated API response times

We’re investigating slower API responses. The website and dashboard remain available.

Fictional incident. No messages are sent from this example.

Your brand. Your audience.

A familiar place to find out what’s happening.

Make your status page feel like part of your service. Give each audience the view they need.

  • Customers and internal teams

    Give customers a public view, or share a focused page with colleagues. Readers do not need workspace seats.

  • Control who can view it

    Choose public, unlisted, password-protected or private access. Private pages use approved-reader email sign-in and are available on Pro and Team.

  • Make the page yours

    Use your logo, brand color and footer links. Connect a custom page domain after verifying ownership.

A page that feels like yours
status.acme.exampleExample
a

Acme status

All systems operational

System status

Last 30 days

Website

Operational

Owner-reported status history

Oct 19, 2026Today · UTC

Nov 17, 2026 · Operational · 100% recorded. Operational: 9h 30m.

API

Operational

Owner-reported status history

Oct 19, 2026Today · UTC

Nov 17, 2026 · Operational · 100% recorded. Operational: 9h 30m.

Daily color shows the worst recorded status. Gray marks time without recorded status.

status.acme.example

Fictional snapshot ·

Public pages can be viewed without signing in. Fictional branding and domain.

Built around your workflow

The details that make a status page work for your team.

Choose your identity, audience and updates. Here’s what each option lets you do.

Your logo and brand

Add your logo, choose your page colors and link to your website, support or documentation. Your page should feel like part of your service.

All paid plans

Your own page address

Publish at an address such as status.your-domain.com. Verify ownership and connect the domain to your page.

All paid plans

Email updates for subscribers

Let readers follow your page by email. Choose whether to notify subscribers when publishing an incident update; subscriber limits are shared across your workspace’s pages.

Starter · Pro · Team

Choose who can subscribe

Allow anyone to subscribe, accept only approved email domains, or make subscriptions invitation only. Email subscription and permission to view a private page are separate.

Starter · Pro · Team

Password or private access

Share a password with people who have your page link, or use a private page where approved readers sign in by email. Pick the access that fits each audience.

Password: Starter · Pro · Team
Private: Pro · Team

Remove Statusfield branding

Remove the Powered by Statusfield footer from your page. This is separate from adding your own logo and colors, which are included on every paid plan.

Pro · Team

Choose a plan for your status pages and more.

Your status pages and monitoring share one subscription. Compare page limits, subscriber email, branding and access controls.

Basic

$5/mo

Billed monthly

Give customers a branded place to check your service status.

  • 1 status page
  • No subscriber email
  • Custom domain
  • Your logo and appearance
  • Password protectionNot included
  • Email subscription controlsNot included
  • Private pages with email sign-inNot included
  • Remove the Statusfield footerNot included

Starter

$20/mo

Billed monthly

Keep customers informed on your page and in their inbox.

  • 2 status pages
  • 150 email subscribers per workspace
  • Custom domain
  • Your logo and appearance
  • Password protection
  • Email subscription controls
  • Private pages with email sign-inNot included
  • Remove the Statusfield footerNot included

Pro

Recommended
$60/mo

Billed monthly

Share public updates or keep status private for approved readers.

  • 5 status pages
  • 600 email subscribers per workspace
  • Custom domain
  • Your logo and appearance
  • Password protection
  • Email subscription controls
  • Private pages with email sign-in
  • Remove the Statusfield footer

Team

$150/mo

Billed monthly

Share public updates or keep status private for approved readers.

  • 10 status pages
  • 1,200 email subscribers per workspace
  • Custom domain
  • Your logo and appearance
  • Password protection
  • Email subscription controls
  • Private pages with email sign-in
  • Remove the Statusfield footer

Subscriber limits are shared across all pages in your workspace. Permission to view a private page and an email subscription are managed separately.

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

Let’s talk about your status page.

Ask a question, discuss your setup, or get a walkthrough.

Frequently Asked Questions

Page limits, access and what your readers can expect.

How many status pages can I create?
Basic includes 1 status page and Starter includes 2. Pro includes 5 and Team includes 10. Compare current plan limits before choosing a plan for several teams or clients.
Can I use email without Slack or an on-call integration?
Yes. Starter includes up to 150 status-page email subscribers, shared across your workspace's pages. Basic does not include subscriber email. Workspace monitoring alerts are separate from page subscriptions.
Is a private page the same as a password-protected page?
No. Password protection uses a shared password. Private pages require email sign-in by invited readers or readers from approved domains. Permission to view a private page and a subscription to email updates are managed separately.
Does every vendor incident become an incident on my page?
No. You choose the checks behind automatic services and publish your own incident updates. Vendor-reported status can also appear separately as third-party context.
Can I use my own logo, domain and email sender?
Paid plans include custom logos and branding. Custom page domains are in preview and require domain verification. Pro and Team let you remove the Statusfield footer. Custom email sending domains are coming soon and are separate from your page address.
What history can readers see?
Published incidents have a timeline of updates and a monthly archive. Service-status charts show recorded history; manually reported status is not a measured uptime percentage. Incident history and monitoring-data retention are different.

Still have questions? Email us at support@statusfield.com or set up a meeting. All emails are read by humans.