subnet.im

5.231.50.0/24

TURNEL LLCAS403093

GHOSTnet GmbHAS12586

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 NCCDE

Allocated 11th September 2012

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: 4 observed paths to 5.231.50.0/24, fanning out from AS403093 toward the vantage points that see it. Each path is written out in full beneath the graph.AS403093TURNEL LLCOriginAS24875NovoServe B.V.AS8298IPng Networks GmbHAS8529Zain Omantel Inte…AS2914NTT America, Inc.AS35280F5 Networks SARLAS5405Inter.link GmbHAS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam403093248758298This path
  2. London, UK403093248758529This path
  3. Sao Paulo40309324875291435280This path
  4. Oregon, US403093248755405855142013This 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

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
Germany
Allocated
11th September 2012
Allocation block
5.230.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 5.231.50.0/24
ROA prefixAuthorised originMax length
5.231.50.0/24AS403093/24
5.230.0.0/15AS12586/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 5.231.50.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.5.230.0.0/15AS125865.231.50.0/24AS403093This prefix5.231.51.0/24AS12586

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.

Covering announcements

Announcements that contain 5.231.50.0/24
PrefixAddressesOriginVisibility
5.230.0.0/15131kAS12586GHOSTnet GmbH76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 5.231.50.0/24
PrefixAddressesOriginVisibility
5.231.51.0/24256AS12586GHOSTnet GmbH76/76

History

  1. AS4030939th November 2026 — present
  2. AS1258612th 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 5.231.50.0/24 in the calculator/24 reference

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