PS> (Get-EveEsiStatus).count
205PS> (Get-EveEsiStatus).count
199
CCP remove endpoints from their own status API so you cannot track status of a down endpoint. That’s the most stupidest thing ever.
Whoever designed that needs a refresh course in how to implement a status API.
You have four status, 3 official statuses, green yellow and red, and the invisible cloaked fourth.
See my complaints on this here Https://esi.evetech.net/latest/characters/{character_id}/assets/ returning 404 - #10 by Emotional_Support_Clown, here Https://esi.evetech.net/latest/characters/{character_id}/assets/ returning 404 - #14 by Emotional_Support_Clown, here Https://esi.evetech.net/latest/characters/{character_id}/assets/ returning 404 - #16 by Emotional_Support_Clown and here Https://esi.evetech.net/latest/characters/{character_id}/assets/ returning 404 - #20 by Emotional_Support_Clown.
Can you either show it as status:red or a new fourth state of status:dead but please keep the status API stable.
Sitting here figuring out which one is missing is not good.
Then I can do things like track it over time reliably and
PS> Get-EveEsiStatus|where {$_.status -match 'red|yellow|dead'}|ft
PS> (Get-EveEsiStatus|where {$_.status -match 'red|dead'}).Count
PS> Get-EveEsiStatus|where {$_.status -match 'red|dead'}|select -Unique tags