SUBNET.IM

31.217.135.0/24

IX Reach LtdAS4455

BSO Network Solutions SASAS31216

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

63%

50 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 11th August 2011

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
  1. London, UK445512998529This path
  2. Singapore44551299132337This path
  3. Amsterdam31216645334549213151This path
  4. Sao Paulo445512993356266213This path
  5. Oregon, US312166453693920130This 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

63%

Seen by 50 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
France
Allocated
11th August 2011
Allocation block
31.217.128.0/19
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 31.217.135.0/24
ROA prefixAuthorised originMax length
31.217.128.0/19AS31216/24
31.217.128.0/19AS43531/24
31.217.128.0/19AS4455/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 31.217.135.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.31.217.128.0/19AS445531.217.128.0/19AS3121631.217.128.0/19AS4353131.217.135.0/24AS4455This prefix

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 31.217.135.0/24
PrefixAddressesOriginVisibility
31.217.128.0/198.2kAS4455IX Reach Ltd62/80
31.217.128.0/198.2kAS31216BSO Network Solutions SAS15/80
31.217.128.0/198.2kAS43531BSO Network Solutions SAS3/80

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. AS3121612th August 2026 present
  2. AS445512th 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 31.217.135.0/24 in the calculator/24 reference

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