2a05:45c7:e300::/40

Currently announced by AS202660 BRM-DataCenter, in the routed prefix 2a05:45c7:e300::/40.

Current ASN: AS202660; BRM-DataCenter
Routed prefix: 2a05:45c7:e300::/40; Most specific route covering this prefix
ASNs over time: 1; 2 announcement records
RIR allocation: RIPENCC; Uzbekistan · 2a05:45c0::/29

Routing data · Nov 10, 2026, 12:46 UTC

ASN historyEvery routed prefix covering 2a05:45c7:e300::/40

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2a05:45c7:e300::/40	AS202660	BRM-DataCenter	Uzbekistan	2026-10-27 10:19	2026-11-10 12:46	Announcing
2a05:45c7:e000::/36	AS202660	BRM-DataCenter	Uzbekistan	Before monitoring	2026-11-10 12:46	Announcing

No more specific routes inside this prefix.

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-10-27 10:19	2a05:45c7:e300::/40	New announcement	AS202660	BRM-DataCenter	—	Uzbekistan

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.