SUBNET.IM

46.235.85.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCKZ

Allocated 10th February 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
AS path graph: 5 observed paths to 46.235.85.0/24, fanning out from AS35104 toward the vantage points that see it. Each path is written out in full beneath the graph.AS35104Jusan Mobile JSCOriginAS43727JSC KVANT-TELEKOMAS8529Zain Omantel Inte…AS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS20130Depaul UniversityAS3216Vimpelcom PJSCAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK35104437278529This path
  2. Singapore3510443727132337This path
  3. Amsterdam35104437276939213151This path
  4. Oregon, US3510443727693920130This path
  5. Sao Paulo351044372732163356266213This 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
Kazakhstan
Allocated
10th February 2011
Allocation block
46.235.80.0/21
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 46.235.85.0/24
ROA prefixAuthorised originMax length
46.235.85.0/24AS35104/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 46.235.85.0/24
PrefixAddressesOriginVisibility
46.235.84.0/24256AS35104Jusan Mobile JSC80/80

History

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

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