SUBNET.IM

46.148.255.0/24

MTS PJSCAS49154

AS65404

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

85%

68 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 6th December 2010

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.148.255.0/24, fanning out from AS49154, AS65404 toward the vantage points that see it. Each path is written out in full beneath the graph.AS49154MTS PJSCOriginAS8359MTS PJSCAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS65404OriginAS49154MTS PJSCAS8359MTS PJSCAS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS3257GTT Communication…AS23352DEFT.COMAS20130Depaul University
  1. London, UK49154835912998529This path
  2. Singapore65404491548359132337This path
  3. Amsterdam491548359129934549213151This path
  4. Sao Paulo49154835912993356266213This path
  5. Oregon, US491548359129932572335220130This 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

85%

Seen by 68 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
Russia
Allocated
6th December 2010
Allocation block
46.148.240.0/20
Status
allocated
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.

CoveringMore specific
Prefix hierarchy for 46.148.255.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.46.148.240.0/20AS835946.148.254.0/24AS4915446.148.255.0/24AS49154This prefix46.148.254.0/24AS65404

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 46.148.255.0/24
PrefixAddressesOriginVisibility
46.148.240.0/204.1kAS8359MTS PJSC80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 46.148.255.0/24
PrefixAddressesOriginVisibility
46.148.254.0/24256AS49154MTS PJSC68/80
46.148.254.0/24256AS6540412/80

History

  1. AS4915412th August 2026 — present
  2. AS6540412th 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.148.255.0/24 in the calculator/24 reference

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