BetaPreside is in beta. Thank you for helping us shape it: tell us what you think at info@presideos.com
Status

All checks are passing

What our monitor measured, and what we have told customers about incidents. Time with no saved check is shown as no data, never as up.

Checks by component

Each bar is one UTC day. Percentages are the share of saved checks that passed, and the coverage beside them says how much of the period has a saved check at all. Read them together: a high percentage with low coverage says little. Figures as of 22 Nov 2026, 13:12 UTC.

  • All checks passed
  • Some checks failed
  • All checks failed
  • No data
  • Application

    Passing

    90 days agoToday
    Last 30 days
    100.00%2,615 checks saved, covering 30.7% of this period
    Last 90 days
    100.00%2,615 checks saved, covering 10.1% of this period

    Last saved check: 22 Nov 2026, 13:10 UTC.

  • Database

    Passing

    90 days agoToday
    Last 30 days
    100.00%2,615 checks saved, covering 30.7% of this period
    Last 90 days
    100.00%2,615 checks saved, covering 10.1% of this period

    Last saved check: 22 Nov 2026, 13:10 UTC.

  • Sign-in

    Passing

    90 days agoToday
    Last 30 days
    100.00%2,615 checks saved, covering 30.7% of this period
    Last 90 days
    100.00%2,615 checks saved, covering 10.1% of this period

    Last saved check: 22 Nov 2026, 13:10 UTC.

  • File storage

    Passing

    90 days agoToday
    Last 30 days
    100.00%2,615 checks saved, covering 30.7% of this period
    Last 90 days
    100.00%2,615 checks saved, covering 10.1% of this period

    Last saved check: 22 Nov 2026, 13:10 UTC.

Incident history

This history begins on 13 November 2026. Events before that date are not listed here, so a short or empty list does not mean nothing happened earlier.

No incidents have been posted.

How to read this page

  • A scheduled job runs every 5 minutes. It requests the application's health address and the sign-in service, queries the database, and lists one item in the private file store. Each result is saved as pass or fail.
  • The monitor runs on the same platform as the application. If the whole platform goes down, the monitor goes down with it, and that time shows here as a gap rather than as a failure. If the database cannot be reached, results cannot be saved, so that time is a gap too.
  • A neutral monitor outside our platform is not connected yet.
  • A part shows no recent data when its newest saved check is more than 15 minutes old.
  • Incident posts are written by a person. The monitor never posts one by itself, so a failed check can appear here before an incident does.
  • These figures describe the past. They do not promise anything about the future.

All times are UTC. To report a problem, write to info@presideos.com. For how we protect board data, see Security.