bgpreport

Network · data from 2026-11-12

AS269986 SERVICIOS PROFESIONALES WICOM

Registry name: AS269986 - SERVICIOS PROFESIONALES WICOM S.A.S., CO · PeeringDB

9IPv4 routes 100.0% RPKI valid · 55.6% with a route object
15IPv6 routes 80.0% RPKI valid · 20.0% with a route object
3RPKI invalid 3 origin · 0 maxLength
0No ROA 16 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS269986, seen from no peer

Announced routes

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

2800:310:1001::/48 Invalid: origin None 46 7%low visibility 30
2800:310:1006::/48 Invalid: origin None 46 7%low visibility 30
2800:310:100a::/48 Invalid: origin None 46 7%low visibility 30
40.27.89.0/24 Valid Nonecovered by 40.27.88.0/21 670 100% 67
40.27.90.0/24 Valid Nonecovered by 40.27.88.0/21 670 100% 67
40.27.91.0/24 Valid Nonecovered by 40.27.88.0/21 670 100% 67
201.49.129.0/24 Valid Nonecovered by 201.49.128.0/22 670 100% 67
2803:5ee0:b::/48 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:c::/48 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:128::/48 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:129::/48 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:4000::/40 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:4100::/40 Valid Nonecovered by 2803:5ee0::/32 631 99% 67
2803:5ee0:a::/48 Valid Nonecovered by 2803:5ee0::/32 630 99% 67
2803:5ee0:127::/48 Valid Nonecovered by 2803:5ee0::/32 630 99% 67
2803:5ee0:2000::/35 Valid Nonecovered by 2803:5ee0::/32 630 99% 67
40.27.88.0/24 Valid Other IRR onlyRADB 670 100% 67
40.27.92.0/24 Valid Other IRR onlyRADB 670 100% 67
40.27.93.0/24 Valid Other IRR onlyRADB 670 100% 67
201.49.128.0/24 Valid Other IRR onlyRADB 670 100% 67
2803:5ee0:d::/48 Valid Other IRR onlyRADB 632 99% 69
2803:5ee0:130::/48 Valid Other IRR onlyRADB 632 99% 69
2803:5ee0:4200::/40 Valid Other IRR onlyRADB 632 99% 69
201.49.128.0/22 Valid RIR databaseLACNIC, RADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS269986: LACNIC::AS269986:AS-WICOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS269986 isn't in the set, or no route object for AS269986 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS269986 in itNot covered
LACNIC::AS269986:AS-WICOM LACNIC 1112 Yes 3

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

  • ROA: origin3
  • Route object: none16
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2800:310:1001::/48ROAs covering it name AS18678, not AS269986. If AS269986 should announce it, add a ROA for AS269986.46 of 636
Route object: none2800:310:1001::/48No route object for it. Add a route object with origin AS269986 in the RIR database for the space.46 of 636
ROA: origin2800:310:1006::/48ROAs covering it name AS18678, not AS269986. If AS269986 should announce it, add a ROA for AS269986.46 of 636
Route object: none2800:310:1006::/48No route object for it. Add a route object with origin AS269986 in the RIR database for the space.46 of 636
ROA: origin2800:310:100a::/48ROAs covering it name AS18678, not AS269986. If AS269986 should announce it, add a ROA for AS269986.46 of 636
Route object: none2800:310:100a::/48No route object for it. Add a route object with origin AS269986 in the RIR database for the space.46 of 636
Route object: none40.27.89.0/24No route object for it. A route object for 40.27.88.0/21 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.670 of 673
Route object: none40.27.90.0/24No route object for it. A route object for 40.27.88.0/21 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.670 of 673
Route object: none40.27.91.0/24No route object for it. A route object for 40.27.88.0/21 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.670 of 673
Route object: none201.49.129.0/24No route object for it. A route object for 201.49.128.0/22 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.670 of 673
Route object: none2803:5ee0:b::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:c::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:128::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:129::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:4000::/40No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:4100::/40No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.631 of 636
Route object: none2803:5ee0:a::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.630 of 636
Route object: none2803:5ee0:127::/48No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.630 of 636
Route object: none2803:5ee0:2000::/35No route object for it. A route object for 2803:5ee0::/32 with origin AS269986 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269986 in the RIR database for the space.630 of 636
Route object: RIR40.27.88.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR40.27.92.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR40.27.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.49.128.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2803:5ee0:d::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2803:5ee0:130::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2803:5ee0:4200::/40Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

40.27.88.0/21ARIN, RADBValid
190.90.22.208/28LACNICValid
190.90.38.0/24LACNIC, RADBValid
2803:5ee0::/32LACNIC, RADBValid

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.