bgpreport

Network · data from 2026-11-12

AS214413 SecureLink

Registry name: SecureLink WYOCORE TECHNOLOGIES LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214413, 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.
195.40.82.0/24 Valid Nonecovered by 195.40.82.0/23 672 100% 67
195.40.83.0/24 Valid Nonecovered by 195.40.82.0/23 672 100% 67
195.40.94.0/24 Valid Nonecovered by 195.40.94.0/23 672 100% 67
195.40.95.0/24 Valid Nonecovered by 195.40.94.0/23 672 100% 67
156.229.56.0/23 Valid Nonecovered by 156.229.56.0/22 671 100% 67
156.229.58.0/23 Valid Nonecovered by 156.229.56.0/22 671 100% 67
156.239.128.0/23 Valid Nonecovered by 156.239.128.0/22 671 100% 67
156.239.130.0/23 Valid Nonecovered by 156.239.128.0/22 671 100% 67
154.193.168.0/22 Valid Other IRR onlyRADB 671 100% 67
154.193.176.0/22 Valid Other IRR onlyRADB 671 100% 67
156.225.52.0/22 Valid Other IRR onlyRADB 671 100% 67
156.226.200.0/22 Valid Other IRR onlyRADB 671 100% 67
156.227.52.0/22 Valid Other IRR onlyRADB 671 100% 67
156.230.152.0/22 Valid Other IRR onlyRADB 671 100% 67
156.238.56.0/22 Valid Other IRR onlyRADB 671 100% 67
156.245.220.0/22 Valid Other IRR onlyRADB 671 100% 67
156.249.240.0/22 Valid Other IRR onlyRADB 671 100% 67
154.82.0.0/23 Valid Other IRR onlyRADB 670 100% 66
154.193.144.0/22 Valid Other IRR onlyRADB 670 100% 66
154.193.148.0/22 Valid Other IRR onlyRADB 670 100% 66
154.194.226.0/23 Valid Other IRR onlyRADB 670 100% 66
156.236.120.0/22 Valid Other IRR onlyRADB 670 100% 66
154.193.136.0/21 Valid Other IRR onlyRADB 669 99% 67
154.193.172.0/22 Valid Other IRR onlyRADB 669 99% 67
154.193.180.0/22 Valid Other IRR onlyRADB 669 99% 67
195.40.94.0/23 Valid RIR databaseRIPE 672 100% 67
195.40.182.0/23 Valid RIR databaseRIPE 672 100% 67
212.134.12.0/22 Valid RIR databaseRIPE 672 100% 67
212.134.66.0/23 Valid RIR databaseRIPE 672 100% 67
154.205.253.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
154.205.254.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.131.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.132.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.218.0/23 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.243.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.244.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.252.30.0/23 Valid RIR databaseAFRINIC, RADB 671 100% 67
195.40.82.0/23 Valid RIR databaseRIPE 671 100% 68
195.40.176.0/22 Valid RIR databaseRIPE 671 100% 66
212.134.68.0/22 Valid RIR databaseRIPE 671 100% 66
45.194.87.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
45.194.95.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
156.229.56.0/22 Valid RIR databaseAFRINIC, RADB 670 100% 68
156.239.128.0/22 Valid RIR databaseAFRINIC, RADB 670 100% 68
195.40.76.0/23 Valid RIR databaseRIPE 670 100% 67
212.134.8.0/23 Valid RIR databaseRIPE 670 100% 67
156.233.216.0/22 Valid RIR databaseAFRINIC, RADB 669 99% 67

AS-SET

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

  • Route object: none8
  • Route object: RIR17
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none195.40.82.0/24No route object for it. A route object for 195.40.82.0/23 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.672 of 673
Route object: none195.40.83.0/24No route object for it. A route object for 195.40.82.0/23 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.672 of 673
Route object: none195.40.94.0/24No route object for it. A route object for 195.40.94.0/23 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.672 of 673
Route object: none195.40.95.0/24No route object for it. A route object for 195.40.94.0/23 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.672 of 673
Route object: none156.229.56.0/23No route object for it. A route object for 156.229.56.0/22 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.671 of 673
Route object: none156.229.58.0/23No route object for it. A route object for 156.229.56.0/22 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.671 of 673
Route object: none156.239.128.0/23No route object for it. A route object for 156.239.128.0/22 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.671 of 673
Route object: none156.239.130.0/23No route object for it. A route object for 156.239.128.0/22 with origin AS214413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214413 in the RIR database for the space.671 of 673
Route object: RIR154.193.168.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR154.193.176.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.225.52.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.226.200.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.227.52.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.230.152.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.238.56.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.245.220.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.249.240.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR154.82.0.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.193.144.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.193.148.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.194.226.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR156.236.120.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.193.136.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR154.193.172.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR154.193.180.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

156.243.113.0/24AFRINIC, RADBValid
156.243.114.0/24AFRINIC, RADBValid
156.255.59.0/24AFRINIC, RADBValid
156.255.60.0/24AFRINIC, RADBValid
195.40.72.0/22RIPEValid

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.