COVERAGE METHOD / FOUR BOUNDED REFERENCES
Coverage, without the guesswork
Each regional choice supplies a reference clock and the same controlled player-side comparison. It does not claim that a machine in one city represents a country, provider, or continent. Live values stay unavailable until an attributable source record exists.
REGIONAL REGISTER / STATIC RECORDS
Choose the scope, not a result
SAS / published
South Asia
Reference clock: Asia/Kolkata. Results describe the selected method, not every city, provider, or player in South Asia.
SEA / published
Southeast Asia
Reference clock: Asia/Singapore. Results describe the selected method, not every city, provider, or player in Southeast Asia.
EAS / published
East Asia
Reference clock: Asia/Tokyo. Results describe the selected method, not every city, provider, or player in East Asia.
WAS / published
West Asia
Reference clock: Asia/Beirut. IANA rules may change its UTC offset seasonally; results describe one selected method, not a regional measurement.
METHOD LEDGER / CHECKED 2026–07–18
Coverage ledger
| Region record | Reference clock | Method | Live values |
|---|---|---|---|
| South Asiaasia-region-south-asia-v1 | Asia/Kolkata | Player-side route check: verify the exact address and edition, try the same target on the original connection, then compare one alternate connection. Record time and network; do not generalize beyond those attempts. | Unavailableping, route, players · 2026-07-18 |
| Southeast Asiaasia-region-southeast-asia-v1 | Asia/Singapore | Player-side route check: verify the exact address and edition, try the same target on the original connection, then compare one alternate connection. Record time and network; do not generalize beyond those attempts. | Unavailableping, route, players · 2026-07-18 |
| East Asiaasia-region-east-asia-v1 | Asia/Tokyo | Player-side route check: verify the exact address and edition, try the same target on the original connection, then compare one alternate connection. Record time and network; do not generalize beyond those attempts. | Unavailableping, route, players · 2026-07-18 |
| West Asiaasia-region-west-asia-v1 | Asia/Beirut | Player-side route check: verify the exact address and edition, try the same target on the original connection, then compare one alternate connection. Record time and network; do not generalize beyond those attempts. | Unavailableping, route, players · 2026-07-18 |
SCOPE LIMITER / BINDING RULES
What the method can establish
- 01
An exact address plus edition identifies the connection contract before the path is blamed.
- 02
One repeat on the original connection distinguishes a transient attempt from a repeatable local symptom.
- 03
One alternate connection adds a controlled comparison; it still does not represent a region.
- 04
Destination and platform status sources can corroborate a service issue. Their scope stays separate from a player’s route.
The board reports the method and the absence of live inputs separately. An unavailable ping is not zero, and an unavailable route is not evidence of blocking or an outage.