subnet.im

67.20.121.0/24

Not announced at this prefix length

We do not see 67.20.121.0/24 announced as its own route. The most specific announcement covering it is 67.20.120.0/23, originated by AS46606 (Unified Layer). Traffic to addresses in this block follows that route.

At a glance

Addresses

256

/24 block

Visibility

Unknown

RPKI

Unknown

Registry

ARINUS

Allocated 14th January 2009

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
ARIN — North America
Country
United States
Allocated
14th January 2009
Allocation block
67.20.64.0/18
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 67.20.121.0/24
ROA prefixAuthorised originMax length
67.20.120.0/22AS396982/22
67.20.64.0/18AS19871/24
67.20.64.0/18AS198949/24
67.20.64.0/18AS26337/24
67.20.64.0/18AS31898/24
67.20.64.0/18AS46606/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 67.20.121.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.67.20.120.0/23AS4660667.20.120.0/22AS3189867.20.64.0/18AS4660667.20.121.0/24This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 67.20.121.0/24
PrefixAddressesOriginVisibility
67.20.120.0/23512AS46606Unified Layer76/76
67.20.120.0/221kAS31898Oracle Cloud76/76
67.20.64.0/1816.4kAS46606Unified Layer76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS466069th November 2026 — 9th November 2026
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 67.20.121.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.