bgpreport

Network · data from 2026-11-12

AS273500 YPN TECNOLOGIA LTDA

Registry name: AS273500 - YPN TECNOLOGIA LTDA, BR · 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 AS273500, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273500, 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:8f98::/33 Valid Nonecovered by 2804:8f98::/32 350 55% 65
2804:8f98:8000::/33 Valid Nonecovered by 2804:8f98::/32 350 55% 65
186.227.69.0/24 Valid Nonecovered by 186.227.68.0/22 208 31% 56
186.227.70.0/24 Valid Nonecovered by 186.227.68.0/22 208 31% 56
186.227.71.0/24 Valid Nonecovered by 186.227.68.0/22 208 31% 56
186.227.68.0/24 Valid Nonecovered by 186.227.68.0/22 207 31% 56
186.227.68.0/23 Valid Nonecovered by 186.227.68.0/22 206 31% 56
186.227.70.0/23 Valid Nonecovered by 186.227.68.0/22 206 31% 56
186.227.68.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
2804:8f98::/32 Valid Other IRR onlyRADB, TC 634 100% 69

AS-SET

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

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2804:8f98::/33No route object for it. A route object for 2804:8f98::/32 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.350 of 636
Route object: none2804:8f98:8000::/33No route object for it. A route object for 2804:8f98::/32 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.350 of 636
Route object: none186.227.69.0/24No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.208 of 673
Route object: none186.227.70.0/24No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.208 of 673
Route object: none186.227.71.0/24No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.208 of 673
Route object: none186.227.68.0/24No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.207 of 673
Route object: none186.227.68.0/23No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.206 of 673
Route object: none186.227.70.0/23No route object for it. A route object for 186.227.68.0/22 with origin AS273500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273500 in the RIR database for the space.206 of 673
Route object: RIR186.227.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:8f98::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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