bgpreport

Network · data from 2026-11-12

AS212316 Melmasti Global (Gibraltar) Limited

Registry name: Melmasti-Global Melmasti Global (Gibraltar) Limited, GI · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object
6IPv6 routes 100.0% RPKI valid · 16.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 7 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS212316, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212316, 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.6.126.0/24 Valid Nonecovered by 107.6.126.0/23 671 100% 66
107.6.127.0/24 Valid Nonecovered by 107.6.126.0/23 671 100% 66
2a05:dc80::/48 Valid Nonecovered by 2a05:dc80::/29 633 100% 67
2a05:dc86::/48 Valid Nonecovered by 2a05:dc80::/29 633 100% 67
2a05:dc86:1::/48 Valid Nonecovered by 2a05:dc80::/29 633 100% 67
2a05:dc86:10::/48 Valid Nonecovered by 2a05:dc80::/29 633 100% 67
2a05:dc86:11::/48 Valid Nonecovered by 2a05:dc80::/29 633 100% 67
107.6.126.0/23 Valid Other IRR onlyRADB 671 100% 66
2a05:dc80::/29 Valid Other IRR onlyRADB 632 99% 67

AS-SET

AS212316'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 10 are in fix.csv.

  • Route object: none7
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none107.6.126.0/24No route object for it. A route object for 107.6.126.0/23 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.671 of 673
Route object: none107.6.127.0/24No route object for it. A route object for 107.6.126.0/23 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.671 of 673
Route object: none2a05:dc80::/48No route object for it. A route object for 2a05:dc80::/29 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.633 of 636
Route object: none2a05:dc86::/48No route object for it. A route object for 2a05:dc80::/29 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.633 of 636
Route object: none2a05:dc86:1::/48No route object for it. A route object for 2a05:dc80::/29 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.633 of 636
Route object: none2a05:dc86:10::/48No route object for it. A route object for 2a05:dc80::/29 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.633 of 636
Route object: none2a05:dc86:11::/48No route object for it. A route object for 2a05:dc80::/29 with origin AS212316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212316 in the RIR database for the space.633 of 636
Route object: RIR107.6.126.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2a05:dc80::/29Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

2a0c:9a40:8690::/48RADBValid

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.