SUBNET.IM

185.201.240.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCIT

Allocated 4th May 2017

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.201.240.0/22, fanning out from AS44241 toward the vantage points that see it. Each path is written out in full beneath the graph.AS44241Infranet S.p.A.OriginAS44512KONVERTO SPAAS6663Türk Telekom Inte…AS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS3257GTT Communication…AS23352DEFT.COMAS20130Depaul University
  1. Amsterdam44241445126663213151This path
  2. London, UK442414451266638529This path
  3. Singapore44241445126663132337This path
  4. Sao Paulo442414451266633356266213This path
  5. Oregon, US442414451232572335220130This 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
Italy
Allocated
4th May 2017
Allocation block
185.201.240.0/22
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 185.201.240.0/22
ROA prefixAuthorised originMax length
185.201.240.0/22AS44241/22

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

No prefix of the same length in the same parent block is announced.

History

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

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