subnet.im

185.138.169.0/24

Voicenter LTDAS203077

Voicenter LTDAS203110

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

90%

72 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCIL

Allocated 12th February 2016

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 185.138.169.0/24, fanning out from AS203077 toward the vantage points that see it. Each path is written out in full beneath the graph.AS203077Voicenter LTDOriginAS8551Bezeq Internation…AS8529Zain Omantel Inte…AS174Cogent Communicat…AS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS3257GTT Communication…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS23352DEFT.COMAS20130Depaul University
  1. London, UK20307785518529This path
  2. Singapore2030778551174132337This path
  3. Amsterdam203077855117434549213151This path
  4. Sao Paulo203077855132573356266213This path
  5. Oregon, US203077855132572335220130This 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

90%

Seen by 72 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
Israel
Allocated
12th February 2016
Allocation block
185.138.168.0/22
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 185.138.169.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.185.138.168.0/23AS203110185.138.169.0/24AS203077This prefix185.138.168.0/24AS203110

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 185.138.169.0/24
PrefixAddressesOriginVisibility
185.138.168.0/23512AS203110Voicenter LTD80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.138.169.0/24
PrefixAddressesOriginVisibility
185.138.168.0/24256AS203110Voicenter LTD80/80

History

  1. AS20311012th August 2026 — present
  2. AS20307712th 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 185.138.169.0/24 in the calculator/24 reference

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