bgpreport

Network · data from 2026-11-12

AS271596 AS271596 - MaxNet Telecom

Registry name: AS271596 - MaxNet Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271596, 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.
138.99.80.0/24 No ROA Other origin onlycovered by 138.99.80.0/23 672 100% 66
138.99.81.0/24 No ROA Other origin onlycovered by 138.99.80.0/23 668 99% 67
2804:7e00:8000::/33 No ROA Nonecovered by 2804:7e00::/32 636 100% 67
2804:7e00::/33 No ROA Nonecovered by 2804:7e00::/32 635 100% 67
190.9.126.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67

AS-SET

AS271596 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none138.99.80.0/24No ROA covers it. Add a ROA for AS271596, maxLength 24.672 of 673
Route object: none138.99.80.0/24Route objects for it name AS4809, AS264156. A route object for 138.99.80.0/23 with origin AS271596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271596 in the RIR database for the space.672 of 673
ROA: none138.99.81.0/24No ROA covers it. Add a ROA for AS271596, maxLength 24.668 of 673
Route object: none138.99.81.0/24Route objects for it name AS4809, AS264156. A route object for 138.99.80.0/23 with origin AS271596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271596 in the RIR database for the space.668 of 673
ROA: none2804:7e00:8000::/33No ROA covers it. Add a ROA for AS271596, maxLength 33.636 of 636
Route object: none2804:7e00:8000::/33No route object for it. A route object for 2804:7e00::/32 with origin AS271596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271596 in the RIR database for the space.636 of 636
ROA: none2804:7e00::/33No ROA covers it. Add a ROA for AS271596, maxLength 33.635 of 636
Route object: none2804:7e00::/33No route object for it. A route object for 2804:7e00::/32 with origin AS271596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271596 in the RIR database for the space.635 of 636
ROA: none190.9.126.0/24No ROA covers it. Add a ROA for AS271596, maxLength 24.671 of 673
Route object: RIR190.9.126.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

138.99.80.0/23RADB, TCNo ROA
2804:7e00::/32RADB, TCNo 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.