Summary
ASNs ASNs assigned to resource holders registered in this country | 1 |
Countries ASNs assigned to resource holders registered in this country | 1 |
| BGP Prefixes | 1 |
Routers IP addresses belonging to Routers in this country | 53 |
Pingable IPs IP addresses that replied to an ICMP ping | 660 |
- 100%
Important routers in 208.204.0.0/16
| 208.204.9.82 | New York City, United States | AS701Verizon Business |
| 208.204.22.46 | Ashburn, United States | AS701Verizon Business |
| 208.204.18.34 | Sheffield, United States | AS701Verizon Business |
| 208.204.22.9 | Dallas, United States | AS701Verizon Business |
| 208.204.19.98 | Severn, United States | AS701Verizon Business |
| 208.204.24.34 | Boston, United States | AS701Verizon Business |
| 208.204.9.250 | Atlanta, United States | AS701Verizon Business |
| 208.204.24.41 | New York City, United States | AS701Verizon Business |
| 208.204.24.42 | New York City, United States | AS701Verizon Business |
| 208.204.24.130 | Washington, United States | AS701Verizon Business |
Pingable IPs
660 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| 208.204.110.177Ping | AS701Verizon Business | 1.16ms from New York City, Â US |
| 208.204.25.9Ping | AS701Verizon Business | 2.84ms from Chicago, Â US |
| 208.204.21.97Ping | AS701Verizon Business | 0.95ms from Chicago, Â US |
| 208.204.17.33Ping | AS701Verizon Business | 0.46ms from New York City, Â US |
| 208.204.26.89Ping | AS701Verizon Business | 1.91ms from Boston, Â US |
| 208.204.19.121Ping | AS701Verizon Business | 0.70ms from Philadelphia, Â US |
| 208.204.163.225Ping | AS701Verizon Business | 0.44ms from New York City, Â US |
| 208.204.89.57Ping | AS701Verizon Business | 0.95ms from Philadelphia, Â US |
| 208.204.16.41Ping | AS701Verizon Business | 1.18ms from New York City, Â US |
| 208.204.9.253Ping | AS701Verizon Business | 0.88ms from Philadelphia, Â US |
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| 172.215.34.192Ping | AS8075Microsoft Corporation | 0.40ms from Des Moines, Â US |
| 76.21.61.0Ping | AS7922Comcast Cable Communications, LLC | 4.47ms from Fremont, Â US |
| 85.23.76.144Ping | AS16086DNA Oyj | 2.25ms from Helsinki, Â FI |
| 113.254.190.96Ping | AS9304HGC Global Communications Limited | 12.27ms from Hong Kong, Â HK |
| 183.118.25.112Ping | AS4766Korea Telecom | 6.72ms from Incheon, Â KR |
| 39.34.41.144Ping | AS17557Pakistan Telecommunication Company Limited | 2.28ms from Lahore, Â PK |
| 5.252.191.240Ping | AS62240Clouvider | 0.77ms from New York City, Â US |
| 90.84.179.0Ping | AS2280Orange S.A. | 0.35ms from Paris, Â FR |
| 138.124.31.80Ping | AS41745Baykov Ilya Sergeevich | 0.51ms from Paris, Â FR |
| 52.45.140.96Ping | AS14618Amazon.com, Inc. | 0.16ms from Reston, Â 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 -m8 208.204.35.97
traceroute to 208.204.35.97 (208.204.35.97): 8 hops max, 52 byte packets
6Â *
7Â *
8Â *
Measurement taken from 
 IPinfo ProbeNet in Allentown, US
 IPinfo ProbeNet in Allentown, USOnÂ