subnet.im

192.235.32.0/20

Petersburg Internet Network ltd.AS44050

PIN LLCAS54985

Announced by more than one origin AS (MOAS).

At a glance

Addresses

4,096

/20 block

Visibility

56%

45 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 25th February 2013

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 192.235.32.0/20 as seen from Amsterdam, read outward from the origin: AS44050 → AS50509 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS44050Petersburg Intern…OriginAS50509Transroute.NetAS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS44050Petersburg Internet Network ltd.RUOrigin
    Peer of AS44050seen on 8,339 paths from 137 vantage points
  2. 2AS50509Transroute.NetRU
    Peer of AS50509seen on 51,174 paths from 133 vantage points
  3. 3AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 309,709 paths from 2 vantage points
  4. 4AS213151Christian ElsenDEVantage 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. London, UK440501374098529This path
  2. Amsterdam44050505096939213151Shown above
  3. Sao Paulo44050505096939266213This path
  4. Singapore44050505096939132337This path
  5. Oregon, US5498550509693920130This 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

56%

Seen by 45 of 80 full-feed vantage points

Partially 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
25th February 2013
Allocation block
192.235.32.0/20
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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 192.235.32.0/20
PrefixAddressesOriginVisibility
192.235.48.0/204.1kAS14813Columbus Telecommunications (Barbados) Limited79/80

History

  1. AS4405012th August 2026 — present
  2. AS5498512th 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 192.235.32.0/20 in the calculator/20 reference

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