2a0f:b240:7c01::/48

Currently announced by AS210235 JULIANKUHN, in the routed prefix 2a0f:b240:7c00::/40.

Current ASN: AS210235; JULIANKUHN
Routed prefix: 2a0f:b240:7c00::/40; Most specific route covering this prefix
ASNs over time: 1; 2 announcement records
RIR allocation: RIPENCC; Canada · 2a0f:b240::/29

Routing data · Nov 11, 2026, 18:22 UTC

ASN historyEvery routed prefix covering 2a0f:b240:7c01::/48

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2a0f:b240:7c01::/48	AS210235	JULIANKUHN	Germany	Before monitoring	2026-11-11 04:24	Stopped
2a0f:b240:7c00::/40	AS210235	JULIANKUHN	Germany	Before monitoring	2026-11-11 18:22	Announcing

No more specific routes inside this prefix.

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-11-11 06:24	2a0f:b240:7c01::/48	Withdrawal	AS210235	JULIANKUHN	—	Germany

From the RIRs’ delegated statistics files. Shows where the addresses are registered, not where they are used.

Every 2 hours ASNBase takes the bgp.tools global routing table (prefix → origin ASN) and compares it with the previous one. The detected time is the time of that comparison; the actual change can be up to about 2 hours earlier.
Only routes seen by more than 100 bgp.tools peers are listed as changes; routes with less visibility are only kept in the history.
A new announcement counts only if it is still in the next routing table, and a withdrawal only if the prefix is missing from two tables in a row, so short flaps are ignored.
ASNBase has been monitoring since 2026-10-19. “Before monitoring” under “First seen” means the route was already announced when monitoring started; the earlier date is unknown.
Prefixes first seen during the first day of monitoring do not count as new announcements: most of them were simply missing from the table at the moment monitoring started.
Countries and regions follow the ASN’s registration, not the actual location of the IP addresses.