bgpreport

Network · data from 2026-11-12

AS271726 AS271726 - UNIPONTE PROVEDOR DE INTERNET LTDA

Registry name: AS271726 - UNIPONTE PROVEDOR DE INTERNET LTDA, BR · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 14.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 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS271726, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271726, 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.
201.216.88.0/23 Valid Nonecovered by 201.216.88.0/22 671 100% 66
201.216.88.0/24 Valid Nonecovered by 201.216.88.0/22 671 100% 66
201.216.89.0/24 Valid Nonecovered by 201.216.88.0/22 671 100% 66
201.216.90.0/23 Valid Nonecovered by 201.216.88.0/22 671 100% 66
201.216.90.0/24 Valid Nonecovered by 201.216.88.0/22 671 100% 66
201.216.91.0/24 Valid Nonecovered by 201.216.88.0/22 671 100% 66
2804:800c::/33 Valid Nonecovered by 2804:800c::/32 633 100% 67
2804:800c:8000::/33 Valid Nonecovered by 2804:800c::/32 633 100% 67
201.216.88.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
2804:800c::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS271726 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 10 are in fix.csv.

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none201.216.88.0/23No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none201.216.88.0/24No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none201.216.89.0/24No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none201.216.90.0/23No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none201.216.90.0/24No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none201.216.91.0/24No route object for it. A route object for 201.216.88.0/22 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.671 of 673
Route object: none2804:800c::/33No route object for it. A route object for 2804:800c::/32 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.633 of 636
Route object: none2804:800c:8000::/33No route object for it. A route object for 2804:800c::/32 with origin AS271726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271726 in the RIR database for the space.633 of 636
Route object: RIR201.216.88.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:800c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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