2804:4e1c::/33

No route covers the whole prefix right now; more specific routes inside it are announced.

Routing data · Nov 8, 2026, 10:26 UTC

ASN historyEvery routed prefix covering 2804:4e1c::/33

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2804:4e1c::/33	AS268240	SVCOM	Brazil	Before monitoring	2026-11-06 16:24	Stopped
2804:4e1c::/32	AS268240	SVCOM	Brazil	Before monitoring	2026-11-06 16:24	Stopped

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2804:4e1c::/34	AS268240	SVCOM	Brazil	2026-11-06 18:24	2026-11-08 10:26	Announcing
2804:4e1c:4000::/44	AS268240	SVCOM	Brazil	2026-11-06 22:26	2026-11-08 10:26	Announcing

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-11-06 18:24	2804:4e1c::/33	Withdrawal	AS268240	SVCOM	—	Brazil
2026-11-06 18:24	2804:4e1c::/32	Withdrawal	AS268240	SVCOM	—	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.