SUBNET.IM

185.40.188.0/22

IPMONT d.o.o. PodgoricaAS62301

At a glance

Addresses

1,024

/22 block

Visibility

54%

43 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCME

Allocated 18th November 2013

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.40.188.0/22, fanning out from AS62301 toward the vantage points that see it. Each path is written out in full beneath the graph.AS62301IPMONT d.o.o. Pod…OriginAS25467Akton d.o.o.AS132337AxclusiveAS262355VSX NetworksAS266213PLANETCLICK TELEC…AS21283A1 Slovenija d.d.AS8447A1 Telekom Austri…AS8529Zain Omantel Inte…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS6461Zayo BandwidthAS23352DEFT.COMAS20130Depaul University
  1. Singapore6230125467132337This path
  2. Sao Paulo6230125467262355266213This path
  3. London, UK62301254672128384478529This path
  4. Amsterdam623012546721283844734549213151This path
  5. Oregon, US623012546721283844764612335220130This 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

54%

Seen by 43 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
Montenegro
Allocated
18th November 2013
Allocation block
185.40.188.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.40.188.0/22: 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.40.188.0/22AS62301This prefix185.40.188.0/24AS62301185.40.189.0/24AS62301

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 185.40.188.0/22
PrefixAddressesOriginVisibility
185.40.188.0/24256AS62301IPMONT d.o.o. Podgorica80/80
185.40.189.0/24256AS62301IPMONT d.o.o. Podgorica80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.40.188.0/22
PrefixAddressesOriginVisibility
185.40.184.0/221kAS8769IT-Total Sweden AB79/80

History

  1. AS6230112th 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.40.188.0/22 in the calculator/22 reference

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