bgpreport

Network · data from 2026-11-12

AS11070 Metanet Communications

Registry name: META-AS - Metanet Communications, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11070, 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.
107.182.0.0/24 No ROA None 672 100% 67
107.182.1.0/24 No ROA None 672 100% 67
107.182.10.0/24 No ROA None 672 100% 67
107.182.13.0/24 No ROA None 672 100% 67
192.225.163.0/24 Valid None 672 100% 67
192.225.165.0/24 Valid None 672 100% 67
192.225.166.0/24 Valid None 672 100% 67
192.225.172.0/24 Valid None 672 100% 67
192.225.173.0/24 Valid None 672 100% 67
192.225.175.0/24 Valid None 672 100% 67

AS-SET

AS11070'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 18 are in fix.csv.

  • ROA: none4
  • Route object: none10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none107.182.0.0/24No ROA covers it. Add a ROA for AS11070, maxLength 24.672 of 673
Route object: none107.182.0.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
ROA: none107.182.1.0/24No ROA covers it. Add a ROA for AS11070, maxLength 24.672 of 673
Route object: none107.182.1.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
ROA: none107.182.10.0/24No ROA covers it. Add a ROA for AS11070, maxLength 24.672 of 673
Route object: none107.182.10.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
ROA: none107.182.13.0/24No ROA covers it. Add a ROA for AS11070, maxLength 24.672 of 673
Route object: none107.182.13.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.163.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.165.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.166.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.172.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.173.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673
Route object: none192.225.175.0/24No route object for it. Add a route object with origin AS11070 in the RIR database for the space.672 of 673

Route objects not announced

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

66.128.200.0/22ARINValid
107.182.14.0/24ARINValid
209.45.246.0/23ARINNo ROA
209.45.248.0/23ARINNo 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.