bgpreport

Network · data from 2026-11-12

AS265240 ULTRA NET SERVICOS EM INTERNET LTDA

Registry name: AS265240 - NET GUIBOR, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265240, 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.0.0.0/24 No ROA Other IRR onlyRADB 667 99% 67
168.0.1.0/24 No ROA Other IRR onlyRADB 667 99% 67
168.0.2.0/24 No ROA Other IRR onlyRADB, TC 667 99% 67
2804:2cbc::/35 No ROA Other IRR onlyRADB 630 99% 69
2804:2cbc::/36 No ROA Other IRR onlyRADB 630 99% 69
2804:2cbc:1000::/36 No ROA Other IRR onlyRADB 630 99% 69

AS-SET

AS265240'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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none168.0.0.0/24No ROA covers it. Add a ROA for AS265240, maxLength 24.667 of 673
Route object: RIR168.0.0.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none168.0.1.0/24No ROA covers it. Add a ROA for AS265240, maxLength 24.667 of 673
Route object: RIR168.0.1.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none168.0.2.0/24No ROA covers it. Add a ROA for AS265240, maxLength 24.667 of 673
Route object: RIR168.0.2.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:2cbc::/35No ROA covers it. Add a ROA for AS265240, maxLength 35.630 of 636
Route object: RIR2804:2cbc::/35Route object only in RADB. Add it in the RIR database for the space.630 of 636
ROA: none2804:2cbc::/36No ROA covers it. Add a ROA for AS265240, maxLength 36.630 of 636
Route object: RIR2804:2cbc::/36Route object only in RADB. Add it in the RIR database for the space.630 of 636
ROA: none2804:2cbc:1000::/36No ROA covers it. Add a ROA for AS265240, maxLength 36.630 of 636
Route object: RIR2804:2cbc:1000::/36Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

168.0.0.0/22RADBNo ROA
168.0.0.0/23RADB, TCNo ROA
168.0.2.0/23RADBNo ROA
2804:2cbc::/32RADB, TCNo 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.