SUBNET.IM

205.201.240.0/20

At a glance

Addresses

4,096

/20 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 20th June 2008

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 205.201.240.0/20, fanning out from AS22925 toward the vantage points that see it. Each path is written out in full beneath the graph.AS22925Allied Telecom Gr…OriginAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul UniversityAS2914NTT America, Inc.AS34549meerfarbig GmbH &…AS213151Christian ElsenAS8966Etisalat (E&)AS132337Axclusive
  1. London, UK2292533568529This path
  2. Sao Paulo229253356266213This path
  3. Oregon, US22925693920130This path
  4. Amsterdam22925291434549213151This path
  5. Singapore2292529148966132337This 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
ARIN — North America
Country
United States
Allocated
20th June 2008
Allocation block
205.201.240.0/20
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 205.201.240.0/20
ROA prefixAuthorised originMax length
205.201.240.0/20AS22925/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 205.201.240.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.205.201.240.0/20AS22925This prefix205.201.241.0/24AS22925

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 205.201.240.0/20
PrefixAddressesOriginVisibility
205.201.241.0/24256AS22925Allied Telecom Group, LLC79/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 205.201.240.0/20
PrefixAddressesOriginVisibility
205.201.224.0/204.1kAS7314Peace Communications LLC80/80

History

  1. AS2292512th 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 205.201.240.0/20 in the calculator/20 reference

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