How Awe Status works
Awe Status answers one question: is it down for everyone or just you. Here is where the numbers come from and where their limits are.
Two sources
User reports and our own check. We open popular sites from our list every 5 minutes from a server in Helsinki. Any other site is checked when you press “Check now”, and from 6 countries (Kazakhstan, Russia, Ukraine, Turkey, Germany, USA) through the open check-host.net node network.
When we say “outage”
For each service we compute the usual number of reports per hour over the previous week. “Possible problems”: at least 3 reports in an hour and twice the usual, or our server can’t open the site for 10 minutes. “Outage”: at least 8 reports and 4 times the usual, or the site doesn’t open for 15 minutes.
Limits
Our check sees whether a site answers, not whether login, payments or the app work. That only shows in reports. If a site blocks foreign addresses, our check is left out of its status. If a third of all sites fail at once, our own network broke, and we don’t record that run.
Protection from fake reports
One report per service per device every 30 minutes, at most 10 different services per device per hour, bots are filtered out. A new site appears only if the domain exists.
What we store
Report reasons, time, country and city from Cloudflare, and device type. Instead of an IP: an anonymous device fingerprint. Raw reports are kept for 92 days, hourly totals for 400 days.
Who made it
Awe Status was built by Viktor Kravchenko, founder and developer of the Awe ecosystem: the Awe Reads magazine, the Awe Check website checker and the Awe ID account.