2804:1bf0::/32

Currently announced by AS61758 TOP NET SERVIÇOS, in the routed prefix 2804:1bf0::/32.

Current ASN: AS61758; TOP NET SERVIÇOS
Routed prefix: 2804:1bf0::/32; Most specific route covering this prefix
ASNs over time: 1; 1 announcement record
RIR allocation: LACNIC; Brazil · 2804:1bf0::/32

Routing data · Nov 1, 2026, 22:23 UTC

ASN historyEvery routed prefix covering 2804:1bf0::/32

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2804:1bf0::/32	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing

More specific routes25 total

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2804:1bf0::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:2::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:7::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:a::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:c::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:14::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:16::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:1d::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:20::/47	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b0::/44	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b1::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b2::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b3::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b4::/46	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b8::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:ba::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:bb::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:bc::/46	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b00::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b01::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b02::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:b03::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:face::/48	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing
2804:1bf0:ff00::/40	AS61758	TOP NET SERVIÇOS	Brazil	Before monitoring	2026-11-01 22:23	Announcing

Change logAll changes

The routes covering this address have had no origin changes since ASNBase started monitoring.

Look up another address

RIR allocation record

Registry: LACNIC
Allocated block: 2804:1bf0::/32
Country: Brazil
Allocation date: 2014-08-14
Status: allocated

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

How monitoring works

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.