bgpreport

Network · data from 2026-11-12

AS13331 Metapeer

Registry name: METAPEER-INC - MetaPeer, US · PeeringDB

11IPv4 routes 0.0% RPKI valid · 90.9% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
28Route objects not announced registered with origin AS13331, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13331, 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.
209.222.69.0/24 No ROA Nonecovered by 209.222.68.0/23 670 100% 67
163.237.208.0/24 No ROA Other IRR onlyRADB 671 100% 67
207.229.71.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
207.229.72.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
207.229.73.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
207.229.74.0/24 No ROA Other IRR onlyRADB 670 100% 67
207.229.75.0/24 No ROA Other IRR onlyRADB 670 100% 67
208.93.88.0/22 No ROA Other IRR onlyRADB 670 100% 67
2001:4978:5ff::/48 No ROA Other IRR onlyRADB 636 100% 68
163.237.210.0/24 No ROA Other IRR onlyRADB 200 30% 52
204.15.8.0/21 No ROA RIR databaseARIN, RADB 672 100% 67
162.249.16.0/22 No ROA RIR databaseARIN, RADB 670 100% 67
2620:11c:5000::/44 Valid RIR databaseARIN 635 100% 68

AS-SET

AS13331'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 50 are in fix.csv.

  • ROA: none12
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none209.222.69.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: none209.222.69.0/24No route object for it. A route object for 209.222.68.0/23 with origin AS13331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13331 in the RIR database for the space.670 of 673
ROA: none163.237.208.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.671 of 673
Route object: RIR163.237.208.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none207.229.71.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: RIR207.229.71.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none207.229.72.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: RIR207.229.72.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none207.229.73.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: RIR207.229.73.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none207.229.74.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: RIR207.229.74.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none207.229.75.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.670 of 673
Route object: RIR207.229.75.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.93.88.0/22No ROA covers it. Add a ROA for AS13331, maxLength 22.670 of 673
Route object: RIR208.93.88.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:4978:5ff::/48No ROA covers it. Add a ROA for AS13331, maxLength 48.636 of 636
Route object: RIR2001:4978:5ff::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none163.237.210.0/24No ROA covers it. Add a ROA for AS13331, maxLength 24.200 of 673
Route object: RIR163.237.210.0/24Route object only in RADB. Add it in the RIR database for the space.200 of 673
ROA: none204.15.8.0/21No ROA covers it. Add a ROA for AS13331, maxLength 21.672 of 673
ROA: none162.249.16.0/22No ROA covers it. Add a ROA for AS13331, maxLength 22.670 of 673

Route objects not announced

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

66.154.105.0/24NTTCOMNo ROA
162.249.19.0/24RADBNo ROA
163.237.222.0/24RADBNo ROA
163.237.223.0/24RADBNo ROA
163.237.224.0/24RADBNo ROA
163.237.225.0/24RADBNo ROA
163.237.240.0/24NTTCOM, RADBNo ROA
192.203.32.0/24RADBNo ROA
192.203.33.0/24RADBNo ROA
192.203.34.0/24RADBNo ROA
192.203.35.0/24RADBNo ROA
192.203.36.0/24RADBNo ROA
199.254.229.0/24ALTDBNo ROA
206.197.106.0/24RADBNo ROA
207.229.72.0/22RADBNo ROA
209.162.128.0/19ALTDBNo ROA
209.222.68.0/23ARIN, RADBNo ROA
209.222.68.0/24RADBNo ROA
2001:4978:500::/48RADBNo ROA
2001:4978:501::/48RADBNo ROA
2001:4978:502::/48RADBNo ROA
2001:4978:503::/48RADBNo ROA
2001:4978:504::/48RADBNo ROA
2001:4978:1001::/48RADBNo ROA
2001:4978:1002::/48RADBNo ROA
2001:4978:1003::/48RADBNo ROA
2001:4978:1004::/48RADBNo ROA
2001:4978:10ae::/48RADBNo 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.