bgpreport

Network · data from 2026-11-12

AS274768 ULTRANET VALE DO RIBEIRA LTDA

Registry name: AS274768 - ULTRANET VALE DO RIBEIRA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274768, 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:934c::/33 No ROA Nonecovered by 2804:934c::/32 635 100% 67
2804:934c:8000::/33 No ROA Nonecovered by 2804:934c::/32 635 100% 67
2804:934c::/34 No ROA Nonecovered by 2804:934c::/32 27 4%low visibility 13
2804:934c:4000::/34 No ROA Nonecovered by 2804:934c::/32 27 4%low visibility 13
2804:934c:8000::/34 No ROA Nonecovered by 2804:934c::/32 27 4%low visibility 13
2804:934c:c000::/34 No ROA Nonecovered by 2804:934c::/32 27 4%low visibility 13
2804:934c::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS274768'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 14 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2804:934c::/33No ROA covers it. Add a ROA for AS274768, maxLength 33.635 of 636
Route object: none2804:934c::/33No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.635 of 636
ROA: none2804:934c:8000::/33No ROA covers it. Add a ROA for AS274768, maxLength 33.635 of 636
Route object: none2804:934c:8000::/33No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.635 of 636
ROA: none2804:934c::/34No ROA covers it. Add a ROA for AS274768, maxLength 34.27 of 636
Route object: none2804:934c::/34No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.27 of 636
ROA: none2804:934c:4000::/34No ROA covers it. Add a ROA for AS274768, maxLength 34.27 of 636
Route object: none2804:934c:4000::/34No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.27 of 636
ROA: none2804:934c:8000::/34No ROA covers it. Add a ROA for AS274768, maxLength 34.27 of 636
Route object: none2804:934c:8000::/34No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.27 of 636
ROA: none2804:934c:c000::/34No ROA covers it. Add a ROA for AS274768, maxLength 34.27 of 636
Route object: none2804:934c:c000::/34No route object for it. A route object for 2804:934c::/32 with origin AS274768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274768 in the RIR database for the space.27 of 636
ROA: none2804:934c::/32No ROA covers it. Add a ROA for AS274768, maxLength 32.635 of 636
Route object: RIR2804:934c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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