bgpreport

Network · data from 2026-11-12

AS274664 AS274664 - UBBY INTERNET LTDA

Registry name: AS274664 - UBBY INTERNET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274664, 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:91c8::/36 No ROA Nonecovered by 2804:91c8::/32 634 100% 67
2804:91c8:1000::/36 No ROA Nonecovered by 2804:91c8::/32 634 100% 67
2804:91c8:2000::/36 No ROA Nonecovered by 2804:91c8::/32 634 100% 67
2804:91c8:4000::/36 No ROA Nonecovered by 2804:91c8::/32 589 93% 67
190.115.209.0/24 No ROA Other origin only 415 62% 65

AS-SET

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

  • ROA: none5
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:91c8::/36No ROA covers it. Add a ROA for AS274664, maxLength 36.634 of 636
Route object: none2804:91c8::/36No route object for it. A route object for 2804:91c8::/32 with origin AS274664 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274664 in the RIR database for the space.634 of 636
ROA: none2804:91c8:1000::/36No ROA covers it. Add a ROA for AS274664, maxLength 36.634 of 636
Route object: none2804:91c8:1000::/36No route object for it. A route object for 2804:91c8::/32 with origin AS274664 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274664 in the RIR database for the space.634 of 636
ROA: none2804:91c8:2000::/36No ROA covers it. Add a ROA for AS274664, maxLength 36.634 of 636
Route object: none2804:91c8:2000::/36No route object for it. A route object for 2804:91c8::/32 with origin AS274664 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274664 in the RIR database for the space.634 of 636
ROA: none2804:91c8:4000::/36No ROA covers it. Add a ROA for AS274664, maxLength 36.589 of 636
Route object: none2804:91c8:4000::/36No route object for it. A route object for 2804:91c8::/32 with origin AS274664 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274664 in the RIR database for the space.589 of 636
ROA: none190.115.209.0/24No ROA covers it. Add a ROA for AS274664, maxLength 24.415 of 673
Route object: none190.115.209.0/24Route objects for it name AS270844. Add a route object with origin AS274664 in the RIR database for the space.415 of 673

Route objects not announced

Route objects with origin AS274664 whose prefix no peer sees AS274664 announce. Many are kept on purpose (backup routes, space announced only in some places).

2804:91c8::/32TCNo ROA

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.