bgpreport

Network · data from 2026-11-12

AS20018 Moapa Valley Telephone

Registry name: MVT-AS - Moapa Valley Telephone Company, US · PeeringDB

9IPv4 routes 88.9% RPKI valid · 88.9% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
5Route objects not announced registered with origin AS20018, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20018, 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.
44.125.0.0/24 No ROA None 673 100% 67
66.132.182.0/23 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
72.14.124.0/23 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
130.250.104.0/24 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
130.250.110.0/23 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
208.76.92.0/22 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
208.101.206.0/24 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
208.101.224.0/23 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
104.152.128.0/22 Valid RIR databaseALTDB, ARIN, RADB 670 100% 67
2602:fea1::/36 Valid RIR databaseALTDB, ARIN, RADB 636 100% 69

AS-SET

AS20018's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none44.125.0.0/24No ROA covers it. Add a ROA for AS20018, maxLength 24.673 of 673
Route object: none44.125.0.0/24No route object for it. Add a route object with origin AS20018 in the RIR database for the space.673 of 673

Route objects not announced

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

65.160.21.0/24RADBNo ROA
65.160.31.0/24RADBNo ROA
67.77.23.0/24RADBNo ROA
173.239.88.0/21RADBNo ROA
199.241.148.0/22RADBNo ROA

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.