SUBNET.IM

163.164.232.0/22

CGI France SASAS211124

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCGB

Allocated 26th August 1992

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 163.164.232.0/22, fanning out from AS211124 toward the vantage points that see it. Each path is written out in full beneath the graph.AS211124CGI France SASOriginAS5089Virgin Media Limi…AS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS6830Liberty Global Eu…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS1299Arelion (fka. Tel…AS132337AxclusiveAS2914NTT America, Inc.AS34549meerfarbig GmbH &…AS213151Christian ElsenAS3257GTT Communication…AS23352DEFT.COMAS20130Depaul University
  1. London, UK211124508933568529This path
  2. Sao Paulo211124508968303356266213This path
  3. Singapore211124508968301299132337This path
  4. Amsterdam21112450896830291434549213151This path
  5. Oregon, US2111245089683032572335220130This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Kingdom
Allocated
26th August 1992
Allocation block
163.164.0.0/16
Status
assigned
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.

CoveringMore specific
Prefix hierarchy for 163.164.232.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.163.164.232.0/22AS211124This prefix163.164.232.0/23AS211124

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 163.164.232.0/22
PrefixAddressesOriginVisibility
163.164.232.0/23512AS211124CGI France SAS79/80

Sibling prefixes

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

History

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

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