SUBNET.IM

62.205.128.0/19

NetAssist LLCAS8772

Netassist International EOODAS29632

Announced by more than one origin AS (MOAS).

At a glance

Addresses

8,192

/19 block

Visibility

98%

78 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 1st February 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 62.205.128.0/19, fanning out from AS8772, AS29632 toward the vantage points that see it. Each path is written out in full beneath the graph.AS29632Netassist Interna…OriginAS8529Zain Omantel Inte…AS8772NetAssist LLCOriginAS132337AxclusiveAS29632Netassist Interna…AS213151Christian ElsenAS6939Hurricane Electri…AS20130Depaul UniversityAS9002RETN LimitedAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK296328529This path
  2. Singapore8772132337This path
  3. Amsterdam877229632213151This path
  4. Oregon, US8772693920130This path
  5. Sao Paulo877290023356266213This 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

98%

Seen by 78 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
United Kingdom
Allocated
1st February 2008
Allocation block
62.205.128.0/19
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 62.205.128.0/19
ROA prefixAuthorised originMax length
62.205.128.0/19AS8772/19

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 62.205.128.0/19: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.62.205.128.0/19AS8772This prefix62.205.128.0/20AS877262.205.128.0/20AS2963262.205.144.0/20AS2963262.205.144.0/20AS877262.205.132.0/24AS8772+6 more

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 62.205.128.0/19
PrefixAddressesOriginVisibility
62.205.160.0/198.2kAS8402Vimpelcom OJSC (Beeline)80/80

History

  1. AS2963212th August 2026 — present
  2. AS877212th 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 62.205.128.0/19 in the calculator/19 reference

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