Data Sources

Where the status page gets its data

The public page is built from your selected monitor provider plus any manual content you add in the editor. Statuscode does not invent live monitor health on its own.

Provider behavior

With UptimeRobot, Statuscode fetches monitor state, uptime ratios, response times, and recent logs using your API key.

With Better Stack, the live page uses the selected Better Stack monitor source.

Manual or demo data is useful for layout testing, but it should not be confused with real production monitoring.

What the page combines

Live monitor health from the provider.

Custom annotations and incident notes from the editor.

Scheduled maintenance windows from the maintenance manager.

Custom monitor display names and grouping choices from the theme config.

When data looks wrong

Check whether the API key is missing, invalid, or tied to the wrong provider.

Check whether the monitor was selected in the project.

If the editor preview looks right but the live page does not, publish again so the public snapshot updates.

Good rule of thumb

Provider

Supplies real monitor state.

Editor

Supplies branding, grouping, maintenance, and custom text.

Publish

Freezes the latest safe public shape for the live page.

Was this helpful?

Quick feedback helps improve the docs.