2804:5984:8a10::/48

Currently announced by AS262663 METROFLEX, in the routed prefix 2804:5984:8a10::/48.

Current ASN: AS262663; METROFLEX
Routed prefix: 2804:5984:8a10::/48; Most specific route covering this prefix
ASNs over time: 2; 4 announcement records
RIR allocation: LACNIC; Brazil · 2804:5984::/32

Routing data · Nov 1, 2026, 20:20 UTC

ASN historyEvery routed prefix covering 2804:5984:8a10::/48

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2804:5984:8a10::/48	AS262663	METROFLEX	Brazil	Before monitoring	2026-11-01 20:20	Announcing
2804:5984:8000::/36	AS268707	4WNET AS268707	Brazil	Before monitoring	2026-11-01 20:20	Announcing
2804:5984:8000::/35	AS268707	4WNET AS268707	Brazil	Before monitoring	2026-10-27 12:20	Stopped
2804:5984:8000::/33	AS268707	4WNET AS268707	Brazil	Before monitoring	2026-11-01 20:20	Announcing

No more specific routes inside this prefix.

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-10-31 14:22	2804:5984:8a10::/48	WithdrawalAnnounced again	AS262663	METROFLEX	—	Brazil
2026-10-27 14:20	2804:5984:8000::/35	Withdrawal	AS268707	4WNET AS268707	—	Brazil

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.