bgpreport

Network · data from 2026-11-12

AS61712 YUPNET TELECOMUNICACOES

Registry name: AS61712 - YUPNET TELECOMUNICACOES LTDA, BR · PeeringDB

12IPv4 routes 100.0% RPKI valid · 66.7% 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 AS61712, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61712, 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.174.120.0/24 Valid Nonecovered by 45.174.120.0/22 670 100% 66
45.174.123.0/24 Valid Nonecovered by 45.174.120.0/22 670 100% 66
131.72.44.0/24 Valid Nonecovered by 131.72.44.0/23 670 100% 66
131.72.47.0/24 Valid Nonecovered by 131.72.46.0/23 670 100% 66
2804:1b28::/33 Valid Nonecovered by 2804:1b28::/32 352 55% 64
2804:1b28:8000::/33 Valid Nonecovered by 2804:1b28::/32 352 55% 64
45.174.120.0/22 Valid Other IRR onlyRADB 671 100% 66
131.72.44.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
45.174.121.0/24 Valid Other IRR onlyRADB 670 100% 66
45.174.122.0/24 Valid Other IRR onlyRADB 670 100% 66
131.72.44.0/23 Valid Other IRR onlyRADB 670 100% 66
131.72.45.0/24 Valid Other IRR onlyRADB 670 100% 66
131.72.46.0/23 Valid Other IRR onlyRADB 670 100% 66
131.72.46.0/24 Valid Other IRR onlyRADB 670 100% 66
2804:1b28::/32 Valid Other IRR onlyRADB, TC 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS61712: AS61712:AS-YUPNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61712 isn't in the set, or no route object for AS61712 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS61712 in itNot covered
AS61712:AS-YUPNET ALTDB 6243 Yes 0

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

  • Route object: none6
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: none45.174.120.0/24No route object for it. A route object for 45.174.120.0/22 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.670 of 673
Route object: none45.174.123.0/24No route object for it. A route object for 45.174.120.0/22 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.670 of 673
Route object: none131.72.44.0/24No route object for it. A route object for 131.72.44.0/23 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.670 of 673
Route object: none131.72.47.0/24No route object for it. A route object for 131.72.46.0/23 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.670 of 673
Route object: none2804:1b28::/33No route object for it. A route object for 2804:1b28::/32 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.352 of 636
Route object: none2804:1b28:8000::/33No route object for it. A route object for 2804:1b28::/32 with origin AS61712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61712 in the RIR database for the space.352 of 636
Route object: RIR45.174.120.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.72.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.174.121.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.174.122.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.72.44.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.72.45.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.72.46.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.72.46.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:1b28::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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