SUBNET.IM

178.211.92.0/22

At a glance

Addresses

1,024

/22 block

Visibility

24%

19 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCIT

Allocated 30th June 2010

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
  1. Singapore47408132337This path
  2. London, UK474081374098529This path
  3. Sao Paulo47408262355266213This path
  4. Oregon, US47408693920130This path
  5. Amsterdam4740869395829941051213151This 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

24%

Seen by 19 of 80 full-feed vantage points

Seen by few vantage points

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
Italy
Allocated
30th June 2010
Allocation block
178.211.64.0/19
Status
allocated
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 178.211.92.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.178.211.64.0/19AS47408178.211.92.0/22AS47408This 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 178.211.92.0/22
PrefixAddressesOriginVisibility
178.211.64.0/198.2kAS47408Mandarin S.p.A.80/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. AS4740812th 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 178.211.92.0/22 in the calculator/22 reference

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