bgpreport

Network · data from 2026-11-12

AS205809 MEGA New Zealand

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

16IPv4 routes 100.0% RPKI valid · 93.8% with a route object
17IPv6 routes 100.0% RPKI valid · 94.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS205809, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205809, 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.
66.203.126.0/23 Valid None 673 100% 67
2a09:a381:100::/40 Valid None 635 100% 67
82.21.172.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.29.203.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.29.204.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.29.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.29.206.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.29.207.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.24.36.0/24 Valid RIR databaseRIPE 673 100% 67
94.24.37.0/24 Valid RIR databaseRIPE 673 100% 67
162.208.16.0/24 Valid RIR databaseRIPE 673 100% 67
185.206.24.0/24 Valid RIR databaseRIPE 673 100% 67
185.206.25.0/24 Valid RIR databaseRIPE 673 100% 67
185.206.26.0/24 Valid RIR databaseRIPE 673 100% 67
185.206.27.0/24 Valid RIR databaseRIPE 673 100% 67
217.180.20.0/24 Valid RIR databaseRIPE 673 100% 67
217.180.21.0/24 Valid RIR databaseRIPE 673 100% 67
2a0b:e41:2::/48 Valid RIR databaseRIPE 636 100% 67
2a0b:e43::/40 Valid RIR databaseRIPE 636 100% 67
2a09:a381::/40 Valid RIR databaseRIPE 635 100% 67
2a0b:e40:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e40:2::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e40:3::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e41:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e42:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e43:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:3::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:4::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:5::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:6::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e44:7::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e45:1::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS205809'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 14 are in fix.csv.

  • Route object: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none66.203.126.0/23No route object for it. Add a route object with origin AS205809 in the RIR database for the space.673 of 673
Route object: none2a09:a381:100::/40No route object for it. Add a route object with origin AS205809 in the RIR database for the space.635 of 636

Route objects not announced

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

66.203.126.0/24RIPEInvalid: maxLength
66.203.127.0/24RIPEInvalid: maxLength
82.26.65.0/24RADB, RIPEValid
2a0b:e40::/32RIPENo ROA
2a0b:e41::/32RIPENo ROA
2a0b:e41::/48RIPENo ROA
2a0b:e42::/32RIPENo ROA
2a0b:e43::/32RIPENo ROA
2a0b:e43::/48RIPEInvalid: maxLength
2a0b:e44::/32RIPENo ROA
2a0b:e44:2::/48RIPEValid
2a0b:e45::/32RIPENo 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.