cycles/min: 6 |
pings/min: 2,906 |
failed jobs (24h): 0 |
engine: active |
email: okay |
Happy Thursday :) :) :) :)
| Currently being monitored: [Home] | [Refresh] | [Auto Refresh] | [Full Screen] | ||||||
| # | Status | pinescore ? | Recent ms/Last online | LTA ? | Trace | Last Checked | IP | Public |
Key:
| Standard column color, node is in a normal state |
| Node stopped responding to requests within 24 hours |
| Node stopped responding to requests 24-48 hours ago |
| Node stopped responding to requests more than 48 hours ago |
| We take an average on the node response times over the last month, and we've found this node is currently responding slower than normal. Or it has dropped a single request. |
| We take an average on the node response times over the last month, and we've found this node is currently responding quicker than normal |
| Node has been online, and is starting to drop packets. Or - Node was offline and has just started responding. It's in limbo. |
| pinescore is below 50, node appears to be suffering intermittent drops. Worth investigating. |
| pinescore is below 0, node is dropping many packets, indicative of a problem. |
| pinescore (the score of the node), bold and Red: score has dropped in last 15 minutes, Green: score has improved in last 2 hours |
| [0] (the number in the box) if [>0]: node is moving towards an offline state if [>0]: node is moving towards an online state |
| Group Score: percent of nodes with a score higher than 50. If 90 or above you'll see a smily face too. You'll only see a group score if you're in the live view of one of your groups. |
[ ] The brackets at the end of the Status show how many times the ping has returned a different result from the current status. Once this is > 10 it will be considered a change in Status rather than a temporary hiccup.
pinescore is our score up to 100 for the stability of the host over the last 48 hours.