2a0b:3080::/32
AS206516 · ProRail B.V.
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
Netherlands
|
| Domain | prorail.nl |
| ASN | AS206516 |
| Registry | RIPE |
| ID | NL-PRORAIL-20170103 |
WHOIS Details
inet6num: 2a0b:3080::/32 netname: NL-PRORAIL-20170103 country: NL org: ORG-PB123-RIPE admin-c: NLPR1-RIPE tech-c: NLPR1-RIPE status: ALLOCATED-BY-RIR mnt-by: RIPE-NCC-HM-MNT mnt-by: PRORAIL-MNT created: 2017-01-03T09:31:56Z last-modified: 2017-01-03T09:31:56Z source: RIPE abuse-email: abuse@prorail.nl abuse-c: NLPR4-RIPE abuse-org: ORG-PB123-RIPE organisation: ORG-PB123-RIPE org-name: ProRail B.V. country: NL org-type: LIR address: Moreelsepark 3 address: 3511EP address: Utrecht address: NETHERLANDS phone: +31882312600 e-mail: ict.netwerk@prorail.nl admin-c: NLPR1-RIPE tech-c: NLPR1-RIPE abuse-c: NLPR4-RIPE mnt-ref: PRORAIL-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: PRORAIL-MNT created: 2016-12-29T14:34:19Z last-modified: 2024-12-18T10:27:40Z source: RIPE role: ProRail BV - Role Object org: ORG-PB123-RIPE address: Moreelsepark 3 address: 3511EP address: Utrecht address: NETHERLANDS phone: +31882312600 e-mail: ict.netwerk@prorail.nl admin-c: NLPR3-RIPE tech-c: NLPR2-RIPE nic-hdl: NLPR1-RIPE mnt-by: PRORAIL-MNT created: 2017-01-02T13:35:26Z last-modified: 2025-01-27T09:09:10Z source: RIPE route6: 2a0b:3080::/32 origin: AS206516 mnt-by: PRORAIL-MNT created: 2021-07-14T04:45:12Z last-modified: 2021-07-14T04:45:12Z source: RIPE
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
No IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 97.149.40.0 |
14.04ms from Chicago,
US
|
|
| 108.87.16.0 |
8.64ms from Chicago,
US
|
|
| 217.253.150.176 |
7.19ms from Frankfurt am Main,
DE
|
|
| 34.111.98.128 |
0.07ms from Melbourne,
AU
|
|
| 178.205.139.144 |
14.21ms from Moscow,
RU
|
|
| 95.54.197.160 |
17.01ms from Saint Petersburg,
RU
|
|
| 124.153.169.0 |
8.11ms from Seoul,
KR
|
|
| 211.73.188.224 |
3.43ms from Taipei,
TW
|
|
| 154.119.175.208 |
11.18ms from Cape Town,
ZA
|
|
| 108.60.209.64 |
2.02ms from Dallas,
US
|
|
| 212.64.199.16 |
0.43ms from Istanbul,
TR
|
|
| 51.211.113.16 |
1.35ms from Jeddah,
SA
|
|
| 61.179.132.144 |
2.43ms from Jinan,
CN
|
|
| 2.115.93.176 |
8.72ms from Milan,
IT
|
|
| 138.197.72.224 |
0.30ms from New York City,
US
|
|
| 37.193.193.208 |
1.22ms from Novosibirsk,
RU
|
|
| 191.178.44.128 |
11.93ms from Rio de Janeiro,
BR
|
|
| 20.140.61.80 |
1.50ms from San Antonio,
US
|
|
| 175.239.152.240 |
5.51ms from Seoul,
KR
|
|
| 118.218.26.64 |
6.09ms from Seoul,
KR
|
|
| 113.227.167.224 |
7.10ms from Tieling,
CN
|
|
| 153.172.229.192 |
3.50ms from Tokyo,
JP
|
|
| 74.235.195.192 |
0.48ms from Ashburn,
US
|
|
| 15.205.7.144 |
0.51ms from Boardman,
US
|
|
| 116.205.246.144 |
1.63ms from Guangzhou,
CN
|
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all toolsSummarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs