sin location. It would be really nice if there was more information exposed in Tigris’s response headers (edge location hit, storage location retrieved from) for debugging. Based on the latency (~250 ms) even after a few requests to a 10 KB object, I assume I’m going somewhere else. I do ~1‑2 ms when ICMP pinging the Tigris endpoint directly.x-tigris-regions header, and I see some curious information being returned sometimes:sin?_mr?sin comes back?_mr mean?*_mr value reported in the x-tigris-regions header, that is something internal and should not have been reported in the header value. We will fix that.