bgpreport

Network · data from 2026-11-12

AS263744 AS263744 - Udasha S.A.

Registry name: AS263744 - Udasha S.A., HN · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS263744, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263744, 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.137.168.0/22 Valid RIR databaseALTDB, LACNIC, RIPE-NONAUTH 673 100% 67
168.228.45.0/24 Valid RIR databaseALTDB, LACNIC 673 100% 67
168.228.46.0/23 Valid RIR databaseALTDB, LACNIC 673 100% 67
170.81.196.0/22 Valid RIR databaseALTDB, LACNIC, RIPE-NONAUTH 673 100% 67
168.196.241.0/24 Valid RIR databaseLACNIC 667 99% 67
131.108.16.0/22 Valid RIR databaseALTDB, LACNIC, RIPE-NONAUTH 666 99% 67
138.94.216.0/22 Valid RIR databaseALTDB, LACNIC, RIPE-NONAUTH 666 99% 67
168.196.240.0/22 Valid RIR databaseALTDB, LACNIC 666 99% 67
2803:5380::/32 Valid RIR databaseALTDB, LACNIC, RIPE-NONAUTH 635 100% 67

AS-SET

AS263744 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 1 are in fix.csv.

  • Route object: not announced1

Route objects not announced

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

168.228.44.0/22ALTDB, RIPE-NONAUTHNo 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.