subnet.im

163.159.0.0/18

The Ministry of Digital TransformationAS58046

At a glance

Addresses

16,384

/18 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCSI

Allocated 20th August 1992

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 163.159.0.0/18, fanning out from AS58046 toward the vantage points that see it. Each path is written out in full beneath the graph.AS58046The Ministry of D…OriginAS2107ARNESAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS174Cogent Communicat…AS132337AxclusiveAS21320GEANT VerenigingAS2603NORDUnetAS8529Zain Omantel Inte…AS6939Hurricane Electri…AS20130Depaul UniversityAS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. Sao Paulo5804621073356266213This path
  2. Singapore580462107174132337This path
  3. London, UK5804621072132026038529This path
  4. Oregon, US58046210721320693920130This path
  5. Amsterdam58046210721320260334549213151This 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

99%

Seen by 79 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
Slovenia
Allocated
20th August 1992
Allocation block
163.159.0.0/17
Status
assigned
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 163.159.0.0/18: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.163.159.0.0/17AS58046163.159.0.0/18AS58046This prefix163.159.64.0/18AS58046163.159.63.0/24AS58046

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 163.159.0.0/18
PrefixAddressesOriginVisibility
163.159.0.0/1732.8kAS58046The Ministry of Digital Transformation79/80

More specific announcements

Announcements contained within 163.159.0.0/18
PrefixAddressesOriginVisibility
163.159.63.0/24256AS58046The Ministry of Digital Transformation80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 163.159.0.0/18
PrefixAddressesOriginVisibility
163.159.64.0/1816.4kAS58046The Ministry of Digital Transformation79/80

History

  1. AS5804612th 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 163.159.0.0/18 in the calculator/18 reference

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