SUBNET.IM

217.148.48.0/20

Ekaterinburg-2000 LLCAS31499

At a glance

Addresses

4,096

/20 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 26th May 2004

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 217.148.48.0/20, fanning out from AS31499 toward the vantage points that see it. Each path is written out in full beneath the graph.AS31499Ekaterinburg-2000…OriginAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS20764CJSC RASCOMAS6939Hurricane Electri…AS213151Christian ElsenAS3216Vimpelcom PJSCAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS20130Depaul UniversityAS51028Zummer LLCAS12389Rostelecom PJSCAS4766Korea TelecomAS132337Axclusive
  1. London, UK3149912998529This path
  2. Amsterdam31499207646939213151This path
  3. Sao Paulo3149932163356266213This path
  4. Oregon, US3149920764693920130This path
  5. Singapore3149951028123894766132337This 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
Russia
Allocated
26th May 2004
Allocation block
217.148.48.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.

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 217.148.48.0/20
PrefixAddressesOriginVisibility
217.148.32.0/204.1kAS29527Astutium Limited79/80

History

  1. AS3149912th 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 217.148.48.0/20 in the calculator/20 reference

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