subnet.im

48.102.238.0/24

Akenai Products LTDAS219064

Ace Data Centers II, L.L.C.AS401152

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 7th December 1990

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 48.102.238.0/24 as seen from Oregon, US, read outward from the origin: AS219064 → AS49581 → AS44592 → AS6204 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS219064Akenai Products L…OriginAS49581Ferdinand Zink tr…AS44592SkyLink Data Cent…AS6204INTERKVM HOST SRLAS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS219064seen on 420 paths from 137 vantage points
  2. Peer of AS49581seen on 41,823 paths from 126 vantage points
  3. Peer of AS44592seen on 14,448 paths from 64 vantage points
  4. Peer of AS6204seen on 1,547 paths from 1 vantage point
  5. Peer of AS8551seen on 1,077,002 paths from 1 vantage 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. Amsterdam219064495818298This path
  2. London, UK2190644958169398529This path
  3. Sao Paulo2190644958144592645335280This path
  4. Oregon, US21906449581445926204855142013Shown above

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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

Observed at 4 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
United States
Allocated
7th December 1990
Allocation block
48.102.0.0/15
Status
assigned
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 48.102.238.0/24
ROA prefixAuthorised originMax length
48.102.238.0/24AS219064/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 48.102.238.0/24
PrefixAddressesOriginVisibility
48.102.239.0/24256AS49592Pipe Networks GmbH76/76

History

  1. AS4011525th November 2026 — present
  2. AS2190648th November 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 48.102.238.0/24 in the calculator/24 reference

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