Hello there!
Just wanted to let you know SeAT is still using a route that has been deprecated for a while, and is now being removed next month. For more details, please see this blog:
https://developers.eveonline.com/blog/spring-cleaning-legacy-routes-removed-24-march-2026
The specific URL SeAT is still using is /status.json here.
This route is replaced by a newer route, now part of the official API. If you like, you can migrate to that new route.
Alternatively, you can also just apply a back-off (and not check the health-status): if the route fails, wait 1s. If it still fails, 2s, 5s, up to some cap. That, for us, is also perfectly fine. But of course what you are doing is not wrong :)
If we can assist, please don't hesitate to reach out!
Hello there!
Just wanted to let you know SeAT is still using a route that has been deprecated for a while, and is now being removed next month. For more details, please see this blog:
https://developers.eveonline.com/blog/spring-cleaning-legacy-routes-removed-24-march-2026
The specific URL SeAT is still using is
/status.jsonhere.This route is replaced by a newer route, now part of the official API. If you like, you can migrate to that new route.
Alternatively, you can also just apply a back-off (and not check the health-status): if the route fails, wait 1s. If it still fails, 2s, 5s, up to some cap. That, for us, is also perfectly fine. But of course what you are doing is not wrong :)
If we can assist, please don't hesitate to reach out!