Actually it seems to be on and off at random. Might be just a bug.
probably related to
Yes
PS> Get-EveEsiStatus|where {$_.status -match 'red|yellow'}|ft
endpoint method route status tags
-------- ------ ----- ------ ----
esi-alliances-protobuf get /alliances/{alliance_id}/ red {Alliance}
esi-alliances-protobuf get /alliances/{alliance_id}/corporations/ yellow {Alliance}
esi-location-protobuf get /characters/{character_id}/location/ yellow {Location}
esi-location-protobuf get /characters/{character_id}/online/ red {Location}
esi-location-protobuf get /characters/{character_id}/ship/ red {Location}
esi-planets-protobuf get /characters/{character_id}/planets/ red {Planetary Interaction}
esi-planets-protobuf get /characters/{character_id}/planets/{planet_id}/ red {Planetary Interaction}
esi-planets-protobuf get /corporations/{corporation_id}/customs_offices/ red {Planetary Interaction}
esi-status-protobuf get /status/ red {Status}
esi-wars-protobuf get /wars/{war_id}/ red {Wars}
esi-wars-protobuf get /wars/{war_id}/killmails/ red {Wars}
esi-skills-protobuf get /characters/{character_id}/attributes/ red {Skills}
esi-skills-protobuf get /characters/{character_id}/skillqueue/ red {Skills}
esi-skills-protobuf get /characters/{character_id}/skills/ red {Skills}
esi-calendar-protobuf get /characters/{character_id}/calendar/ red {Calendar}
esi-calendar-protobuf get /characters/{character_id}/calendar/{event_id}/ red {Calendar}
esi-corporations-protobuf get /corporations/{corporation_id}/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/alliancehistory/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/blueprints/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/containers/logs/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/divisions/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/medals/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/medals/issued/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/members/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/members/limit/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/members/titles/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/membertracking/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/roles/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/roles/history/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/standings/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/starbases/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/starbases/{starbase_id}/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/structures/ red {Corporation}
esi-corporations-protobuf get /corporations/{corporation_id}/titles/ red {Corporation}
esi-characters-protobuf post /characters/affiliation/ red {Character}
esi-characters-protobuf get /characters/{character_id}/ red {Character}
esi-characters-protobuf get /characters/{character_id}/agents_research/ red {Character}
esi-characters-protobuf get /characters/{character_id}/blueprints/ red {Character}
esi-characters-protobuf get /characters/{character_id}/corporationhistory/ red {Character}
esi-characters-protobuf get /characters/{character_id}/fatigue/ red {Character}
esi-characters-protobuf get /characters/{character_id}/medals/ red {Character}
esi-characters-protobuf get /characters/{character_id}/notifications/ red {Character}
esi-characters-protobuf get /characters/{character_id}/roles/ red {Character}
esi-characters-protobuf get /characters/{character_id}/standings/ red {Character}
esi-characters-protobuf get /characters/{character_id}/titles/ red {Character}
The status endpoint and route (along with others) is red.
Really hope this is just a bug and coincidence and not a sign of removalā¦
When CCP break endpoints, they get removed from the status API (lol) and spec (lol).
ohā¦thats a fabulous system.
The only thing left to break then is the status api of the api itself.
Itās back, soā¦ seems it was.
They dont want everyone to see the massive drop in player count as the end of the month approaches.
The death rattle of Eve.
The REAL problem is the Russia/Ukraine war. Due to sanctions Russian players are unable to sub so CCP wants us players to make up the amount that they are short. That is cheeky to say the least. They should have kept the prices the same and told us the truth about the reason to hike prices by 34% in one go. Why should we have to do that? It is CCPs business judgement of relying on Russian players, it is only their fault and as far as your comment of āgreat more unique players in spaceā CCP would not agree.
Perhaps because a lot of people on these very forums were calling to ban those players just because. Enjoy humble pie.
You lost me there. I did neither of those things and voting with my wallet means I can have a voice in the cash grab debacle.
Well, a good chunk of effort was removing topics on the forum about collective punishment, so now people have to pay for the consequences of their loss. They wanted to reduce the number of players based on nationality or ethnicity out of spite, so, this is the consequence, somebody has to pay to cover the lossā¦
It isnāt the people on the forums that is to blame. I was hoping that the Russian players were being allowed to play, but the international banks made to sanctions and that is why Russian players are stuck. I donāt think for one second that CCP booted players because they are Russian. Probably Russian players are still playing as alphas, but that means that CCP are losing significant amounts of money. If CCP were actively blocking Russian player there wouldnāt be hundreds of then in Russian help.
It would have been if they got their way. The point is that was what many were calling for, and I am highlighting the consequence of such a demand.
Just no. That is not the reason they lost the russian community. The price hike is not a punishment for whatever bullshitery you believe in. Itās still wrong but not THAT wrong.
CCP would never block a player due to player demand. It would be bad business practice and they would lose even more players. They probably sat back and observed but they were overwhelmed by lack of money from Russia. Like I say there are hundreds of players in Russian help, so CCP let them be.
Who knows, they give in to their other demands, remember NFTās?
simply said, no