subnet.im

184.164.250.0/24

Not announced at this prefix length

No announcement covering 184.164.250.0/24 was visible from any of our collectors at the last snapshot. That can mean the space is unrouted, or that it is announced only within a network we have no vantage point inside.

At a glance

Addresses

256

/24 block

Visibility

Unknown

RPKI

Unknown

Registry

ARINUS

Allocated 2nd June 2011

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
2nd June 2011
Allocation block
184.164.224.0/19
Status
allocated
Origin validation
Unknown

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 184.164.250.0/24
PrefixAddressesOriginVisibility
184.164.251.0/24256AS47065USC / UFMG PEERING Research Testbed74/76

History

  1. AS4706517th October 2026 — 24th October 2026
  2. AS4706515th October 2026 — 16th October 2026
  3. AS470655th October 2026 — 14th October 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 184.164.250.0/24 in the calculator/24 reference

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