They use statuspage.io, a great service, but most people use to manually set the times that the service was out - but I believe they have an API for that as well.
So I think MailGun just didn't indicate the service was unavailable when they put the outage details in.
A software engineer is firing a rifle on the shooting range, but not hitting any targets. Puzzled, he puts his finger into the barrel, and pulls the trigger. Seeing as his finger is blow off, he cheerfully reports to the instructor:
- On my end the bullets are flying out, so the problem is somewhere on your end, with the target!
The system would be useable. You just wouldn't be able to validate the certificate. That said, it's a fine line and I would consider the system down in this case anyway.
Yeah, but if your status page is made to be seen by external people, the right thing to do would be to monitor it just like if you were using it externally. There are whole slew of problems that wouldn't be exposed correctly if your monitoring point is internal -- like this exact problem, DNS, etc.
