SUBNET.IM

202.165.64.0/21

GSL Networks Pty LTDAS137409

At a glance

Addresses

2,048

/21 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

APNICAU

Allocated 24th May 1999

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 202.165.64.0/21 as seen from Sao Paulo, read outward from the origin: AS137409 → AS266213. Each hop is listed with its network name beneath the graph.AS137409GSL Networks Pty …OriginAS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. 1AS137409GSL Networks Pty LTDAUOrigin
    Peer of AS137409seen on 12,063 paths from 2 vantage points
  2. 2AS266213PLANETCLICK TELECOMUNICACOES LTDABRVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Amsterdam137409213151This path
  2. London, UK1374098529This path
  3. Sao Paulo137409266213Shown above
  4. Singapore137409132337This path
  5. Oregon, US13740932572335220130This 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
APNIC — Asia-Pacific
Country
Australia
Allocated
24th May 1999
Allocation block
202.165.64.0/21
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 202.165.64.0/21: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.202.165.64.0/21AS137409This prefix202.165.64.0/23AS137409202.165.66.0/23AS137409202.165.70.0/23AS137409202.165.64.0/24AS137409202.165.65.0/24AS137409+5 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 202.165.64.0/21
PrefixAddressesOriginVisibility
202.165.72.0/212kAS7029Windstream Communications LLC80/80

History

  1. AS13740912th 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 202.165.64.0/21 in the calculator/21 reference

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