Lesson 10·Regulation & Risk·5 min read

How to Read a Status Page (Without Being Misled)

A green status page does not always mean everything is fine. Here's what to look for.

Status pages were invented by Atlassian's Statuspage product in the mid-2010s. Today every serious platform has one — but they vary wildly in honesty.

What 'all systems operational' actually means

A green badge means the platform's automated monitoring isn't tripping any alarms. It does not mean every user is having a working experience. If you're sure the platform is broken but the status page is green, you're probably not alone — there's often a lag of 10–30 minutes before an incident is acknowledged.

Reading uptime numbers

Monthly uptime of 99.9% sounds great until you realize it allows 43 minutes of downtime per month — usually concentrated during peak load. For prediction markets, that peak is exactly when you want to trade: election nights, Fed announcements, major sporting events.

Incident history is the real signal

Scroll past the green badge and read the incident history. Look for: frequency, average time to acknowledge, average time to resolve, and whether the same component fails repeatedly. A platform that posts post-mortems is signaling that it takes reliability seriously.

Frequently asked

Why is the status page green when the site is down?
Status pages update manually or on a delay. If many users are reporting an issue but the page is green, the incident hasn't been acknowledged yet.