Network · data from 2026-11-12

AS4995 Comunicaciones Netglobalis S.A

Registry name: AS4995 - Netup S.A., CL · PeeringDB

24IPv4 routes 91.7% RPKI valid · 91.7% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

7Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS4995, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4995, 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.196.184.0/24	Invalid: origin	Other origin only	39 6%low visibility	16
168.196.186.0/24	Invalid: origin	Other origin only	39 6%low visibility	16
200.29.7.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.8.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.9.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.10.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.11.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.24.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.29.28.0/24	Valid	RIR databaseLACNIC, RADB	669 99%	67
200.2.196.0/24	Valid	RIR databaseLACNIC	668 99%	67
200.2.197.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.206.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.207.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.209.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.214.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.216.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.246.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.29.76.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.29.82.0/24	Valid	RIR databaseLACNIC	663 99%	67
200.2.193.0/24	Valid	RIR databaseLACNIC	13 2%low visibility	8
200.2.198.0/24	Valid	RIR databaseLACNIC	13 2%low visibility	8
200.2.199.0/24	Valid	RIR databaseLACNIC	13 2%low visibility	8
200.2.215.0/24	Valid	RIR databaseLACNIC	13 2%low visibility	8
200.2.222.0/24	Valid	RIR databaseLACNIC	13 2%low visibility	8

168.196.184.0/24

Invalid: origin

Other origin only

39 6%low visibility

168.196.186.0/24

Invalid: origin

Other origin only

39 6%low visibility

200.29.7.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.8.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.9.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.10.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.11.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.24.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.29.28.0/24

Valid

RIR databaseLACNIC, RADB

669 99%

200.2.196.0/24

Valid

RIR databaseLACNIC

668 99%

200.2.197.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.206.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.207.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.209.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.214.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.216.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.246.0/24

Valid

RIR databaseLACNIC

663 99%

200.29.76.0/24

Valid

RIR databaseLACNIC

663 99%

200.29.82.0/24

Valid

RIR databaseLACNIC

663 99%

200.2.193.0/24

Valid

RIR databaseLACNIC

13 2%low visibility

200.2.198.0/24

Valid

RIR databaseLACNIC

13 2%low visibility

200.2.199.0/24

Valid

RIR databaseLACNIC

13 2%low visibility

200.2.215.0/24

Valid

RIR databaseLACNIC

13 2%low visibility

200.2.222.0/24

Valid

RIR databaseLACNIC

13 2%low visibility

AS-SET

AS4995'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 5 are in fix.csv.

ROA: origin2
Route object: none2
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	168.196.184.0/24	ROAs covering it name AS10778, not AS4995. If AS4995 should announce it, add a ROA for AS4995.	39 of 673
Route object: none	168.196.184.0/24	Route objects for it name AS10778. Add a route object with origin AS4995 in the RIR database for the space.	39 of 673
ROA: origin	168.196.186.0/24	ROAs covering it name AS10778, not AS4995. If AS4995 should announce it, add a ROA for AS4995.	39 of 673
Route object: none	168.196.186.0/24	Route objects for it name AS10778. Add a route object with origin AS4995 in the RIR database for the space.	39 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

168.196.184.0/24

ROAs covering it name AS10778, not AS4995. If AS4995 should announce it, add a ROA for AS4995.

39 of 673

Route object: none

168.196.184.0/24

Route objects for it name AS10778. Add a route object with origin AS4995 in the RIR database for the space.

39 of 673

ROA: origin

168.196.186.0/24

ROAs covering it name AS10778, not AS4995. If AS4995 should announce it, add a ROA for AS4995.

39 of 673

Route object: none

168.196.186.0/24

Route objects for it name AS10778. Add a route object with origin AS4995 in the RIR database for the space.

39 of 673

Route objects not announced

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


200.2.224.0/24	LACNIC	Valid

200.2.224.0/24

LACNIC

Valid

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.