bgpreport

Network · data from 2026-11-12

AS26609 Universal Telecom Ltda.

Registry name: AS26609 - Universal Telecom S.A., BR · PeeringDB

11IPv4 routes 0.0% RPKI valid · 36.4% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No 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 AS26609, seen from no peer

Announced routes

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

189.8.0.0/19 No ROA Nonecovered by 189.8.0.0/18 672 100% 67
189.8.0.0/20 No ROA Nonecovered by 189.8.0.0/18 672 100% 67
189.85.192.0/19 No ROA Nonecovered by 189.85.192.0/18 672 100% 67
189.85.192.0/24 No ROA Nonecovered by 189.85.192.0/18 672 100% 67
189.8.16.0/20 No ROA Nonecovered by 189.8.0.0/18 671 100% 67
200.150.224.0/21 No ROA Nonecovered by 200.150.224.0/20 671 100% 67
200.150.232.0/21 No ROA Nonecovered by 200.150.224.0/20 671 100% 67
2804:137c::/32 No ROA None 636 100% 67
189.8.0.0/18 No ROA Other IRR onlyRADB 672 100% 67
189.85.192.0/18 No ROA Other IRR onlyRADB 672 100% 67
200.143.128.0/19 No ROA Other IRR onlyRADB 671 100% 67
200.150.224.0/20 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS26609'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 24 are in fix.csv.

  • ROA: none12
  • Route object: none8
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none189.8.0.0/19No ROA covers it. Add a ROA for AS26609, maxLength 19.672 of 673
Route object: none189.8.0.0/19No route object for it. A route object for 189.8.0.0/18 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.672 of 673
ROA: none189.8.0.0/20No ROA covers it. Add a ROA for AS26609, maxLength 20.672 of 673
Route object: none189.8.0.0/20No route object for it. A route object for 189.8.0.0/18 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.672 of 673
ROA: none189.85.192.0/19No ROA covers it. Add a ROA for AS26609, maxLength 19.672 of 673
Route object: none189.85.192.0/19No route object for it. A route object for 189.85.192.0/18 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.672 of 673
ROA: none189.85.192.0/24No ROA covers it. Add a ROA for AS26609, maxLength 24.672 of 673
Route object: none189.85.192.0/24No route object for it. A route object for 189.85.192.0/18 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.672 of 673
ROA: none189.8.16.0/20No ROA covers it. Add a ROA for AS26609, maxLength 20.671 of 673
Route object: none189.8.16.0/20No route object for it. A route object for 189.8.0.0/18 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.671 of 673
ROA: none200.150.224.0/21No ROA covers it. Add a ROA for AS26609, maxLength 21.671 of 673
Route object: none200.150.224.0/21No route object for it. A route object for 200.150.224.0/20 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.671 of 673
ROA: none200.150.232.0/21No ROA covers it. Add a ROA for AS26609, maxLength 21.671 of 673
Route object: none200.150.232.0/21No route object for it. A route object for 200.150.224.0/20 with origin AS26609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26609 in the RIR database for the space.671 of 673
ROA: none2804:137c::/32No ROA covers it. Add a ROA for AS26609, maxLength 32.636 of 636
Route object: none2804:137c::/32No route object for it. Add a route object with origin AS26609 in the RIR database for the space.636 of 636
ROA: none189.8.0.0/18No ROA covers it. Add a ROA for AS26609, maxLength 18.672 of 673
Route object: RIR189.8.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none189.85.192.0/18No ROA covers it. Add a ROA for AS26609, maxLength 18.672 of 673
Route object: RIR189.85.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.143.128.0/19No ROA covers it. Add a ROA for AS26609, maxLength 19.671 of 673
Route object: RIR200.143.128.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.150.224.0/20No ROA covers it. Add a ROA for AS26609, maxLength 20.671 of 673
Route object: RIR200.150.224.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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