2a00:8a60::/29
AS47610 · RWTH Aachen University
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 |
Germany
|
| Domain | rwth-aachen.de |
| ASN | AS47610 |
| Registry | RIPE |
| ID | DE-RWTHAACHEN-20150504 |
WHOIS Details
inet6num: 2a00:8a60::/29 netname: DE-RWTHAACHEN-20150504 country: DE org: ORG-RAU1-RIPE admin-c: NN2136-RIPE tech-c: CJV25-RIPE tech-c: NN2136-RIPE status: ALLOCATED-BY-RIR mnt-by: RIPE-NCC-HM-MNT mnt-by: RWTH1-MNT mnt-routes: RWTH1-MNT created: 2018-10-25T15:39:35Z last-modified: 2019-02-14T15:55:05Z source: RIPE abuse-c: AR32014-RIPE abuse-email: abuse@rwth-aachen.de abuse-c: AR32014-RIPE abuse-org: ORG-RAU1-RIPE organisation: ORG-RAU1-RIPE org-name: RWTH Aachen University country: DE org-type: LIR address: Templergraben 55 address: 52056 address: Aachen address: GERMANY phone: +49 241 80 24680 e-mail: lir@itc.rwth-aachen.de admin-c: NN2136-RIPE tech-c: CJV25-RIPE tech-c: NN2136-RIPE tech-c: RLIR1-RIPE abuse-c: AR32014-RIPE mnt-ref: RWTH1-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: RWTH1-MNT mnt-ref: RIPE-NCC-HM-MNT created: 2015-04-29T13:43:42Z last-modified: 2024-09-11T20:48:11Z source: RIPE person: Christoph Viethen address: RWTH Aachen address: IT Center address: Wendlingweg 10 address: 52074 Aachen address: Germany phone: +49 241 80 29204 e-mail: viethen@itc.rwth-aachen.de nic-hdl: CJV25-RIPE mnt-by: RWTH1-MNT created: 2015-04-29T14:44:54Z last-modified: 2015-04-29T14:56:55Z source: RIPE person: Nils Neumann address: RWTH Aachen address: IT Center address: Wendlingweg 10 address: 52074 Aachen address: Germany phone: +49 241 80 29214 nic-hdl: NN2136-RIPE mnt-by: RWTH1-MNT created: 2015-04-29T13:43:41Z last-modified: 2015-04-29T15:21:02Z source: RIPE route6: 2a00:8a60::/29 descr: ACHSEv6 origin: AS47610 mnt-by: RWTH1-MNT created: 2018-10-26T14:46:14Z last-modified: 2018-10-26T14:48:17Z source: RIPE
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
10,351 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 2a00:8a60:101b::1:21 |
4.22ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:5200::329:71 |
4.26ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:1:c635:1000::6 |
4.07ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:1031::1 |
4.33ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:1013:1::1 |
4.46ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:2001::1 |
4.55ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4300::30:65 |
4.24ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4::1 |
4.37ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:e019:f0::2 |
4.22ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4206::1 |
4.52ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:6::1 |
4.61ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:453:1::1 |
4.14ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4a3::1:1 |
4.31ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4501:11::1 |
4.30ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:3200::43:75 |
4.22ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:e022:f0::2 |
4.24ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:1010:f0::1 |
4.53ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:450::1 |
4.15ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:3103::1 |
4.47ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:5303::1 |
4.41ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:2007::1 |
4.53ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4100:100::1 |
4.46ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4003::1 |
4.56ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:5304:1::1 |
4.44ms from Frankfurt am Main,
DE
|
|
| 2a00:8a60:4205:1::1 |
4.35ms from Frankfurt am Main,
DE
|
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 |
|---|---|---|
| 1.158.206.45 |
9.54ms from Adelaide,
AU
|
|
| 18.206.56.45 |
0.45ms from Ashburn,
US
|
|
| 204.6.192.253 |
0.43ms from Ashburn,
US
|
|
| 65.101.64.125 |
8.10ms from Ashburn,
US
|
|
| 162.17.201.125 |
8.83ms from Ashburn,
US
|
|
| 20.75.176.109 |
0.46ms from Ashburn,
US
|
|
| 134.164.233.189 |
0.62ms from Atlanta,
US
|
|
| 24.30.21.45 |
4.95ms from Atlanta,
US
|
|
| 182.95.99.109 |
0.65ms from Bengaluru,
IN
|
|
| 72.22.130.61 |
2.91ms from Bridgetown,
BB
|
|
| 188.6.18.253 |
2.88ms from Budapest,
HU
|
|
| 71.75.106.13 |
10.92ms from Charlotte,
US
|
|
| 151.74.255.125 |
6.85ms from Crotone,
IT
|
|
| 87.167.165.141 |
9.60ms from Frankfurt am Main,
DE
|
|
| 139.159.200.237 |
1.71ms from Guangzhou,
CN
|
|
| 223.226.173.93 |
11.23ms from Kolkata,
IN
|
|
| 180.73.84.173 |
1.66ms from Kuala Lumpur,
MY
|
|
| 86.128.138.173 |
6.47ms from London,
GB
|
|
| 212.241.198.29 |
0.45ms from London,
GB
|
|
| 58.122.81.29 |
1.83ms from Seoul,
KR
|
|
| 60.19.64.157 |
2.52ms from Tieling,
CN
|
|
| 196.184.84.221 |
12.26ms from Tunis,
TN
|
|
| 20.85.233.157 |
0.40ms from Ashburn,
US
|
|
| 102.40.145.93 |
2.65ms from Cairo,
EG
|
|
| 83.70.71.61 |
1.43ms from Dublin,
IE
|
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 tools
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs