Status Page Beta

Middleware Status Page lets you publish a branded, public-facing page that communicates the health of your services to customers and stakeholders. Link services to Synthetic Monitoring checks for live uptime data, report incidents with lifecycle updates, notify email subscribers, and embed a live status badge on your website or docs.

New to Status Page? Start with these three.

Find it under Synthetics → Status Page in the Middleware console.

  1. Create and publish your pagePick a subdomain, add your branding and go live
  2. Add your servicesFrom Synthetic monitors for live uptime, or manually
  3. Report incidentsPost updates as you resolve them — subscribers are notified

Key capabilities#

Everything a public status page needs, in one place.

Public status pages hosted at a Middleware subdomain (yourcompany.mwstatus.com) or your own custom domain

Service health displayed per component, driven by synthetic monitor data and incident updates

Incident management with impact types, workflow statuses, and a public timeline

Subscriber notifications via email when incidents are created or updated

Embeddable status badges (image, iframe, or Markdown) that reflect your page's current state

Branding controls including logo, favicon, theme color, and font

Guides#

Six guides, grouped by when you need them: setting the page up, then running it day to day.

How status is determined#

Middleware combines synthetic monitor results and incident data to show the current state of your page and each service.

Page-level status

StatusMeaning
UPAll added services are operational
DOWNAt least one service is degraded or in downtime

Service status

StatusMeaning
OperationalService is healthy
DegradedService is up but performance is impacted
DowntimeService is fully unavailable

Public banner labels

Visitors see one of these banners at the top of your status page.

All Systems Operational — everything is healthy

Some Systems Degraded — at least one service is degraded

Some Systems Experiencing Downtime — at least one service is down

When a service is linked to a Synthetic monitor, Middleware also polls recent uptime data (last 10 minutes) to refine service status alongside incident-driven updates.

Prerequisites#

  • A Middleware account with access to Synthetics
  • For custom domains and removing the "Powered by Middleware" footer: an active paid billing plan
  • For uptime charts and live service health: at least one Synthetic monitor (optional but recommended)

Next steps#

Two things to do once you have read this page.

Status Page is currently in beta. Some features such as Slack public subscribe are not yet available in the public UI.

Need assistance or want to learn more about Middleware? Get in touch with us via our Contact Us or join our Slack channel.

What did you think of this content?