Interesting. Where are you pinging from? I'm seeing much less https ping:
https://cloudup.com/c47xyiOpV4g
for https://statusduck.io/76687749-5690-48d9-9bd6-2f258f615978
and see ~500ms when curling from various places outside the EU.
https://cloudup.com/c47xyiOpV4g
for https://statusduck.io/76687749-5690-48d9-9bd6-2f258f615978
and see ~500ms when curling from various places outside the EU.
If you want to get HTTP status message, send a HEAD request. If a server handles it differently than a GET without a body, that's not your problem. As an application developer, you might do this on purpose as a health check.
I'm not saying my solution is without flaws, just saying actually detecting "status" automatically isn't trivial and HEAD requests only expose one facet if this.
Regardless, just because HEAD requests CAN time out doesn't mean they WILL, even in good faith. GET requests will surface precisely the same behavior browsers do.
> it's very unlikely your 15ms is the total response
I'm seeing 9ms for the entire HTML payload on the server itself, and 90ms from my house. It's just returning a pre-generated html file, so it shouldn't be slow at all, bandwidth/RTT withstanding.