SUBNET.IM

147.64.28.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 5th July 1991

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 147.64.28.0/22 as seen from Amsterdam, read outward from the origin: AS398564 → AS13536 → AS34549 → AS213151. Each hop is listed with its network name beneath the graph.AS398564Pennsylvania West…OriginAS13536FirstLight Networ…AS34549meerfarbig GmbH &…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS398564seen on 831 paths from 78 vantage points
  2. Peer of AS13536seen on 254 paths from 3 vantage points
  3. Peer of AS34549seen on 716,762 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. Amsterdam3985641353634549213151Shown above
  2. London, UK3985641353612998529This path
  3. Singapore398564135366939132337This path
  4. Oregon, US39856413536693920130This path
  5. Sao Paulo3985641353612993356266213This 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
ARIN — North America
Country
United States
Allocated
5th July 1991
Allocation block
147.64.0.0/16
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 147.64.28.0/22
ROA prefixAuthorised originMax length
147.64.0.0/16AS398564/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 147.64.28.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.147.64.0.0/16AS398564147.64.28.0/22AS398564This prefix

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

Announcements that contain 147.64.28.0/22
PrefixAddressesOriginVisibility
147.64.0.0/1665.5kAS398564Pennsylvania Western University80/80

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. AS39856412th 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 147.64.28.0/22 in the calculator/22 reference

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