| 1. | ^[a-z\d]+-[^\.]+\.[^\.]+\.([a-z]{3})\d+\.([a-z]{2})\.[a-z]+-ntwk\.cl\.network$ | -- iata, cc | -- 19 TPs |
| Bold | Apparent custom geocode | |
Green |
+ | Extracted apparent geocode, true positive when evaluated against training data |
Orange |
~ | False negative, apparent geocode unmatched |
Purple |
? | Extracted geocode, but not in dictionary |
Red |
! | Extracted apparent geocode, false positive when evaluated against training data |
| Hint | Location | Closest VP | |
| syd|au | Sydney, NSW, AU | syd3-au | 100ms |
| tor|ca | Toronto, ON, CA | jfk-us | 91ms |
| can|cn | Guangzhou (Huadu), 44, CN | cjj-kr | 48ms |
| hkg|cn | Hong Kong, HK | cjj-kr | 46ms |
| sha|cn | Shanghai, 31, CN | nrt-jp | 34ms |
| fra|de | Frankfurt am Main, HE, DE | fra-gc | 1ms |
| gum|gu | Hagatna, Guam International Airport, GU | nrt3-jp | 32ms |
| tyo|jp | Tokyo / Narita, 12, JP | nrt-jp | 2ms |
| icn|kr | Seoul, 28, KR | cjj-kr | 4ms |
| mow|ru | Moscow, MOS, RU | fra-gc | 39ms |
| sin|sg | Singapore, 04, SG | hnd-jp | 71ms |
| sea|us | Seattle, WA, US | nrt3-jp | 96ms |
| sha|cn: nrt-jp 34ms, id 3936986 | |||
| 202.144.198.52 | + | [1] | ae0-1.r02.sha03.cn.asia-ntwk.cl.network |
| gum|gu: nrt3-jp 32ms, id 8662160 | |||
| 202.144.198.216 | + | [1] | ae1-0.r01.gum01.gu.oa-ntwk.cl.network |
| syd|au: syd3-au 100ms, id 8662196 | |||
| 202.144.198.113 | + | [1] | ae1-0.r01.syd01.au.oa-ntwk.cl.network |
| tyo|jp: nrt3-jp 3ms, id 561633 | |||
| 202.144.198.7 | + | [1] | ae5-0.r01.tyo05.jp.asia-ntwk.cl.network |
| icn|kr: swu-kr 8ms, id 8662198 | |||
| 202.144.198.206 | + | [1] | ae6-0.r01.icn01.kr.asia-ntwk.cl.network |
| tyo|jp: nrt3-jp 3ms, id 8662152 | |||
| 202.144.198.22 | + | [1] | ae6-0.r02.tyo05.jp.asia-ntwk.cl.network |
| hkg|cn: cjj-kr 46ms, id 8662177 | |||
| 202.144.198.29 | + | [1] | ae6-0.r03.hkg01.cn.asia-ntwk.cl.network |
| fra|de: fra-gc 1ms, id 8662174 | |||
| 202.144.198.160 | + | [1] | ae7-0.r01.fra05.de.europe-ntwk.cl.network |
| tyo|jp: nrt-jp 2ms, id 46916674 | |||
| 202.144.198.139 | + | [1] | ae7-0.r03.tyo02.jp.asia-ntwk.cl.network |
| sha|cn: nrt3-jp 35ms, id 8662161 | |||
| 202.144.198.180 | + | [1] | ae9-0.r01.sha03.cn.asia-ntwk.cl.network |
| fra|de: fra-gc 2ms, id 46916673 | |||
| 202.144.198.127 | + | [1] | ge2-0-3-0.vrf-stsr.fra09.de.europe-ntwk.cl.network |
| sha|cn: cjj-kr 54ms, id 46916675 | |||
| 202.144.198.218 | + | [1] | xe-1-0-7-0.r01.sha09.cn.asia-ntwk.cl.network |
| mow|ru: fra-gc 39ms, id 46916672 | |||
| 202.144.198.123 | + | [1] | xe-2-0-0-0.r01.mow01.ru.europe-ntwk.cl.network |
| tor|ca: jfk-us 91ms, id 8662187 | |||
| 202.144.198.116 | + | [1] | xe-2-0-5-0.r01.tor01.ca.na-ntwk.cl.network |
| icn|kr: cjj-kr 4ms, id 8662159 | |||
| 202.144.198.203 | + | [1] | xe-2-0-6-1.r01.icn03.kr.asia-ntwk.cl.network |
| fra|de: fra-gc 1ms, id 8662175 | |||
| 202.144.198.9 | + | [1] | xe-3-0-1-0.r02.fra05.de.europe-ntwk.cl.network |
| sin|sg: hnd-jp 71ms, id 8662158 | |||
| 202.144.198.201 | + | [1] | xe-3-0-5-1.r01.sin02.sg.asia-ntwk.cl.network |
| sea|us: nrt3-jp 96ms, id 8662157 | |||
| 202.144.198.196 | + | [1] | xe-6-0-3-0.r01.sea01.us.na-ntwk.cl.network |
| can|cn: cjj-kr 48ms, id 7770917 | |||
| 202.144.198.67 | + | [1] | xe-6-2-0-0.r01.can01.cn.asia-ntwk.cl.network |