SUBNET.IM

206.53.4.0/22

At a glance

Addresses

1,024

/22 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 4th November 2008

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 206.53.4.0/22 as seen from Oregon, US, read outward from the origin: AS40321 → AS701 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS40321Emigrant BankOriginAS701Verizon BusinessAS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS40321seen on 48 paths from 48 vantage points
  2. Peer of AS701seen on 65,319 paths from 26 vantage points
  3. Peer of AS6939seen on 975,334 paths from 1 vantage point
  4. 4AS20130Depaul UniversityUSVantage 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, UK4032170164538529This path
  2. Singapore403217016939132337This path
  3. Oregon, US40321701693920130Shown above
  4. Sao Paulo403215400461283356266213This path
  5. Amsterdam40321540046128646134549213151This 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
4th November 2008
Allocation block
206.53.4.0/22
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 206.53.4.0/22
ROA prefixAuthorised originMax length
206.53.4.0/22AS40321/22

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

No prefix of the same length in the same parent block is announced.

History

  1. AS4032112th 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 206.53.4.0/22 in the calculator/22 reference

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