bgpreport

Network · data from 2026-11-12

AS47022 WILSON-TELEPHONE-COMPANY-INC - Wilson Telephone Company Inc

Registry name: WILSON-TELEPHONE-COMPANY-INC - Wilson Telephone Company Inc, US · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS47022, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47022, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
199.87.200.0/21 No ROA Other origin only 670 100% 68
199.87.200.0/24 Valid RIR databaseARIN 670 100% 68
199.87.201.0/24 Valid RIR databaseARIN 670 100% 68
199.87.206.0/24 Valid RIR databaseARIN 670 100% 68
199.87.207.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

AS47022 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none199.87.200.0/21No ROA covers it. Add a ROA for AS47022, maxLength 21.670 of 673
Route object: none199.87.200.0/21Route objects for it name AS13329. Add a route object with origin AS47022 in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS47022 whose prefix no peer sees AS47022 announce. Many are kept on purpose (backup routes, space announced only in some places).

199.87.202.0/24ARINValid
199.87.203.0/24ARINValid
199.87.204.0/24ARINValid
199.87.205.0/24ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.