Skip to main content
This guide walks you through configuring a public status page for your organization, selecting the components your customers should see, and publishing it.
Status page configuration

A configured status page ready to publish

​
Prerequisites

  • One or more components in your catalog. You can create them inline from the status page settings, but having them ready makes the flow faster.
  • The Admin role in your organization.
1

Open status page settings

Go to Settings → Status Page in the scaling.cloud dashboard.If you haven’t configured a page before, scaling.cloud has already created a draft for you with a default slug (org-<8-hex>). The page is not published yet — customers won’t see it.
2

Choose a slug

Pick a short, URL-safe identifier for your status page. The slug is part of the URL:
The slug must be unique across all scaling.cloud status pages. Lowercase letters, numbers, and hyphens; up to 63 characters.
Use your product or company name (e.g., acme, acme-platform). Avoid changing it later — customers may bookmark or embed the URL.
3

Select components to display

In the Components section, pick which components from your catalog should appear on the page.Components are grouped on the page by their groupLabel. To group them, set a groupLabel (e.g., Platform, Payments) on each component in Settings → Components.
4

(Optional) Set manual overrides

For planned maintenance or a known issue you want to surface separately, set a component’s status manually:
  • Maintenance — declare planned maintenance on a single component. The overall banner reads Under maintenance while it’s set.
  • Degraded / partial outage / major outage — force a status that takes precedence over the live incident-derived status.
Manual overrides win over incident-derived status. Use the Clear override button to return the component to its automatic status.
To announce planned work as a titled notice with its own time window spanning several components — rather than flipping one component’s status — schedule a maintenance window instead.
5

Publish

Toggle the Published switch at the top of the page settings.Your page is now live at https://scaling.cloud/status/<slug>. Share the URL with your customers, embed the JSON feed at https://scaling.cloud/api/public/status/<slug> in your help center, or attach a custom domain like status.example.com.

​
Verify the page

Open the URL in an incognito window (no scaling.cloud account needed) and confirm:
  • The overall banner reflects the current health.
  • Components are grouped as expected.
  • The header and component names match your brand voice — these are customer-visible.

​
Unpublishing

Toggle Published off at any time. The page immediately returns a 404 for new requests; the CDN cache (30 seconds) flushes shortly after.

​
Publishing your first incident update

Once the page is live, the next thing your team will want to do during an incident is post a public update — a customer-visible message that lands on the status page. This is a separate, deliberate action from filing the incident itself. You can publish from three surfaces: Every surface defaults to internal. Publishing is always an explicit choice — you cannot accidentally push staff chatter to customers.

​
NO_PUBLIC_SURFACE — what it means and how to avoid it

A public update is rejected with NO_PUBLIC_SURFACE when the incident’s affected components don’t overlap any selected components on a published Status Page. Two common causes:
  • The incident was filed without componentIds, so it has no components to match against.
  • The components on the incident aren’t on this Status Page’s selected list.
Fix by either tagging the incident with one of the page’s components, or extending the page to include the incident’s components. For the full data model (visibility, redaction, the render rule on the public page), see Incidents — Incident Updates.

​
Next steps