bgpreport

Network · data from 2026-11-12

AS267398 MEGA IP CONNECT

Registry name: AS267398 - mega ip connect, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267398, 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.
2804:4ce0::/33 Valid Nonecovered by 2804:4ce0::/32 352 55% 64
2804:4ce0:8000::/33 Valid Nonecovered by 2804:4ce0::/32 352 55% 64
45.235.22.0/23 Valid Nonecovered by 45.235.20.0/22 204 30% 54
205.164.248.0/23 Valid Nonecovered by 205.164.248.0/22 204 30% 54
205.164.250.0/23 Valid Nonecovered by 205.164.248.0/22 204 30% 54
45.235.20.0/23 Valid Nonecovered by 45.235.20.0/22 203 30% 54
45.235.20.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
205.164.248.0/22 Valid Other IRR onlyRADB 669 99% 67
2804:4ce0::/32 Valid Other IRR onlyTC 635 100% 67

AS-SET

AS267398'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 9 are in fix.csv.

  • Route object: none6
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2804:4ce0::/33No route object for it. A route object for 2804:4ce0::/32 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.352 of 636
Route object: none2804:4ce0:8000::/33No route object for it. A route object for 2804:4ce0::/32 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.352 of 636
Route object: none45.235.22.0/23No route object for it. A route object for 45.235.20.0/22 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.204 of 673
Route object: none205.164.248.0/23No route object for it. A route object for 205.164.248.0/22 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.204 of 673
Route object: none205.164.250.0/23No route object for it. A route object for 205.164.248.0/22 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.204 of 673
Route object: none45.235.20.0/23No route object for it. A route object for 45.235.20.0/22 with origin AS267398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267398 in the RIR database for the space.203 of 673
Route object: RIR45.235.20.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR205.164.248.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4ce0::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS267398 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.