Router Naming Convention for nitelusa.net

Regular Expressions:

1.^[a-z]+-[^\.]+\..+\.([a-z]{3})\d+\.([a-z]{2})\.nitelusa\.net$ -- iata, cc -- 80 TPs

Statistics:

Legend:

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

Geocodes:

Hint Location Closest VP
atl|usAtlanta, GA, US atl2-us4ms
chi|usChicago, IL, US ord-us2ms
dal|usDallas, TX, US okc-us8ms
den|usDenver, CO, US wbu-us2ms
lax|usLos Angeles, CA, US lax3-us2ms
mia|usMiami, FL, US mia-gc2ms
nyc|usNew York, NY, US jfk-us1ms
sea|usSeattle, WA, US bfi-us3ms

Evaluation against training data:

mia|us: mia-gc 2ms, id 18330
207.200.195.26+[1]be-1.cr1.mia1.us.nitelusa.net
198.32.242.23+[1]equinix-miami.te-0-1-0-2.cr1.mia1.us.nitelusa.net
207.200.195.21+[1]te-0-0-0-1.cr1.mia1.us.nitelusa.net
207.200.195.24+[1]te-0-1-0-1.cr1.mia1.us.nitelusa.net
157.238.226.233xe-0-5-3-3.a02.miamfl02.us.ce.gin.ntt.net
 
mia|us: mia-gc 2ms, id 42921
207.200.195.27+[1]be-1.cr2.mia1.us.nitelusa.net
206.41.108.192~[1]fl-ix.te-0-1-0-2.cr2.mia1.us.nitelusa.net
207.200.195.23+[1]te-0-0-0-1.cr2.mia1.us.nitelusa.net
 
atl|us: atl2-us 4ms, id 46966581
207.200.192.217+[1]ge-0-0-0.ar4.atl1.us.nitelusa.net
 
atl|us: atl2-us 5ms, id 100172
207.200.192.221+[1]ge-0-0-0.ar5.atl1.us.nitelusa.net
207.200.192.223+[1]ge-0-0-1.ar5.atl1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 16496
208.115.136.220~g-0-1-1-0.ar2.chi1.nitelusa.net
64.63.129.113+[1]te-0-0-1-1.cr1.chi1.us.nitelusa.net
207.200.195.65+[1]te-0-1-1-5.cr1.chi1.us.nitelusa.net
207.200.195.93+[1]te-0-1-1-7.cr1.chi1.us.nitelusa.net
128.241.1.222xe-3-5-0-0.a06.chcgil09.us.ce.gin.ntt.net
 
dal|us: okc-us 9ms, id 17988
207.200.195.73+[1]te-0-0-1-1.cr1.dal1.us.nitelusa.net
207.200.195.101+[1]te-0-0-1-6.cr1.dal1.us.nitelusa.net
207.200.195.66+[1]te-0-1-1-2.cr1.dal1.us.nitelusa.net
207.200.195.141+[1]te-0-1-1-7.cr1.dal1.us.nitelusa.net
128.241.1.202xe-1-4-3-1.a01.dllstx14.us.ce.gin.ntt.net
 
nyc|us: jfk-us 1ms, id 12733
64.63.129.114+[1]te-0-0-1-1.cr1.nyc1.us.nitelusa.net
207.200.195.5+[1]te-0-0-1-7.cr1.nyc1.us.nitelusa.net
207.200.195.20+[1]te-0-2-0-4.cr1.nyc1.us.nitelusa.net
128.241.1.178xe-0-0-14-2.a00.nycmny13.us.ce.gin.ntt.net
206.126.115.72
207.200.195.1
 
sea|us: bfi-us 4ms, id 1413091
207.200.195.206+[1]te-0-0-1-1.cr1.sea1.us.nitelusa.net
 
atl|us: atl2-us 5ms, id 16703
207.200.195.34+[1]te-0-0-1-1.cr2.atl1.us.nitelusa.net
207.200.195.10+[1]te-0-0-1-7.cr2.atl1.us.nitelusa.net
207.200.195.14+[1]te-0-1-1-7.cr2.atl1.us.nitelusa.net
207.200.195.22+[1]te-0-2-0-13.cr2.atl1.us.nitelusa.net
69.174.20.78ip4.gtt.net
 
chi|us: ord-us 2ms, id 16702
207.200.195.69+[1]te-0-0-1-1.cr2.chi1.us.nitelusa.net
207.200.195.90+[1]te-0-0-1-7.cr2.chi1.us.nitelusa.net
207.200.195.33+[1]te-0-1-1-1.cr2.chi1.us.nitelusa.net
69.174.20.46ip4.gtt.net
206.41.110.93
 
lax|us: lax3-us 3ms, id 23247
207.200.195.74+[1]te-0-0-1-1.cr2.lax1.us.nitelusa.net
207.200.195.213+[1]te-0-1-1-1.cr2.lax1.us.nitelusa.net
207.200.195.82+[1]te-0-1-1-7.cr2.lax1.us.nitelusa.net
69.174.20.38ip4.gtt.net
 
nyc|us: jfk-us 1ms, id 1414694
207.200.195.190+[1]te-0-0-1-1.cr2.nyc1.us.nitelusa.net
 
den|us: wbu-us 2ms, id 12879
207.200.195.70+[1]te-0-0-1-2.cr1.den1.us.nitelusa.net
207.200.195.77+[1]te-0-0-1-3.cr1.den1.us.nitelusa.net
207.200.195.210+[1]te-0-1-1-1.cr1.den1.us.nitelusa.net
207.200.195.205+[1]te-0-1-1-2.cr1.den1.us.nitelusa.net
206.51.46.63206.51.46.63.any2ix.coresite.com
69.174.20.94ip4.gtt.net
 
dal|us: okc-us 8ms, id 10249
207.200.195.209+[1]te-0-0-1-2.cr2.dal1.us.nitelusa.net
207.200.195.102+[1]te-0-0-1-7.cr2.dal1.us.nitelusa.net
207.200.195.98+[1]te-0-1-1-2.cr2.dal1.us.nitelusa.net
207.200.195.142+[1]te-0-1-1-7.cr2.dal1.us.nitelusa.net
207.200.195.25+[1]te-0-2-0-17.cr2.dal1.us.nitelusa.net
206.53.202.141~te-2-0-13.cr1.dal1.nitelusa.net
69.174.20.66ip4.gtt.net
 
atl|us: atl2-us 4ms, id 13839
207.200.195.97+[1]te-0-0-1-4.cr1.atl1.us.nitelusa.net
207.200.195.9+[1]te-0-0-1-7.cr1.atl1.us.nitelusa.net
207.200.195.189+[1]te-0-1-1-2.cr1.atl1.us.nitelusa.net
207.200.195.13+[1]te-0-1-1-7.cr1.atl1.us.nitelusa.net
128.241.3.234xe-2-4-0-1.a02.atlnga05.us.ce.gin.ntt.net
198.32.132.155
 
chi|us: ord-us 3ms, id 1413094
207.200.195.89+[1]te-0-0-1-6.cr1.chi1.us.nitelusa.net
 
lax|us: lax3-us 2ms, id 13842
207.200.195.29+[1]te-0-0-1-7.cr1.lax1.us.nitelusa.net
207.200.195.225+[1]te-0-1-1-0.cr1.lax1.us.nitelusa.net
207.200.195.78+[1]te-0-1-1-5.cr1.lax1.us.nitelusa.net
207.200.195.81+[1]te-0-1-1-7.cr1.lax1.us.nitelusa.net
206.72.211.67network-innovations.as53828.any2ix.coresite.com
128.241.219.158xe-2-5-2-1.a04.lsanca07.us.ce.gin.ntt.net
 
lax|us: lax3-us 3ms, id 1413085
207.200.195.30+[1]te-0-0-1-7.cr2.lax1.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 1413087
207.200.195.6+[1]te-0-0-1-7.cr2.nyc1.us.nitelusa.net
 
dal|us: okc-us 9ms, id 6714117
207.200.195.113+[1]te-0-0-24.ear1.dal1.us.nitelusa.net
 
den|us: wbu-us 3ms, id 3280605
64.63.129.158+[1]te-0-0-24.ear1.den1.us.nitelusa.net
 
lax|us: lax3-us 3ms, id 3280604
207.200.195.49+[1]te-0-0-24.ear1.lax1.us.nitelusa.net
 
sea|us: bfi-us 4ms, id 8814072
207.200.195.154+[1]te-0-0-24.ear1.sea1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 3280593
64.63.129.46+[1]te-0-0-24.ear2.chi1.us.nitelusa.net
 
den|us: wbu-us 3ms, id 3280606
64.63.129.162+[1]te-0-0-24.ear2.den1.us.nitelusa.net
 
lax|us: lax3-us 3ms, id 7257693
64.63.129.137+[1]te-0-0-24.ear2.lax1.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 3280588
64.63.129.22+[1]te-0-0-24.ear2.nyc1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 8814053
64.63.129.50+[1]te-0-0-24.ear3.chi1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 3280594
64.63.129.66+[1]te-0-0-24.ear3.chi2.us.nitelusa.net
 
den|us: wbu-us 3ms, id 3280607
64.63.129.166+[1]te-0-0-24.ear3.den1.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 3280589
64.63.129.26+[1]te-0-0-24.ear3.nyc1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 3280595
64.63.129.70+[1]te-0-0-24.ear4.chi2.us.nitelusa.net
 
den|us: wbu-us 3ms, id 45231664
64.63.129.170+[1]te-0-0-24.ear4.den1.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 3280590
64.63.129.30+[1]te-0-0-24.ear4.nyc1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 46966583
207.200.195.250+[1]te-0-0-24.ear5.chi1.us.nitelusa.net
 
chi|us: ord-us 4ms, id 3280596
64.63.129.75+[1]te-0-0-24.ear5.chi2.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 3381363
64.63.129.34+[1]te-0-0-24.ear5.nyc1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 3280597
64.63.129.85+[1]te-0-0-24.ear6.chi2.us.nitelusa.net
 
atl|us: atl2-us 7ms, id 8814065
64.63.129.218+[1]te-0-0-25.ear1.atl1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 45231663
64.63.129.41+[1]te-0-0-25.ear1.chi2.us.nitelusa.net
 
nyc|us: jfk-us 2ms, id 3280587
64.63.129.190+[1]te-0-0-25.ear1.nyc1.us.nitelusa.net
 
atl|us: atl2-us 6ms, id 3374444
207.200.195.230+[1]te-0-0-26.ear2.atl1.us.nitelusa.net
 
chi|us: ord-us 3ms, id 3280591
64.63.129.90+[1]te-0-0-26.ear2.chi2.us.nitelusa.net
 
sea|us: bfi-us 3ms, id 1413092
207.200.195.214+[1]te-0-1-1-1.cr1.sea1.us.nitelusa.net
 
nyc|us: jfk-us 1ms, id 42946
207.200.195.224+[1]te-0-1-1-4.cr2.nyc1.us.nitelusa.net
206.82.104.21+[1]te-0-2-0-11.cr2.nyc1.us.nitelusa.net
207.200.195.2
 
chi|us: ord-us 3ms, id 934622
207.200.195.94+[1]te-0-1-1-7.cr2.chi1.us.nitelusa.net
 
lax|us: lax3-us 2ms, id 8814033
207.200.195.54+[1]te-0-2.esw2.lax1.us.nitelusa.net
 
okc-us 8ms, id 1414698
206.223.118.221~te-0-5-1-0.ar2.dal1.nitelusa.net
 
ord-us 4ms, id 3280603
64.63.129.106 g-0-3.e1.350norleans.nitelusa.net
 
ord-us 3ms, id 46966582
207.200.193.196 vpn.nitelusa.net