bgpreport

Network · data from 2026-11-12

AS7087 AS7087 - Administracion de Redes Colomsat S.A.

Registry name: AS7087 - Administracion de Redes Colomsat S.A., CO · not in PeeringDB

14IPv4 routes 7.1% RPKI valid · 7.1% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
6RPKI invalid 6 origin · 0 maxLength
7No ROA 13 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS7087, seen from no peer

Announced routes

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

200.13.195.0/24 Invalid: origin Other origin only 74 11% 33
200.13.203.0/24 Invalid: origin Other origin only 73 11% 33
200.13.192.0/19 Invalid: origin Other origin only 27 4%low visibility 10
200.13.193.0/24 Invalid: origin Other origin only 1 0%low visibility 1
200.13.205.0/24 Invalid: origin Other origin only 1 0%low visibility 1
200.13.212.0/24 Invalid: origin Other origin only 1 0%low visibility 1
200.62.10.0/24 No ROA None 8 1%low visibility 7
200.62.43.0/24 No ROA None 7 1%low visibility 6
200.62.60.0/24 No ROA None 7 1%low visibility 6
200.62.61.0/24 No ROA None 7 1%low visibility 6
200.62.62.0/24 No ROA None 7 1%low visibility 6
200.62.63.0/24 No ROA None 7 1%low visibility 6
200.62.60.0/22 No ROA Other origin only 6 1%low visibility 5
2803:4860::/32 Valid RIR databaseLACNIC 630 99% 69
200.23.137.0/24 Valid RIR databaseLACNIC 577 86% 67

AS-SET

AS7087 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 45 are in fix.csv.

  • ROA: origin6
  • ROA: none7
  • Route object: none13
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: origin200.13.195.0/24ROAs covering it name AS41347, AS397006, not AS7087. If AS7087 should announce it, add a ROA for AS7087.74 of 673
Route object: none200.13.195.0/24Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.74 of 673
ROA: origin200.13.203.0/24ROAs covering it name AS41347, AS399486, not AS7087. If AS7087 should announce it, add a ROA for AS7087.73 of 673
Route object: none200.13.203.0/24Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.73 of 673
ROA: origin200.13.192.0/19ROAs covering it name AS41347, not AS7087. If AS7087 should announce it, add a ROA for AS7087.27 of 673
Route object: none200.13.192.0/19Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.27 of 673
ROA: origin200.13.193.0/24ROAs covering it name AS41347, AS397006, not AS7087. If AS7087 should announce it, add a ROA for AS7087.1 of 673
Route object: none200.13.193.0/24Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.1 of 673
ROA: origin200.13.205.0/24ROAs covering it name AS41347, AS399486, not AS7087. If AS7087 should announce it, add a ROA for AS7087.1 of 673
Route object: none200.13.205.0/24Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.1 of 673
ROA: origin200.13.212.0/24ROAs covering it name AS41347, not AS7087. If AS7087 should announce it, add a ROA for AS7087.1 of 673
Route object: none200.13.212.0/24Route objects for it name AS41347. Add a route object with origin AS7087 in the RIR database for the space.1 of 673
ROA: none200.62.10.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.8 of 673
Route object: none200.62.10.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.8 of 673
ROA: none200.62.43.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.7 of 673
Route object: none200.62.43.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.7 of 673
ROA: none200.62.60.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.7 of 673
Route object: none200.62.60.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.7 of 673
ROA: none200.62.61.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.7 of 673
Route object: none200.62.61.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.7 of 673
ROA: none200.62.62.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.7 of 673
Route object: none200.62.62.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.7 of 673
ROA: none200.62.63.0/24No ROA covers it. Add a ROA for AS7087, maxLength 24.7 of 673
Route object: none200.62.63.0/24No route object for it. Add a route object with origin AS7087 in the RIR database for the space.7 of 673
ROA: none200.62.60.0/22No ROA covers it. Add a ROA for AS7087, maxLength 22.6 of 673
Route object: none200.62.60.0/22Route objects for it name AS18747. Add a route object with origin AS7087 in the RIR database for the space.6 of 673

Route objects not announced

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

200.13.208.0/24LACNICValid
200.13.209.0/24LACNICValid
200.13.218.0/24LACNICValid
200.13.220.0/24LACNIC, RADBValid
200.33.170.0/24LACNICValid
200.33.187.0/24LACNICValid
200.34.30.0/24LACNICValid
200.34.31.0/24LACNICValid
200.34.135.0/24LACNICValid
200.34.156.0/24LACNICValid
2806:3d3::/32LACNICValid
2a14:7584:4465::/48RIPEInvalid: origin
2a14:7584:4469::/48RIPEInvalid: origin
2a14:7584:446c::/48RIPEInvalid: origin
2a14:7584:4472::/48RIPEInvalid: origin
2a14:7584:4475::/48RIPEInvalid: origin
2a14:7584:4480::/48RIPEInvalid: origin
2a14:7584:44c4::/48RIPEInvalid: origin
2a14:7584:44db::/48RIPEInvalid: origin

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.