Round-trip times are measured by your browser against each hosting location every 30 seconds. That is the same path a visitor's first request takes before the CDN answers from cache.
last check — · refresh in 30s · refresh now
| Location | City | Region | Role | Latency | Jitter | Loss | Status |
|---|---|---|---|---|---|---|---|
| KR-Chuncheon-01 | Chuncheon | KR | Primary hosting | — | — | — | Checking |
| KR-Seoul-01 | Seoul | KR | Primary hosting | — | — | — | Checking |
| KR-Seoul-02 | Seoul | KR | Secondary / DR | — | — | — | Checking |
| KR-Seoul-03 | Seoul | KR | Edge cache | — | — | — | Checking |
| KR-Busan-01 | Busan | KR | Edge cache | — | — | — | Checking |
| KR-Incheon-01 | Incheon | KR | Edge cache | — | — | — | Checking |
| KR-Daegu-01 | Daegu | KR | Edge cache | — | — | — | Checking |
| KR-Daejeon-01 | Daejeon | KR | Edge cache | — | — | — | Checking |
| JP-Tokyo-01 | Tokyo | JP | Primary hosting | — | — | — | Checking |
| JP-Tokyo-02 | Tokyo | JP | Secondary / DR | — | — | — | Checking |
| JP-Yokohama-01 | Yokohama | JP | Edge cache | — | — | — | Checking |
| JP-Osaka-01 | Osaka | JP | Edge cache | — | — | — | Checking |
| JP-Nagoya-01 | Nagoya | JP | Edge cache | — | — | — | Checking |
| JP-Fukuoka-01 | Fukuoka | JP | Edge cache | — | — | — | Checking |
| HK-KwaiChung-01 | Hong Kong | HK | Edge cache | — | — | — | Checking |
| HK-TseungKwanO-02 | Hong Kong | HK | Edge cache | — | — | — | Checking |
| HK-ChaiWan-03 | Hong Kong | HK | Edge cache | — | — | — | Checking |
| SG-TaiSeng-01 | Singapore | SG | Edge cache | — | — | — | Checking |
| SG-Jurong-02 | Singapore | SG | Edge cache | — | — | — | Checking |
03:12–04:06 UTC. A configuration push left one cache node with a stale rule set, so updated pages took up to six minutes to appear. Six client sites were affected. Root cause: a deploy script skipped a validation step on one node.
18:40–19:15 UTC. A new rule blocked legitimate form submissions containing a Unicode sequence from a client's RFQ page. Rule reverted at 19:15; the form traffic was replayed from logs.
Rolling renewal across 19 hosting locations, one at a time. No measurable interruption; two locations renegotiated sessions twice.