Crown Road Software thanks for reaching out, a small clarification first: if you use the API to mute alerts, as the name imply, the monitoring continues and count your downtimes as they occur (you just don't get alerts). It's not the "muted" time that counts as downtime though, only the actual downtimes.

If you switch to disabling the check instead, it would indeed stop the monitoring and thus "hide" the downtime, it will be considered as uptime. To be more precise: it'll be considered as uptime or downtime depending on the current state when you disable the check, so if you wait until the check is down before disabling, you're not gonna get uptime :)

And finally about the double uptime metric (including and excluding maintenance), that's unlikely to be added as it would be a bit too niche for updown.io design goals (simplicity & price). But with some work you can track those on your end using the downtime API, if you have deployments/maintenance kept on your end you can distinguish real downtimes and compute multiple uptime metrics however you want. I may add later a downtime comment feature though, so you can flag some downtimes as deployment or planned maintenance for your status page display and own recollection.

Adrien Rey-Jarthon thanks for the reply, I will look into changing our integration to disable the checks instead of muting it.