subnet.im

159.242.13.0/24

G1SAT B.V.AS205019

TrustComm, Inc.AS26857

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

65%

52 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCNL

Allocated 17th June 1992

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 159.242.13.0/24, fanning out from AS26857, AS205019 toward the vantage points that see it. Each path is written out in full beneath the graph.AS205019G1SAT B.V.OriginAS6939Hurricane Electri…AS213151Christian ElsenAS26857TrustComm, Inc.OriginAS6461Zayo BandwidthAS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS20130Depaul University
  1. Amsterdam2050196939213151This path
  2. London, UK2685764618529This path
  3. Sao Paulo2050196939266213This path
  4. Singapore2050196939132337This path
  5. Oregon, US205019693920130This 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

65%

Seen by 52 of 80 full-feed vantage points

Partially 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
Netherlands
Allocated
17th June 1992
Allocation block
159.242.8.0/21
Status
assigned
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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. AS20501912th August 2026 — present
  2. AS2685712th 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 159.242.13.0/24 in the calculator/24 reference

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