SUBNET.IM

90.158.72.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 29th January 2007

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 90.158.72.0/24 as seen from Singapore, read outward from the origin: AS9021 → AS32787 → AS132337. Each hop is listed with its network name beneath the graph.AS9021Is Net Elektonik …OriginAS32787Akamai (Prolexic)AS132337Axclusive

Seen from Singapore

  1. Peer of AS9021seen on 1,120 paths from 80 vantage points
  2. Peer of AS32787seen on 6,619 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Amsterdam902132787213151This path
  2. London, UK9021327878529This path
  3. Sao Paulo902132787266213This path
  4. Singapore902132787132337Shown above
  5. Oregon, US902132787693920130This 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

100%

Seen by 80 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
Türkiye
Allocated
29th January 2007
Allocation block
90.158.0.0/15
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 90.158.72.0/24
ROA prefixAuthorised originMax length
90.158.72.0/24AS9021/24
90.158.72.0/22AS9021/22
90.158.0.0/16AS9021/16

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 90.158.72.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.90.158.72.0/22AS902190.158.0.0/16AS902190.158.72.0/24AS9021This prefix90.158.73.0/24AS9021

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.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 90.158.72.0/24
PrefixAddressesOriginVisibility
90.158.73.0/24256AS9021Is Net Elektonik Bilgi Uretim Dagitim Ticaret ve Iletisim Hizmetleri A.S.80/80

History

  1. AS902112th 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 90.158.72.0/24 in the calculator/24 reference

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