SUBNET.IM

185.41.136.0/22

Fundaments B.V.AS20559

123Telcom BV trading as PartellAS57325

Announced by more than one origin AS (MOAS).

At a glance

Addresses

1,024

/22 block

Visibility

94%

75 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCNL

Allocated 27th 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.41.136.0/22, fanning out from AS20559, AS57325 toward the vantage points that see it. Each path is written out in full beneath the graph.AS20559Fundaments B.V.OriginAS132337AxclusiveAS20562Open Peering (Bro…AS213151Christian ElsenAS8529Zain Omantel Inte…AS6939Hurricane Electri…AS20130Depaul UniversityAS57325123Telcom BV trad…OriginAS42093InterRacks B.V.AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. Singapore20559132337This path
  2. Amsterdam2055920562213151This path
  3. London, UK20559205628529This path
  4. Oregon, US20559693920130This path
  5. Sao Paulo57325420933356266213This 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

94%

Seen by 75 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
Netherlands
Allocated
27th November 2013
Allocation block
185.41.136.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.41.136.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.41.136.0/22AS20559This prefix185.41.136.0/24AS57325185.41.137.0/24AS57325185.41.138.0/24AS57325185.41.139.0/24AS57325

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.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.41.136.0/22
PrefixAddressesOriginVisibility
185.41.140.0/221kAS49544i3D.net B.V80/80

History

  1. AS2055912th August 2026 — present
  2. AS5732512th 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.41.136.0/22 in the calculator/22 reference

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