Status Pages
Publish public, unlisted, or private status pages whose components reflect observed monitor results — never invented uptime.
What they show#
Components map to monitoring rules. Component health is observed from check results. Historical uptime graphs are not fabricated.
Set up, step by step#
Free includes one published page. A second page requires Pro.
Step 1: Open Status Pages
Choose Status Pages in the sidebar. Until you create a page the list stays empty — pages only show real checks.
Step 2: Create a page
Click Create status page. Enter a name and slug, choose visibility (Public, Unlisted, or Private), and attach components to existing monitors.
Step 3: Publish
In the editor, enable Publish page and save. Draft pages are not listed on public feeds. Published public and unlisted pages expose
/status.json,/feed.xml, and/atom.xml.Step 4: Verify the public URL
Open
{slug}.mydlestatus.comor/status/{slug}on mydle.app. Component states come from observed checks — attach at least one monitor before expecting green components.
Management#
Create and edit pages in /app/status. Attach components to monitors; maintenance windows are supported.
Public URL#
Customer pages render at {slug}.mydlestatus.com and at /status/{slug} on mydle.app. Visibility: Public, Unlisted, or Private. Free includes one published page. A second page requires Pro. Published public and unlisted pages also expose /status.json, /feed.xml, and /atom.xml. Private and draft pages are omitted from those feeds.
Incidents on the page#
When an incident has publishToStatusPage enabled, public updates appear on the status page. Otherwise the page can fall back to alert projections for component state. Internal notes never publish.
Limitations
{slug}.mydlestatus.comis the public hostname. A customer-owned domain such asstatus.customer.comis a Pro capability and is not routed yet; saving a page clears that field.- Mydle's own vendor system status at status.mydle.app is separate from customer pages.