subnet.im

152.89.171.0/24

NEOFIBER SRLSAS205358

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCES

Allocated 25th January 2019

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 152.89.171.0/24 as seen from Singapore, read outward from the origin: AS205358 → AS212271 → AS216309 → AS132337. Each hop is listed with its network name beneath the graph.AS205358NEOFIBER SRLSOriginAS212271Cinzia Tocci trad…AS216309InvisionTech Grou…AS132337Axclusive

Seen from Singapore

  1. 1AS205358NEOFIBER SRLSITOrigin
    Peer of AS205358seen on 283 paths from 136 vantage points
  2. 2AS212271Cinzia Tocci trading as Lumanex SrlIT
    Peer of AS212271seen on 230 paths from 56 vantage points
  3. 3AS216309InvisionTech Group S.r.l.IT
    Peer of AS216309seen on 8 paths from 1 vantage point
  4. 4AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Oregon, US205358693920130This path
  2. Singapore205358212271216309132337Shown above
  3. Amsterdam20535821227117434549213151This path
  4. London, UK20535821227117412998529This path
  5. Sao Paulo2053582122711743356266213This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

99%

Seen by 79 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
Spain
Allocated
25th January 2019
Allocation block
152.89.170.0/23
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 152.89.171.0/24
ROA prefixAuthorised originMax length
152.89.171.0/24AS205358/24
152.89.171.0/24AS212271/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

Prefixes of the same length sharing a parent block with 152.89.171.0/24
PrefixAddressesOriginVisibility
152.89.170.0/24256AS212271Cinzia Tocci trading as Lumanex Srl79/80

History

  1. AS20535812th August 2026 — present
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 152.89.171.0/24 in the calculator/24 reference

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