One node should not be able to determine a server's online/offline state
At the time of reporting, it appears the Switzerland timing node went down due to some kind of network issue. This is currently causing ~50% of known servers to be recorded as offline, despite every other node saying the servers are online.
Instead of firing notifications and dropping the uptime percentage because of one node, it seems like the service should consider other nodes as well. If other nodes are reporting the server offline, or can be provoked to check, then the server should go down.
Although regional notifications could also be helpful. Ie: "Your server t2l.io is unavailable in Switzerland".
Edited by ar