bgpreport

Network · data from 2026-11-12

AS263771 AS263771 - IP NET, C.A.

Registry name: AS263771 - IP NET, C.A., VE · not in PeeringDB

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

Announced routes

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

2803:3980::/32 No ROA None 636 100% 67
200.71.112.0/24 No ROA Other IRR onlyRADB 670 100% 68
200.71.113.0/24 No ROA Other IRR onlyRADB 670 100% 68
200.71.114.0/24 No ROA Other IRR onlyRADB 666 99% 68
200.71.115.0/24 No ROA Other IRR onlyRADB 666 99% 68
204.199.176.0/24 Valid RIR databaseARIN 670 100% 68
200.41.117.0/24 Valid RIR databaseLACNIC, RADB 667 99% 68
201.234.224.0/24 Valid RIR databaseLACNIC 667 99% 68
201.234.235.0/24 Valid RIR databaseLACNIC, RADB 667 99% 68
190.216.241.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68
190.216.244.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68
190.216.251.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68
190.216.253.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68
190.216.254.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68

AS-SET

AS263771 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 10 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none2803:3980::/32No ROA covers it. Add a ROA for AS263771, maxLength 32.636 of 636
Route object: none2803:3980::/32No route object for it. Add a route object with origin AS263771 in the RIR database for the space.636 of 636
ROA: none200.71.112.0/24No ROA covers it. Add a ROA for AS263771, maxLength 24.670 of 673
Route object: RIR200.71.112.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.71.113.0/24No ROA covers it. Add a ROA for AS263771, maxLength 24.670 of 673
Route object: RIR200.71.113.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.71.114.0/24No ROA covers it. Add a ROA for AS263771, maxLength 24.666 of 673
Route object: RIR200.71.114.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.71.115.0/24No ROA covers it. Add a ROA for AS263771, maxLength 24.666 of 673
Route object: RIR200.71.115.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

Every route object with origin AS263771 is announced.

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.