Summary
ASNs ASNs assigned to resource holders registered in this country | 3 |
Countries ASNs assigned to resource holders registered in this country | 1 |
| BGP Prefixes | 6 |
Routers IP addresses belonging to Routers in this country | 57 |
Pingable IPs IP addresses that replied to an ICMP ping | 403 |
- 100%
Important routers in 199.222.0.0/16
| 199.222.8.70 | San Jose, United States | AS701Verizon Business |
| 199.222.6.178 | Phoenix, United States | AS701Verizon Business |
| 199.222.18.10 | Ashburn, United States | AS701Verizon Business |
| 199.222.2.82 | Miami, United States | AS701Verizon Business |
| 199.222.5.154 | Chicago, United States | AS701Verizon Business |
| 199.222.41.50 | Atlanta, United States | AS701Verizon Business |
| 199.222.19.54 | Philadelphia, United States | AS701Verizon Business |
| 199.222.16.4 | Dallas, United States | AS701Verizon Business |
| 199.222.1.158 | Philadelphia, United States | AS701Verizon Business |
| 199.222.0.150 | Philadelphia, United States | AS701Verizon Business |
Pingable IPs
403 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| 199.222.3.113Ping | AS701Verizon Business | 0.71ms from Philadelphia, Â US |
| 199.222.4.81Ping | AS701Verizon Business | 0.69ms from Philadelphia, Â US |
| 199.222.20.1Ping | AS701Verizon Business | 1.45ms from Ashburn, Â US |
| 199.222.37.52Ping | AS701Verizon Business | 18.47ms from Philadelphia, Â US |
| 199.222.5.201Ping | AS701Verizon Business | 0.80ms from New York City, Â US |
| 199.222.2.145Ping | AS701Verizon Business | 0.84ms from New York City, Â US |
| 199.222.6.25Ping | AS701Verizon Business | 0.75ms from Philadelphia, Â US |
| 199.222.16.225Ping | AS701Verizon Business | 0.44ms from New York City, Â US |
| 199.222.32.193Ping | AS701Verizon Business | 2.92ms from New York City, Â US |
| 199.222.9.57Ping | AS701Verizon Business | 0.80ms from Portland, Â US |
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| 197.60.44.16Ping | AS8452TE-AS | 5.03ms from Cairo, Â EG |
| 173.191.153.80Ping | AS7029Windstream Communications LLC | 8.92ms from Dallas, Â US |
| 52.173.86.16Ping | AS8075Microsoft Corporation | 0.37ms from Des Moines, Â US |
| 178.76.155.128Ping | AS42652inexio Informationstechnologie und Telekommunikation Gmbh | 11.74ms from Frankfurt am Main, Â DE |
| 24.130.125.128Ping | AS7922Comcast Cable Communications, LLC | 6.71ms from Fremont, Â US |
| 93.209.144.16Ping | AS3320Deutsche Telekom AG | 4.46ms from Hamburg, Â DE |
| 125.243.225.144Ping | AS9316DACOM-PUBNETPLUS | 1.74ms from Incheon, Â KR |
| 20.200.52.160Ping | AS8075Microsoft Corporation | 0.17ms from Quebec, Â CA |
| 13.56.238.240Ping | AS16509Amazon.com, Inc. | 0.72ms from San Jose, Â US |
| 47.208.251.96Ping | AS19108Optimum | 9.94ms from San Jose, Â US |
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.Traceroute →
$ traceroute -a -n -q1 -f2 -m9 199.222.66.107
traceroute to 199.222.66.107 (199.222.66.107): 9 hops max, 52 byte packets
7Â *
8Â *
9Â *
Measurement taken from 
 IPinfo ProbeNet in Detroit, US
 IPinfo ProbeNet in Detroit, USOnÂ