[2023] ESI Characters Corporation History

Hey everyone!

I’ve been advised that this afternoon we’ve temporarily taken down one of the ESI endpoints:

esi-characters/{character_id}/corporationhistory/" is the exact endpoint.

• Routes will return empty lists rather than corporation history once the request cache has expired
• This affects all versions of the endpoint: legacy, dev, latest, v1 and v2

• Before this weekend, the average number of daily requests was around 50k per hour, however, it has been spiking to 3 million per hour.

Similar to the issue we had towards the end of the year with the Market endpoint, it seems that these requests are also coming from AWS, so banning the offending IPs won’t resolve the issue. Until the endpoint can be protected better, it will be taken offline.

As per the Market endpoints post, once I’m advised of any further developers on this I’ll relay them into this thread.

We don’t believe it’s intended to be malicious, it’s more than likely an errant third-party dev miscoded something causing it to increase the number of calls. It appears the issue started on Saturday 7 Jan at 18:13 UTC, so if you’re a budding developer that was developing something new around that time, it may be worth checking into!

We aren’t looking to punish the individual responsible for the uptick in requests, but if we do discover the individual that may have accidentally caused the issue, they’re welcome to drop me a message. I can pass that along to the development team to see if we can restore the service before the additional work is put into reinforcing the endpoint.

Hey folks!

During downtime yesterday an update to the Corp History ESI endpoint was put into place, then an hour or so later the service was re-activated and it started caching again. The caching process should be finished around 1200 UTC today so this endpoint should once again be fully operational after this point. In terms of adjusting any existing services that are utilizing this endpoint, please be aware that it now has the same limitations as the Market History ESI endpoint which, just as a reminder is:

• The endpoint is tentatively limited to 300 requests per minute per IP address. The rate limit is subject to review at any time, and we will update according if and when a change is made such that all third-party developers can adjust their apps accordingly.
• When the rate limit is exceeded, users can expect an HTTP 500 error with the original error in the reason text

As always, should anything change in the future, I’ll endeavor to make sure it gets communicated in this section of the forum again.