Skip to main content
The settings on a status page are documented alongside the tabs that hold them in Creating a Status Page. This page collects the limits and timings that are not settings — the fixed behaviours you cannot configure, but which decide what your subscribers experience. Most of them show up as something that looks like a bug the first time you meet it, so they are gathered in one place.

​
Reference

​
Subscriber Verification

Someone subscribing to a public status page receives a verification email. On a private status page, a signed-in user is subscribed directly, without one. That verification link is valid for 30 minutes. After that it expires and they have to subscribe again. Thirty minutes is short enough that a link left in an inbox over lunch will not work. If subscribers report that verification “doesn’t work”, the likely cause is elapsed time rather than a broken email — ask when they clicked, not whether they clicked. An address that is never verified is purged after 30 days. It receives nothing in the meantime; an unverified subscriber is not a quiet subscriber, it is not a subscriber at all.
Neither window is configurable. If a major incident is the moment people try to subscribe, expect some of them to miss the 30-minute window while the incident has their attention.

​
Uptime Tracking Flap Guard

This one is about uptime history, not about what your page displays right now. For a component linked to a service, functionality, or third-party component, uptime is measured over the periods it was actually attached to the page. Detach one and the period closes; re-attach it and a new period opens, with the gap between them rendering as “no data” rather than as uptime or downtime. Re-attaching within 1 hour reopens the period you just closed instead of starting a new one. So an accidental detach, noticed and corrected promptly, does not punch a hole in the chart. A component can accumulate at most 100 tracked periods. At that cap a re-attach always reopens the most recent period regardless of the hour — trading an exact gap record for bounded growth on a component that is being attached and detached repeatedly.
Nothing here delays or smooths the status a component displays. A component’s status comes from the incidents on the page — or, for a third-party component, from that vendor’s own status — and changes when they do. If you are looking for why a component shows the wrong colour, the answer is in those incidents, not here — see Publishing Incidents.

​
Uploaded Images

Logos, favicons, and other images must be strictly under 2 MB — the check is < 2 MB, so a file of exactly 2.00 MB is rejected along with anything larger. The limit applies separately to the logo, the favicon and the Open Graph image. An oversized logo is nearly always an unoptimised export. Compress it rather than reaching for a smaller image — 2 MB is generous for anything a status page displays.

​
Password Attempts

A password-protected status page accepts 30 attempts every 5 minutes, per IP address. Beyond that, further attempts are refused until the window clears. Per IP is the detail that matters. Colleagues on different networks each get their own allowance, but everyone behind one office network or VPN shares a single one — so a rotated password can lock out a whole floor while remote workers get in fine. Distribute a new password before you rotate it, not after. See Status Page Authentication Methods for configuring password and SAML access.

Creating a Status Page

The settings themselves — setup, customization, components, and templates.

Authentication Methods

Password and SAML access control for a status page.