subnet.im

38.91.112.0/22

GNET INC.AS9294

At a glance

Addresses

1,024

/22 block

Visibility

17%

13 of 76 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 16th April 1991

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: 1 observed path to 38.91.112.0/22, fanning out from AS9294 toward the vantage points that see it. Each path is written out in full beneath the graph.AS9294GNET INC.OriginAS18013ASLINE LIMITEDAS17476CloudRadium (HK) …AS2914NTT America, Inc.AS6453TATA Communicatio…AS7552Viettel GroupAS38623Metfone (Viettel …AS23673Cogetel Online, C…
  1. Singapore929418013174762914645375523862323673This 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.

Route visibility

17%

Seen by 13 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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
16th April 1991
Allocation block
38.0.0.0/8
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 38.91.112.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.38.91.112.0/21AS929438.0.0.0/8AS17438.91.112.0/22AS9294This prefix38.91.116.0/22AS929438.91.112.0/24AS2242738.91.113.0/24AS2242738.91.114.0/24AS2242738.91.115.0/24AS22427

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 38.91.112.0/22
PrefixAddressesOriginVisibility
38.91.112.0/212kAS9294GNET INC.76/76
38.0.0.0/816.8MAS174Cogent Communications, LLC74/76

More specific announcements

Announcements contained within 38.91.112.0/22
PrefixAddressesOriginVisibility
38.91.112.0/24256AS22427GNET INC.76/76
38.91.113.0/24256AS22427GNET INC.76/76
38.91.114.0/24256AS22427GNET INC.76/76
38.91.115.0/24256AS22427GNET INC.76/76

Sibling prefixes

Prefixes of the same length sharing a parent block with 38.91.112.0/22
PrefixAddressesOriginVisibility
38.91.116.0/221kAS9294GNET INC.13/76

History

  1. AS92947th November 2026 — present
  2. AS92946th November 2026 — 6th November 2026
  3. AS92941st November 2026 — 3rd November 2026
  4. AS929430th October 2026 — 31st October 2026
  5. AS929429th October 2026 — 30th October 2026
  6. AS929427th October 2026 — 28th October 2026
  7. AS929424th October 2026 — 25th October 2026
  8. AS929420th October 2026 — 22nd October 2026
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 38.91.112.0/22 in the calculator/22 reference

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