bgpreport

Network · data from 2026-11-12

AS19114 Otecel

Registry name: AS19114 - Otecel S.A., EC · PeeringDB

45IPv4 routes 100.0% RPKI valid · 100.0% with a route object
52IPv6 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
3Low visibility seen by under 10% of full-table peers
40Route objects not announced registered with origin AS19114, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS19114, 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.
181.198.23.0/24 Valid Other IRR onlyRADB 25 4%low visibility 18
181.188.192.0/18 Valid RIR databaseLACNIC 671 100% 67
181.188.192.0/20 Valid RIR databaseLACNIC 671 100% 67
181.188.192.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.194.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.224.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.226.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.232.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.240.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.242.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.243.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.244.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.245.0/24 Valid RIR databaseLACNIC 671 100% 67
181.188.248.0/24 Valid RIR databaseLACNIC 671 100% 67
186.65.0.0/18 Valid RIR databaseLACNIC 671 100% 67
186.65.32.0/19 Valid RIR databaseLACNIC 671 100% 67
200.7.192.0/20 Valid RIR databaseLACNIC 670 100% 67
200.7.192.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.193.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.194.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.195.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.204.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.208.0/20 Valid RIR databaseLACNIC 670 100% 67
200.7.221.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.224.0/21 Valid RIR databaseLACNIC 670 100% 67
200.7.224.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.226.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.228.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.236.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.237.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.238.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.239.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.240.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.242.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.243.0/24 Valid RIR databaseLACNIC 670 100% 67
200.7.244.0/22 Valid RIR databaseLACNIC 670 100% 67
200.7.248.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.252.0/23 Valid RIR databaseLACNIC 670 100% 67
200.7.254.0/23 Valid RIR databaseLACNIC 670 100% 67
200.24.192.0/19 Valid RIR databaseLACNIC 670 100% 67
200.24.208.0/20 Valid RIR databaseLACNIC 670 100% 67
200.24.210.0/24 Valid RIR databaseLACNIC 670 100% 67
200.24.217.0/24 Valid RIR databaseLACNIC 670 100% 67
200.24.192.0/20 Valid RIR databaseLACNIC 667 99% 67
2800:830::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:1000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:2000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:3000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:4000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:5000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:6000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:7000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:8000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:8032::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:8035::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:8036::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:8037::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:803c::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:80e1::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:9000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:a000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:b000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:c000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:d000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:e000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:e007::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:e012::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:e013::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:e014::/48 Valid RIR databaseLACNIC 636 100% 67
2800:830:f000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:1000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:2000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:3000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:4000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:5000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:6000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:7000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:8000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:9000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:a000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:b000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:c000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:d000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:e000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:831:f000::/36 Valid RIR databaseLACNIC 636 100% 67
2800:830:802e::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:802f::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:803d::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:804d::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:80a7::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:80ac::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:80ad::/48 Valid RIR databaseLACNIC 635 100% 67
2800:830:80ef::/48 Valid RIR databaseLACNIC 635 100% 67
200.7.212.0/24 Valid RIR databaseLACNIC 482 72% 67
2800:830:8034::/48 Valid RIR databaseLACNIC 3 0%low visibility 3
2800:830:80aa::/48 Valid RIR databaseLACNIC 2 0%low visibility 2

AS-SET

AS19114'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 41 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
Route object: RIR181.198.23.0/24Route object only in RADB. Add it in the RIR database for the space.25 of 673

Route objects not announced

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

157.100.118.0/24RADBValid
181.188.195.0/24LACNICValid
181.188.200.0/24LACNICValid
181.188.201.0/24LACNICValid
181.188.225.0/24LACNICValid
181.188.227.0/24LACNICValid
181.188.235.0/24LACNICValid
181.188.237.0/24LACNICValid
181.188.251.0/24LACNICValid
186.65.35.0/24LACNICValid
200.7.209.0/24LACNICValid
200.7.210.0/24LACNICValid
200.7.211.0/24LACNICValid
200.7.218.0/24LACNICValid
200.7.219.0/24LACNICValid
200.7.232.0/22LACNICValid
200.7.234.0/24LACNICValid
200.7.246.0/24LACNICValid
200.7.247.0/24LACNICValid
200.7.251.0/24LACNICValid
200.24.192.0/24LACNICValid
200.24.200.0/24LACNICValid
200.24.201.0/24LACNICValid
200.24.204.0/24LACNICValid
200.24.220.0/24LACNICValid
2800:830:a7::/48LACNICValid
2800:830:8039::/48LACNICValid
2800:830:8081:81::/64LACNICValid
2800:830:80a6:a6::/64LACNICValid
2800:830:80a9::/48LACNICValid
2800:830:80ee::/48LACNICValid
2800:830:80f0::/48LACNICValid
2800:830:e003::/48LACNICValid
2800:830:e004::/48LACNICValid
2800:830:e005::/48LACNICValid
2800:830:e006::/48LACNICValid
2800:830:e008::/48LACNICValid
2803:26e0::/32LACNICValid
2803:26e0:5000::/40LACNICValid
2803:26e0:5200::/40LACNICValid

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.