Service Status & Health

Grid Identity & Bounds

Coverage Details

Live round-trip response times measured directly from your browser:

The hexagon row is the worst case: a whole Res 8 viewport in one request, which is what the map used to ask for on every pan. It now asks for the tile row instead — small, fixed boxes cached for a year — so a warm pan makes no request at all. Each row splits its round trip into the service’s own time and everything else — distance, TLS and the download — so a slow deployment can be told apart from a distant one.

Resolution Ladder Diagnostics

Every level the grid defines, Res 0 to Res 14. The map only offers Res 0–8, so this table is the one place the finer end is visible — but those levels are real and callable: /v1/index with res=12 returns a valid cell today. They are marked finer than base because this deployment standardises on Res 8, and a cell finer than the data behind it asserts an accuracy the input does not have.

Kingdom counts are land area ÷ cell area, not an enumeration — nobody enumerates 22 trillion cells to fill a table. The equal-area projection makes that division exact to within the boundary's own accuracy.