subnet.im

151.243.179.0/24

Not announced at this prefix length

No announcement covering 151.243.179.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

RIPE NCCAE

Allocated 15th August 2012

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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Arab Emirates
Allocated
15th August 2012
Allocation block
151.243.128.0/17
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 151.243.179.0/24
ROA prefixAuthorised originMax length
151.243.179.0/24AS20473/24
151.243.179.0/24AS834/24
151.243.178.0/23AS834/24
151.243.176.0/21AS834/24

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

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

History

  1. AS3653026th September 2026 — 26th September 2026
  2. AS40177612th August 2026 — 21st September 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 151.243.179.0/24 in the calculator/24 reference

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