bgpreport

Network · data from 2026-11-12

AS264919 AS264919 - Ultraceu Ltda

Registry name: AS264919 - Ultraceu Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264919, 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.
168.228.228.0/22 No ROA Other IRR onlyRADB, TC 673 100% 67
168.228.228.0/23 No ROA Other IRR onlyTC 672 100% 67
168.228.229.0/24 No ROA Other IRR onlyTC 672 100% 67
168.228.228.0/24 No ROA Other IRR onlyTC 668 99% 66
168.228.231.0/24 No ROA Other IRR onlyTC 668 99% 66
168.228.230.0/24 No ROA Other IRR onlyTC 667 99% 66
2804:2fe4::/32 No ROA Other IRR onlyRADB, TC 631 99% 68

AS-SET

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

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none168.228.228.0/22No ROA covers it. Add a ROA for AS264919, maxLength 22.673 of 673
Route object: RIR168.228.228.0/22Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
ROA: none168.228.228.0/23No ROA covers it. Add a ROA for AS264919, maxLength 23.672 of 673
Route object: RIR168.228.228.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none168.228.229.0/24No ROA covers it. Add a ROA for AS264919, maxLength 24.672 of 673
Route object: RIR168.228.229.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none168.228.228.0/24No ROA covers it. Add a ROA for AS264919, maxLength 24.668 of 673
Route object: RIR168.228.228.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none168.228.231.0/24No ROA covers it. Add a ROA for AS264919, maxLength 24.668 of 673
Route object: RIR168.228.231.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none168.228.230.0/24No ROA covers it. Add a ROA for AS264919, maxLength 24.667 of 673
Route object: RIR168.228.230.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:2fe4::/32No ROA covers it. Add a ROA for AS264919, maxLength 32.631 of 636
Route object: RIR2804:2fe4::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

168.228.230.0/23TCNo 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.