Network · data from 2026-11-12

AS199124 Mega Limited

Registry name: MEGALimited MEGA Privacy Kft., HU · PeeringDB

5IPv4 routes 100.0% RPKI valid · 80.0% with a route object

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS199124, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199124, 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.


91.218.79.0/24	Valid	Nonecovered by 91.218.78.0/23	673 100%	67
2a09:a380:1::/48	Valid	Nonecovered by 2a09:a380::/40	635 100%	67
2a09:a380:3::/48	Valid	Nonecovered by 2a09:a380::/40	635 100%	67
82.29.200.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
82.29.201.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.218.78.0/23	Valid	RIR databaseRIPE	673 100%	67
69.30.89.0/24	Valid	RIR databaseRIPE	670 100%	67
2a09:a380::/40	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS199124'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 3 are in fix.csv.

Route object: none3

Change	Prefix or set	Detail	Full-table peers
Route object: none	91.218.79.0/24	No route object for it. A route object for 91.218.78.0/23 with origin AS199124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199124 in the RIR database for the space.	673 of 673
Route object: none	2a09:a380:1::/48	No route object for it. A route object for 2a09:a380::/40 with origin AS199124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199124 in the RIR database for the space.	635 of 636
Route object: none	2a09:a380:3::/48	No route object for it. A route object for 2a09:a380::/40 with origin AS199124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199124 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

91.218.79.0/24

No route object for it. A route object for 91.218.78.0/23 with origin AS199124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199124 in the RIR database for the space.

673 of 673

Route object: none

2a09:a380:1::/48

No route object for it. A route object for 2a09:a380::/40 with origin AS199124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199124 in the RIR database for the space.

635 of 636

Route object: none

2a09:a380:3::/48

635 of 636

Route objects not announced

Every route object with origin AS199124 is announced.

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.