[rdl]

Or just use twitter :)

I wish there were a business model for a third party site-monitor and site-uptime service, which let the site owner do more than just post updates, but also prevented the site owner from lying about historical data.

Basically New Relic (that actually worked) + Pingdom + Internet Archive + Twitter + status.example.com.

[jlgaddis]

Pingdom allows you to embed (JavaScript, IIRC) data on your own site showing your status/downtime/etc. from their perspective.

[mh-]

true, but let's add to the criteria:

reliable, accurate, high-frequency

[TazeTSchnitzel]

Yeah, but then what if that site went down? :P

[rdl]

Doesn't really matter -- as long as the odds outages at both sites are independent, and relatively low, it won't happen at both at the same time, usually. You can make the status service pretty reliable, cheaply, compared to most other services, and if it loses the central servers, the remote monitoring nodes can still store test information, so when the service comes back up, the historical record should be accurate.