4 ms·
A website I own was affected by this. I got an alert from our monitoring saying the website was down for 1hr 2min 59sec. Luckily, they didn't redirect it to any
by rgbrenner 9y ago
A website I own was affected by this. I got an alert from our monitoring saying the website was down for 1hr 2min 59sec. Luckily, they didn't redirect it to anything.
I have other domains using Route53 (and hosted at AWS, just like this one).. that weren't affected AFAICT.
- brianucf 9y agoExperienced the same behavior on only one of my hosted zones. Started around 11:28am UTC
- isostatic 9y ago> I got an alert from our monitoring saying the website was down for 1hr 2min 59sec. That's a very accurate time. What system do you use to allow sampling at under 1 second intervals? My nagios boxes poll every minute, so an outage could be 2 seconds, or nearly 2 minutes, and nagios would report the downtime as 1 minute.
- outworlder 9y agoThey could be alerting based on metrics, instead of "pinging" the site.
- isostatic 9y agoYes, if the site serves up lots of traffic (multiple hits per second), then the hole in the logs would certainly give an indication. I get very suspicious when people quote things accurate to 1 part in 1000
- breakingcups 9y agoCould be a process that checks every minute with slightly inaccurate measuring which leads to 1h3m minus 1 second reported.
- syastrov 9y agoTo be accurate, that’s a very precise time. We don’t know if it’s accurate or not.