Team Scout availability
Loading the record.
This month, day by day
Times are Central. Each bar is one day. The colored part is the share of that day's minutes the monitor measured.
Measured, no minute down
At least one minute down
Not measured
Before measuring began
Every recorded failure
A check is recorded as down only when it fails twice, 15 seconds apart.
Loading.
How it is counted
- What is checked, every minute
- The sign-in page, an admin workspace address, Team Scout's own always-open registration form, an organization's public site, the server functions the mobile app calls, and the data service the web and mobile apps share.
- A minute down
- Any one of those six fails twice, 15 seconds apart, within the minute: no normal answer, the expected words missing, or nothing back within 10 seconds.
- Availability
- Minutes up divided by minutes measured, rounded down to two decimals. Months are Central time.
- Coverage
- Minutes measured divided by the minutes in the month since measuring began. A minute no check reached is counted as not measured, never as up.
- Where the checks run
- On GitHub's computers, separate from where Team Scout runs, so an outage on our side cannot stop the record being written. Every result is a commit in a public repository, so the record cannot be changed after the fact without it showing.