2806:20d:3600::/40

Currently announced by AS32098 Flō Networks, in the routed prefix 2806:20d:3600::/40.

Current ASN: AS32098; Flō Networks
Routed prefix: 2806:20d:3600::/40; Most specific route covering this prefix
ASNs over time: 1; 3 announcement records
RIR allocation: LACNIC; Mexico · 2806:20d::/32

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

ASN historyEvery routed prefix covering 2806:20d:3600::/40

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2806:20d:3600::/40	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3000::/36	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d::/32	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing

More specific routes21 total

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2806:20d:3600::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3601::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3602::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3607::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3613::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3615::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:361b::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:361c::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:361e::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:361f::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3622::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3623::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3624::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3625::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3626::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:3627::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:362c::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:362d::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:36fc::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:36fd::/48	AS32098	Flō Networks	United States	Before monitoring	2026-11-01 22:23	Announcing
2806:20d:36fe::/48	AS32098	Flō Networks	United States	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: 2806:20d::/32
Country: Mexico
Allocation date: 2015-12-09
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.