bgpreport

Network · data from 2026-11-12

AS264056 Uli Telecom

Registry name: AS264056 - ULI TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264056, 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.
143.202.36.0/23 No ROA Nonecovered by 143.202.36.0/22 671 100% 67
143.202.38.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
143.202.39.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
143.202.36.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 67
143.202.37.0/24 No ROA Other IRR onlyALTDB, RADB 659 98% 66
2804:2a18::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS264056'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 13 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none143.202.36.0/23No ROA covers it. Add a ROA for AS264056, maxLength 23.671 of 673
Route object: none143.202.36.0/23No route object for it. A route object for 143.202.36.0/22 with origin AS264056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264056 in the RIR database for the space.671 of 673
ROA: none143.202.38.0/24No ROA covers it. Add a ROA for AS264056, maxLength 24.671 of 673
Route object: RIR143.202.38.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none143.202.39.0/24No ROA covers it. Add a ROA for AS264056, maxLength 24.671 of 673
Route object: RIR143.202.39.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none143.202.36.0/24No ROA covers it. Add a ROA for AS264056, maxLength 24.669 of 673
Route object: RIR143.202.36.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none143.202.37.0/24No ROA covers it. Add a ROA for AS264056, maxLength 24.659 of 673
Route object: RIR143.202.37.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.659 of 673
ROA: none2804:2a18::/32No ROA covers it. Add a ROA for AS264056, maxLength 32.636 of 636
Route object: RIR2804:2a18::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

143.202.36.0/22ALTDB, RADB, 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.