subnet.im

181.203.128.0/18

At a glance

Addresses

16,384

/18 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

ARINCA

Allocated 16th July 2026

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 181.203.128.0/18, fanning out from AS5769 toward the vantage points that see it. Each path is written out in full beneath the graph.AS5769Videotron LteeOriginAS35280F5 Networks SARLAS1299Arelion (fka. Tel…AS35280F5 Networks SARLAS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS25091IP-Max SAAS8298IPng Networks GmbH
  1. Sao Paulo576935280This path
  2. London, UK5769129935280This path
  3. Singapore57696939132337This path
  4. Oregon, US5769693920130This path
  5. Amsterdam57691299250918298This 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 80 of 81 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
Canada
Allocated
16th July 2026
Allocation block
181.203.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 181.203.128.0/18
ROA prefixAuthorised originMax length
181.203.0.0/16AS20365/24
181.203.0.0/16AS36273/24
181.203.0.0/16AS54198/24
181.203.0.0/16AS5769/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 181.203.128.0/18: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.181.203.0.0/16AS5769181.203.128.0/18AS5769This prefix181.203.192.0/18AS5769

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 181.203.128.0/18
PrefixAddressesOriginVisibility
181.203.0.0/1665.5kAS5769Videotron Ltee80/81

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 181.203.128.0/18
PrefixAddressesOriginVisibility
181.203.192.0/1816.4kAS5769Videotron Ltee80/81

History

  1. AS576922nd September 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 181.203.128.0/18 in the calculator/18 reference

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