wzm

[compact pike]

Hey there

Yeah the recommendation here is to cache on your end. It should be decently static data, I agree, and I can look further into why there is latency (may just be something going on right now), but regardless there is no real reason for you to be retrieving this consistently.

[grave cloak]

It's been doing that for a long time, and I only fetch it when onboarding a new downstream account, but it seems like if it's taking 10s, and is publicly reachable, it's likely a DOS concern on your side too.

The cache-control headers are 600s, suggesting you don't want us caching it for very long.

[compact pike]

Gotcha, yeah I think the other option is to just ingest the data yourself. I'll flag internally that the endpoint is slow -- there may be good reason for it as you stated. I don't know too much about the specifics of this endpoint.

[grave cloak]

Thanks!