bgpreport

Network · data from 2026-11-12

AS268084 MAXIMA INTERNET BANDA LARGA

Registry name: AS268084 - MAXIMA INTERNET BANDA LARGA, BR · PeeringDB

3IPv4 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 4 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS268084, seen from no peer

Announced routes

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

45.168.244.0/23 Valid Nonecovered by 45.168.244.0/22 672 100% 67
45.168.246.0/23 Valid Nonecovered by 45.168.244.0/22 672 100% 67
2804:57c0::/33 Valid Nonecovered by 2804:57c0::/32 636 100% 67
2804:57c0:8000::/33 Valid Nonecovered by 2804:57c0::/32 636 100% 67
45.168.244.0/22 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
2804:57c0::/32 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS268084'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 6 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.168.244.0/23No route object for it. A route object for 45.168.244.0/22 with origin AS268084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268084 in the RIR database for the space.672 of 673
Route object: none45.168.246.0/23No route object for it. A route object for 45.168.244.0/22 with origin AS268084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268084 in the RIR database for the space.672 of 673
Route object: none2804:57c0::/33No route object for it. A route object for 2804:57c0::/32 with origin AS268084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268084 in the RIR database for the space.636 of 636
Route object: none2804:57c0:8000::/33No route object for it. A route object for 2804:57c0::/32 with origin AS268084 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268084 in the RIR database for the space.636 of 636
Route object: RIR45.168.244.0/22Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:57c0::/32Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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