bgpreport

Network · data from 2026-11-12

AS263766 Datalink SRL

Registry name: AS263766 - Datalink SRL, AR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 14.3% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 13 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS263766, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263766, 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.

131.196.36.0/22 Valid Other origin only 672 100% 67
131.196.36.0/24 Valid None 672 100% 67
131.196.37.0/24 Valid None 672 100% 67
131.196.38.0/24 Valid None 672 100% 67
170.83.108.0/24 Valid Nonecovered by 170.83.108.0/22 672 100% 67
170.83.109.0/24 Valid Nonecovered by 170.83.108.0/22 672 100% 67
170.83.110.0/24 Valid Nonecovered by 170.83.108.0/22 672 100% 67
170.83.111.0/24 Valid Nonecovered by 170.83.108.0/22 672 100% 67
190.103.84.0/24 Valid Nonecovered by 190.103.84.0/22 671 100% 67
190.103.85.0/24 Valid Nonecovered by 190.103.84.0/22 671 100% 67
190.103.86.0/24 Valid Nonecovered by 190.103.84.0/22 671 100% 67
190.103.87.0/24 Valid Nonecovered by 190.103.84.0/22 671 100% 67
2800:d00:1000::/48 Valid Nonecovered by 2800:d00::/32 632 99% 67
190.103.84.0/22 Valid RIR databaseLACNIC 671 100% 67
170.83.108.0/22 Valid RIR databaseLACNIC 670 100% 67
2800:d00::/32 Valid RIR databaseLACNIC 633 100% 69

AS-SET

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

  • Route object: none13
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none131.196.36.0/22Route objects for it name AS265773, AS271970. Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none131.196.36.0/24No route object for it. Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none131.196.37.0/24No route object for it. Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none131.196.38.0/24No route object for it. Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none170.83.108.0/24No route object for it. A route object for 170.83.108.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none170.83.109.0/24No route object for it. A route object for 170.83.108.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none170.83.110.0/24No route object for it. A route object for 170.83.108.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none170.83.111.0/24No route object for it. A route object for 170.83.108.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.672 of 673
Route object: none190.103.84.0/24No route object for it. A route object for 190.103.84.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.671 of 673
Route object: none190.103.85.0/24No route object for it. A route object for 190.103.84.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.671 of 673
Route object: none190.103.86.0/24No route object for it. A route object for 190.103.84.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.671 of 673
Route object: none190.103.87.0/24No route object for it. A route object for 190.103.84.0/22 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.671 of 673
Route object: none2800:d00:1000::/48No route object for it. A route object for 2800:d00::/32 with origin AS263766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263766 in the RIR database for the space.632 of 636

Route objects not announced

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

131.196.188.0/22LACNICValid
2803:dbc0::/32LACNICValid

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.