01
What it looks at
What each part of the answer means, and what to do when one is not right.
Press the button and your browser times a request to each AWS region’s public health check, three times each, and ranks them from nearest to furthest.
What this check looks at
The time for a request from this browser to reach each AWS region’s public DynamoDB health endpoint and come back. The first request to each region pays for looking up its address and agreeing encryption, so the shorter of the next two times is kept.
What the answer tells you
Every 100 milliseconds of round trip slows each request your app makes to a far region. Run your app and its data in the region nearest most of your users, and keep the two together.
What to do with it
Ask the people you serve to run this from where they are, choose the region nearest most of them, and check the region’s laws on where data may be kept. A region that did not answer is either busy or not reachable from your network right now.
02
What people ask about it
Straight answers, from what the check itself does.
- Why does my result differ from a friend’s?
- The figures are from your network to each region: your provider, Wi-Fi and distance all add to them. That is exactly what your users will feel, so it is worth asking them to run it too.
- Is anything sent to Xovris?
- No. Your browser asks AWS’s public health endpoints directly. AWS sees your address as it does for any request. Nothing reaches Xovris.
Add your site and Xovris checks it from outside every 3 minutes, with an alert by email or Slack the moment it stops answering.
Watch my site free
Words on this page, in plain English
Each technical word this page uses, said simply.
- Response time (latency)
- How long something takes to answer, usually counted in milliseconds – thousandths of a second.