2a0d:3dc1:ca97::/48
AS210312 · BGP Clock
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 |
Switzerland
|
| Domain | daknob.net |
| ASN | AS210312 |
| Registry | RIPE |
| ID | DNET-RESEARCH-BGP-CLOCK |
WHOIS Details
inet6num: 2a0d:3dc1::/32
netname: DNET-RESEARCH-BGP-CLOCK
descr: DaKnObNET - Research - BGP Clock
remarks: The BGP Clock
remarks:
remarks: Every 10' the prefix 2a0d:3dc1:XXXX::/48 is advertised. The
remarks: XXXX is the number of 10' periods since the beginning of the
remarks: year. So Jan 1 00:00 is :0000:, Jan 1 00:10 is :0001:, etc.
remarks: Notice that it starts from 0 and not 1, as it should ;)
remarks:
remarks: Only one /48 should be available at any single time, which
remarks: means that they should only be visible for 10' in the global
remarks: RIB per year.
remarks:
remarks: Why? We are conducting research on BGP Stuck Routes to better
remarks: understand how they happen, when, which equipment is more
remarks: buggy, etc. We also want to understand them better. As this is
remarks: a beacon, anyone can study the results using RIPE RIS, or any
remarks: other source like RouteViews. Feel free to take a look and let
remarks: everyone know if something interesting ever comes up!
remarks:
remarks: An example of research presented at RIPE 89 & 91 is here:
remarks: https://ripe89.ripe.net/wp-content/uploads/presentations/8-BGP-Zombies-RIPE89.pdf
remarks: https://ripe91.ripe.net/programme/meeting-plan/sessions/19/87WNTB/
remarks:
remarks: On 2025-11-17 11:40-12:00 UTC there was a change from origin
remarks: AS4601 to AS210312 with ROA and route{6,} object changes.
remarks:
remarks: We are also studying the propagation of BGP Communities with
remarks: this beacon, to minimize the count of BGP UPDATEs generated.
remarks: At origin, all prefixes are tagged with the following values:
remarks:
remarks: BGP Legacy Communities:
remarks: (4492, 64700)
remarks: (4601, 64700)
remarks:
remarks: BGP Extended Communities:
remarks: (ro, 4492, 1337)
remarks: (ro, 4601, 1337)
remarks: (ro, 210312, 1337)
remarks:
remarks: BGP Large Communities:
remarks: (4492, 64700, 1337)
remarks: (4601, 64700, 1337)
remarks: (210312, 64700, 1337)
remarks:
remarks: For any more info or collaboration, find me using the Contact
remarks: page at daknob.net :)
country: CH
geoloc: 47.38274404 8.503785134
admin-c: AAC138-RIPE
tech-c: AAC138-RIPE
status: ASSIGNED
mnt-by: gr-daknob-1-mnt
created: 2025-06-05T08:38:04Z
last-modified: 2025-11-17T11:53:05Z
source: RIPE
abuse-email: abuse@daknob.net
abuse-c: AR48003-RIPE
abuse-org: ORG-AAC10-RIPE
person: Antonis Chariton
address: Avidou 3
address: 59100
address: Veria
address: GREECE
e-mail: daknob@daknob.net
phone: +306988723888
remarks: +-------------------+
remarks: | Contact Info |
remarks: +-------------------+
remarks: | Signal: root.1337 |
remarks: +-------------------+
remarks: | iMessage: Phone |
remarks: +-------------------+
remarks: | Web: daknob.net |
remarks: +-------------------+
nic-hdl: AAC138-RIPE
mnt-by: gr-daknob-1-mnt
created: 2018-08-27T09:36:17Z
last-modified: 2025-11-17T12:36:33Z
source: RIPE
route6: 2a0d:3dc1::/32
origin: AS210312
remarks: The BGP Clock
remarks:
remarks: Read the inet6num for 2a0d:3dc1::/32 for (much) more info!
mnt-by: gr-daknob-1-mnt
created: 2025-11-17T11:41:02Z
last-modified: 2025-11-17T11:41:02Z
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 |
|---|---|---|
| 160.32.37.16 |
5.13ms from Chicago,
US
|
|
| 64.182.163.96 |
0.80ms from Dallas,
US
|
|
| 20.87.98.160 |
0.14ms from Johannesburg,
ZA
|
|
| 86.183.29.112 |
9.62ms from London,
GB
|
|
| 62.31.203.224 |
7.70ms from London,
GB
|
|
| 82.51.184.48 |
3.53ms from Milan,
IT
|
|
| 87.2.165.96 |
5.67ms from Milan,
IT
|
|
| 2.115.0.128 |
7.75ms from Milan,
IT
|
|
| 35.143.66.96 |
12.78ms from Orlando,
US
|
|
| 128.79.118.0 |
9.09ms from Paris,
FR
|
|
| 221.147.127.160 |
1.16ms from Seoul,
KR
|
|
| 1.41.105.128 |
11.55ms from Sydney,
AU
|
|
| 43.213.6.208 |
0.28ms from Taipei,
TW
|
|
| 190.204.159.112 |
16.15ms from Willemstad,
CW
|
|
| 62.250.116.112 |
3.06ms from Amsterdam,
NL
|
|
| 171.103.66.160 |
2.64ms from Bangkok,
TH
|
|
| 120.52.68.0 |
4.38ms from Beijing,
CN
|
|
| 217.139.139.240 |
18.36ms from Cairo,
EG
|
|
| 89.1.130.160 |
6.21ms from Duesseldorf,
DE
|
|
| 115.213.164.208 |
11.87ms from Hangzhou,
CN
|
|
| 202.85.128.240 |
2.24ms from Hong Kong,
HK
|
|
| 176.218.56.0 |
3.08ms from Istanbul,
TR
|
|
| 154.9.195.192 |
0.96ms from Las Vegas,
US
|
|
| 34.105.135.16 |
0.11ms from London,
GB
|
|
| 143.244.150.128 |
0.24ms from New York City,
US
|
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