2620:74:2c::/48

Currently announced jointly by AS19836 VeriSign Infrastructure & Operations, AS20172 VeriSign Global Registry Services, AS22547 VeriSign Global Registry Services, AS36617 VeriSign Global Registry Services, AS36623 VeriSign Global Registry Services, AS211369 VERISIGN-AS, AS396544 VeriSign Global Registry Services, AS396545 VeriSign Global Registry Services, AS396560 VeriSign Global Registry Services, AS396576 VeriSign Global Registry Services, AS397199 VeriSign Global Registry Services, AS397204 VeriSign Global Registry Services, AS397206 VeriSign Global Registry Services, AS397210 VeriSign Global Registry Services, in the routed prefix 2620:74:2c::/48.

Current ASN: AS19836 AS20172 AS22547 AS36617 AS36623 AS211369 AS396544 AS396545 AS396560 AS396576 AS397199 AS397204 AS397206 AS397210; VeriSign Infrastructure & Operations
Routed prefix: 2620:74:2c::/48; Most specific route covering this prefix
ASNs over time: 15; 15 announcement records
RIR allocation: ARIN; United States · 2620:74:20::/43

Routing data · Oct 23, 2026, 02:20 UTC

ASN historyEvery routed prefix covering 2620:74:2c::/48

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2620:74:2c::/48	AS19836	VeriSign Infrastructure & Operations	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS20172	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS22547	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS36617	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS36623	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS211369	VERISIGN-AS	United States	2026-10-20 02:19	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS396544	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS396545	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS396560	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS396576	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS397199	VeriSign Global Registry Services	United States	2026-10-20 02:19	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS397204	VeriSign Global Registry Services	United States	2026-10-20 02:19	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS397206	VeriSign Global Registry Services	United States	Before monitoring	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS397210	VeriSign Global Registry Services	United States	2026-10-22 18:21	2026-10-23 02:20	Announcing
2620:74:2c::/48	AS396605	VeriSign Global Registry Services	United States	Before monitoring	2026-10-20 00:21	Stopped

More specific routes0 total

No more specific routes inside this prefix.

Change logAll changes

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-10-22 18:21	2620:74:2c::/48	Origin added	AS397210	VeriSign Global Registry Services	AS19836 AS20172 AS22547 AS36617 AS36623 AS211369 AS396544 AS396560 AS397199 AS397204	United States

Look up another address

RIR allocation record

Registry: ARIN
Allocated block: 2620:74:20::/43
Country: United States
Allocation date: 2010-05-06
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.