- All monitoring is from EC2's us-east-1 region.
- I don't track the location of the sites, other than specifying the vendor.
- Data is generated by an open source tool called Stella. I'm not currently tracking DNS lookups but probably will eventually.
- Tests with errors are not included in the response times.
The specific response time is less interesting than looking at how a site performs over time (the number and duration of downtime, errors, etc). There are a lot of rabbit holes in testing so what I'm focusing on now is the simplest possible solution that works.
Sometime soon though, it will be possible to select the location.
As it stands, you're doing a disservice to startups that aren't on EC2, for no good reason. You solution "works" on a technical level, but the data is statistically meaningless.
Monitoring from a single location is interesting because it gives a metric for how well my application is performing.
If you have enough monitors and spread them out well (which shouldn't be too hard, since you could just sign up for Perl/PHP enabled hosting accounts in different locations), you can still diagnose where the slow geographical regions are.
In short, having more data can only give you a more accurate picture, depending on how you analyze it.
Build an image, load it onto a bunch of Pogoplugs, send them out to some friends who live in various parts of the world (and various parts of the US with various kinds of broadband!)
- Where are the monitors located?
- Where are the sites located?
- How was the site monitored? Did they account for DNS lookup and connection times in this time? 8ms for skysheet.com makes me think no?
- Are error times rolled into these times? Errors typically will respond quickly.
Having built www.yottaa.com, we worked hard to provide data that users can easily take actions against. In order to that understanding the questions above is important.