bgpreport

Network · data from 2026-11-12

AS203217 Horizon Scope - IQ

Registry name: HORIZON-SCOPE-IQ Horizon Scope Mobile Telecom WLL, IQ · PeeringDB

101IPv4 routes 94.1% RPKI valid · 74.3% with a route object
10IPv6 routes 100.0% RPKI valid · 100.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
1No ROA 26 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
52Route objects not announced registered with origin AS203217, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203217, 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.
151.236.160.255/32 Invalid: origin None 0 0%low visibility 1
151.236.165.255/32 Invalid: origin None 0 0%low visibility 1
151.236.166.255/32 Invalid: origin None 0 0%low visibility 1
194.59.28.124/32 Invalid: origin None 0 0%low visibility 1
194.59.29.124/32 Invalid: origin None 0 0%low visibility 1
185.247.179.0/24 No ROA Other origin only 670 100% 67
38.51.140.0/23 Valid Nonecovered by 38.51.140.0/22 673 100% 67
38.51.142.0/23 Valid Nonecovered by 38.51.140.0/22 673 100% 67
154.43.178.0/23 Valid Nonecovered by 154.43.176.0/22 673 100% 67
38.199.252.0/23 Valid Nonecovered by 38.199.252.0/22 672 100% 66
38.199.252.0/24 Valid Nonecovered by 38.199.252.0/22 672 100% 67
38.199.254.0/23 Valid Nonecovered by 38.199.252.0/22 672 100% 66
154.43.178.0/24 Valid Nonecovered by 154.43.176.0/22 672 100% 67
204.157.180.0/23 Valid Nonecovered by 204.157.180.0/22 672 100% 67
38.199.253.0/24 Valid Nonecovered by 38.199.252.0/22 671 100% 68
38.199.254.0/24 Valid Nonecovered by 38.199.252.0/22 671 100% 68
38.199.255.0/24 Valid Nonecovered by 38.199.252.0/22 671 100% 68
38.51.140.0/24 Valid Nonecovered by 38.51.140.0/22 668 99% 68
38.51.141.0/24 Valid Nonecovered by 38.51.140.0/22 668 99% 68
38.51.142.0/24 Valid Nonecovered by 38.51.140.0/22 668 99% 68
38.51.143.0/24 Valid Nonecovered by 38.51.140.0/22 668 99% 68
154.43.179.0/24 Valid Nonecovered by 154.43.176.0/22 32 5%low visibility 15
204.157.181.0/24 Valid Nonecovered by 204.157.180.0/22 31 5%low visibility 14
204.157.178.0/23 Valid Other origin onlycovered by 204.157.176.0/22 4 1%low visibility 4
154.43.176.0/23 Valid Nonecovered by 154.43.176.0/22 1 0%low visibility 1
204.157.180.0/24 Valid Nonecovered by 204.157.180.0/22 1 0%low visibility 1
38.3.232.0/23 Valid Other IRR onlyRADB 673 100% 66
38.3.234.0/23 Valid Other IRR onlyRADB 673 100% 66
38.3.232.0/24 Valid Other IRR onlyRADB 672 100% 67
38.3.234.0/24 Valid Other IRR onlyRADB 672 100% 67
38.3.235.0/24 Valid Other IRR onlyRADB 672 100% 67
38.3.236.0/23 Valid Other IRR onlyRADB 672 100% 66
38.3.237.0/24 Valid Other IRR onlyRADB 672 100% 66
38.3.238.0/23 Valid Other IRR onlyRADB 672 100% 66
38.3.238.0/24 Valid Other IRR onlyRADB 672 100% 66
38.3.239.0/24 Valid Other IRR onlyRADB 672 100% 66
38.3.233.0/24 Valid Other IRR onlyRADB 671 100% 67
38.3.236.0/24 Valid Other IRR onlyRADB 670 100% 67
204.157.179.0/24 Valid Other IRR onlyRADB 668 99% 68
93.180.220.0/23 Valid RIR databaseRIPE 673 100% 66
93.180.222.0/23 Valid RIR databaseRIPE 673 100% 66
185.20.197.0/24 Valid RIR databaseRIPE 673 100% 66
45.8.72.0/24 Valid RIR databaseRIPE 672 100% 66
185.20.198.0/23 Valid RIR databaseRIPE 672 100% 66
185.20.198.0/24 Valid RIR databaseRIPE 672 100% 66
185.20.199.0/24 Valid RIR databaseRIPE 672 100% 66
185.65.252.0/24 Valid RIR databaseRIPE 672 100% 67
185.112.189.0/24 Valid RIR databaseRIPE 672 100% 67
185.112.190.0/23 Valid RIR databaseRIPE 672 100% 66
185.138.121.0/24 Valid RIR databaseRIPE 672 100% 66
185.194.9.0/24 Valid RIR databaseRIPE 672 100% 66
185.239.176.0/24 Valid RIR databaseRIPE 672 100% 67
195.133.221.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.8.73.0/24 Valid RIR databaseRIPE 671 100% 66
93.180.216.0/23 Valid RIR databaseRIPE 671 100% 66
93.180.218.0/23 Valid RIR databaseRIPE 671 100% 66
93.180.220.0/24 Valid RIR databaseRIPE 671 100% 66
138.124.158.0/23 Valid RIR databaseRIPE 671 100% 66
144.86.228.0/23 Valid RIR databaseRIPE 671 100% 66
185.20.196.0/23 Valid RIR databaseRIPE 671 100% 66
185.112.188.0/23 Valid RIR databaseRIPE 671 100% 66
185.112.191.0/24 Valid RIR databaseRIPE 671 100% 66
185.138.122.0/23 Valid RIR databaseRIPE 671 100% 66
185.194.10.0/23 Valid RIR databaseRIPE 671 100% 66
185.254.14.0/24 Valid RIR databaseRIPE 671 100% 66
195.133.220.0/23 Valid RIR databaseRIPE 671 100% 66
195.133.222.0/23 Valid RIR databaseRIPE 671 100% 66
195.133.223.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
45.8.72.0/23 Valid RIR databaseRIPE 670 100% 67
93.180.218.0/24 Valid RIR databaseRIPE 670 100% 67
93.180.219.0/24 Valid RIR databaseRIPE 670 100% 67
185.138.120.0/23 Valid RIR databaseRIPE 670 100% 67
81.161.228.0/24 Valid RIR databaseRIPE 669 99% 66
93.180.216.0/24 Valid RIR databaseRIPE 669 99% 67
93.180.217.0/24 Valid RIR databaseRIPE 669 99% 68
93.180.221.0/24 Valid RIR databaseRIPE 669 99% 67
144.86.230.0/23 Valid RIR databaseRIPE 669 99% 66
144.86.230.0/24 Valid RIR databaseRIPE 669 99% 68
185.194.11.0/24 Valid RIR databaseRIPE 669 99% 67
93.180.223.0/24 Valid RIR databaseRIPE 668 99% 68
138.124.156.0/23 Valid RIR databaseRIPE 668 99% 67
138.124.156.0/24 Valid RIR databaseRIPE 668 99% 67
144.86.231.0/24 Valid RIR databaseRIPE 668 99% 68
185.20.196.0/24 Valid RIR databaseRADB, RIPE 668 99% 68
185.138.122.0/24 Valid RIR databaseRIPE 668 99% 67
185.194.10.0/24 Valid RIR databaseRIPE 668 99% 68
195.133.220.0/24 Valid RIR databaseRIPE 668 99% 67
195.133.222.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
138.124.158.0/24 Valid RIR databaseRIPE 667 99% 67
144.86.229.0/24 Valid RIR databaseRIPE 667 99% 67
138.124.159.0/24 Valid RIR databaseRIPE 666 99% 67
144.86.228.0/24 Valid RIR databaseRIPE 666 99% 67
185.112.188.0/24 Valid RIR databaseRIPE 666 99% 67
185.138.120.0/24 Valid RIR databaseRIPE 666 99% 67
185.138.123.0/24 Valid RIR databaseRADB, RIPE 666 99% 67
38.3.184.0/24 Valid RIR databaseARIN 665 99% 68
2a0b:1880:1::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:1880:5::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:1880:14::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:1880:18::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:1880:2::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:1880:7::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:1880:f::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:1880:10::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:1880:e::/48 Valid RIR databaseRIPE 633 100% 67
2a0b:1880:12::/48 Valid RIR databaseRIPE 633 100% 67
185.254.13.0/24 Valid RIR databaseRIPE 118 18% 45
199.74.191.0/24 Valid RIR databaseRIPE 93 14% 40
138.124.157.0/24 Valid RIR databaseRIPE 83 12% 37
199.74.189.0/24 Valid RIR databaseRIPE 74 11% 38
154.43.166.0/24 Valid RIR databaseARIN, RADB 4 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS203217: RADB::AS-HZ. 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 (AS203217 isn't in the set, or no route object for AS203217 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 objectsAS203217 in itNot covered
RADB::AS-HZ In no IRR database read today.

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

  • ROA: origin5
  • ROA: none1
  • Route object: none26
  • Route object: RIR13
  • AS-SET: not found1
  • Route object: not announced52
ChangePrefix or setDetailFull-table peers
ROA: origin151.236.160.255/32ROAs covering it name AS19905, AS59588, not AS203217. If AS203217 should announce it, add a ROA for AS203217.0 of 673
Route object: none151.236.160.255/32No route object for it. Add a route object with origin AS203217 in the RIR database for the space.0 of 673
ROA: origin151.236.165.255/32ROAs covering it name AS19905, AS59588, not AS203217. If AS203217 should announce it, add a ROA for AS203217.0 of 673
Route object: none151.236.165.255/32No route object for it. Add a route object with origin AS203217 in the RIR database for the space.0 of 673
ROA: origin151.236.166.255/32ROAs covering it name AS19905, AS59588, not AS203217. If AS203217 should announce it, add a ROA for AS203217.0 of 673
Route object: none151.236.166.255/32No route object for it. Add a route object with origin AS203217 in the RIR database for the space.0 of 673
ROA: origin194.59.28.124/32ROAs covering it name AS59588, not AS203217. If AS203217 should announce it, add a ROA for AS203217.0 of 673
Route object: none194.59.28.124/32No route object for it. Add a route object with origin AS203217 in the RIR database for the space.0 of 673
ROA: origin194.59.29.124/32ROAs covering it name AS59588, not AS203217. If AS203217 should announce it, add a ROA for AS203217.0 of 673
Route object: none194.59.29.124/32No route object for it. Add a route object with origin AS203217 in the RIR database for the space.0 of 673
ROA: none185.247.179.0/24No ROA covers it. Add a ROA for AS203217, maxLength 24.670 of 673
Route object: none185.247.179.0/24Route objects for it name AS204473. Add a route object with origin AS203217 in the RIR database for the space.670 of 673
Route object: none38.51.140.0/23No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.673 of 673
Route object: none38.51.142.0/23No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.673 of 673
Route object: none154.43.178.0/23No route object for it. A route object for 154.43.176.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.673 of 673
Route object: none38.199.252.0/23No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.672 of 673
Route object: none38.199.252.0/24No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.672 of 673
Route object: none38.199.254.0/23No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.672 of 673
Route object: none154.43.178.0/24No route object for it. A route object for 154.43.176.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.672 of 673
Route object: none204.157.180.0/23No route object for it. A route object for 204.157.180.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.672 of 673
Route object: none38.199.253.0/24No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.671 of 673
Route object: none38.199.254.0/24No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.671 of 673
Route object: none38.199.255.0/24No route object for it. A route object for 38.199.252.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.671 of 673
Route object: none38.51.140.0/24No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.668 of 673
Route object: none38.51.141.0/24No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.668 of 673
Route object: none38.51.142.0/24No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.668 of 673
Route object: none38.51.143.0/24No route object for it. A route object for 38.51.140.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.668 of 673
Route object: none154.43.179.0/24No route object for it. A route object for 154.43.176.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.32 of 673
Route object: none204.157.181.0/24No route object for it. A route object for 204.157.180.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.31 of 673
Route object: none204.157.178.0/23Route objects for it name AS211908. A route object for 204.157.176.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.4 of 673
Route object: none154.43.176.0/23No route object for it. A route object for 154.43.176.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.1 of 673
Route object: none204.157.180.0/24No route object for it. A route object for 204.157.180.0/22 with origin AS203217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203217 in the RIR database for the space.1 of 673
Route object: RIR38.3.232.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.3.234.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.3.232.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.234.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.235.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.236.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.237.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.238.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.3.233.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.3.236.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.157.179.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
AS-SET: not foundRADB::AS-HZPeeringDB names RADB::AS-HZ; no IRR database read has it.

Route objects not announced

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

38.3.228.0/22ARINValid
38.3.232.0/21ARIN, RADBValid
38.51.140.0/22ARINValid
38.199.252.0/22ARINValid
45.82.60.0/24RIPEValid
93.180.216.0/21RIPEValid
93.180.216.0/22RIPEValid
93.180.220.0/22RIPEValid
93.180.222.0/24RIPEValid
138.124.156.0/22RIPEValid
144.86.228.0/22RIPEValid
154.43.176.0/22ARINValid
185.20.196.0/22RADB, RIPEValid
185.112.188.0/22RIPEValid
185.112.190.0/24RIPEValid
185.117.9.0/24RIPEValid
185.138.120.0/22RIPEValid
185.194.8.0/22RIPEValid
185.194.8.0/23RIPEValid
185.194.8.0/24RIPEValid
185.239.178.0/24RIPEValid
185.254.12.0/22RADBValid
185.254.12.0/23RIPEValid
185.254.12.0/24RIPEValid
185.254.14.0/23RIPEValid
185.254.15.0/24RIPEValid
194.39.229.0/24RIPEValid
195.133.220.0/22RADB, RIPEValid
199.74.188.0/22RADBValid
199.74.188.0/23RIPEValid
199.74.190.0/23RIPEValid
199.74.190.0/24RIPEValid
204.157.176.0/22ARINValid
204.157.180.0/22ARINValid
2a0b:1880::/48RIPEValid
2a0b:1880:3::/48RIPEValid
2a0b:1880:4::/48RIPEValid
2a0b:1880:6::/48RIPEValid
2a0b:1880:8::/48RIPEValid
2a0b:1880:9::/48RIPEValid
2a0b:1880:a::/48RIPEValid
2a0b:1880:b::/48RIPEValid
2a0b:1880:c::/48RIPEValid
2a0b:1880:d::/48RIPEValid
2a0b:1880:11::/48RIPEValid
2a0b:1880:13::/48RIPEValid
2a0b:1880:15::/48RIPEValid
2a0b:1880:16::/48RIPEValid
2a0b:1880:17::/48RIPEValid
2a0b:1880:19::/48RIPEValid
2a0b:1880:1a::/48RIPEValid
2a0b:1880:1b::/48RIPEValid

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.