subnet.im

143.203.220.0/22

HYEHOST LLCAS47272

At a glance

Addresses

1,024

/22 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 2nd October 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 143.203.220.0/22, fanning out from AS47272 toward the vantage points that see it. Each path is written out in full beneath the graph.AS47272HYEHOST LLCOriginAS204208Peravix Group LTDAS215638Cilix LimitedAS8298IPng Networks GmbHAS6939Hurricane Electri…AS8529Zain Omantel Inte…AS835GoCodeIT IncAS35280F5 Networks SARLAS23673Cogetel Online, C…AS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam472722042082156388298This path
  2. London, UK4727220420869398529This path
  3. Sao Paulo4727220420883535280This path
  4. Singapore4727220420821563823673This path
  5. Oregon, US47272204208215638855142013This 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 76 of 76 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
2nd October 2026
Allocation block
143.203.220.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 143.203.220.0/22
ROA prefixAuthorised originMax length
143.203.220.0/22AS47272/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 143.203.220.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.143.203.220.0/22AS47272This prefix143.203.220.0/24AS47272143.203.221.0/24AS47272143.203.222.0/24AS47272143.203.223.0/24AS47272

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.

More specific announcements

Announcements contained within 143.203.220.0/22
PrefixAddressesOriginVisibility
143.203.220.0/24256AS47272HYEHOST LLC76/76
143.203.221.0/24256AS47272HYEHOST LLC76/76
143.203.222.0/24256AS47272HYEHOST LLC76/76
143.203.223.0/24256AS47272HYEHOST LLC76/76

Sibling prefixes

Prefixes of the same length sharing a parent block with 143.203.220.0/22
PrefixAddressesOriginVisibility
143.203.216.0/221kAS51082SPUZE LLC76/76

History

  1. AS472724th October 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 143.203.220.0/22 in the calculator/22 reference

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