bgpreport

Network · data from 2026-11-12

AS34471 Free Technologies Excom

Registry name: EXCOM-AS Free Technologies Excom S.L., ES · PeeringDB

95IPv4 routes 87.4% RPKI valid · 73.7% with a route object
9IPv6 routes 100.0% RPKI valid · 100.0% with a route object
11RPKI invalid 11 origin · 0 maxLength
1No ROA 25 with no route object for this origin
20Low visibility seen by under 10% of full-table peers
83Route objects not announced registered with origin AS34471, seen from no peer

Announced routes

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

5.182.160.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.182.161.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.182.162.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.182.163.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.218.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.218.253.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.218.254.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.218.255.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.182.160.0/22 Invalid: origin Other origin only 1 0%low visibility 1
193.111.196.0/24 Invalid: origin Other origin only 1 0%low visibility 1
193.111.197.0/24 Invalid: origin Other origin only 1 0%low visibility 1
193.111.171.0/24 No ROA Other origin only 2 0%low visibility 2
46.28.166.0/23 Valid Nonecovered by 46.28.164.0/22 673 100% 66
176.56.78.0/23 Valid Nonecovered by 176.56.64.0/20 673 100% 66
176.56.80.0/22 Valid Other origin onlycovered by 176.56.64.0/19 673 100% 66
176.56.85.0/24 Valid Nonecovered by 176.56.84.0/22 673 100% 66
176.56.86.0/23 Valid Nonecovered by 176.56.84.0/22 673 100% 66
185.243.136.0/23 Valid Other origin onlycovered by 185.243.136.0/22 673 100% 66
176.56.88.0/24 Valid Nonecovered by 176.56.64.0/19 672 100% 66
176.56.92.0/24 Valid Nonecovered by 176.56.92.0/23 672 100% 66
185.223.216.0/22 Valid None 672 100% 66
185.157.4.0/24 Valid Other origin only 671 100% 66
185.157.7.0/24 Valid Other origin only 671 100% 66
193.108.206.0/24 Valid Nonecovered by 193.108.206.0/23 671 100% 66
185.107.162.0/23 Valid Nonecovered by 185.107.160.0/22 2 0%low visibility 2
2.59.108.0/22 Valid RIR databaseRIPE 673 100% 66
31.25.176.0/21 Valid RIR databaseRIPE 673 100% 66
37.122.219.0/24 Valid RIR databaseRIPE 673 100% 66
89.40.84.0/22 Valid RIR databaseRIPE 673 100% 66
109.235.16.0/21 Valid RIR databaseRIPE 673 100% 66
176.56.64.0/21 Valid RIR databaseRIPE 673 100% 66
176.56.72.0/24 Valid RIR databaseRIPE 673 100% 66
176.56.84.0/24 Valid RIR databaseRIPE 673 100% 66
176.56.94.0/24 Valid RIR databaseRIPE 673 100% 66
185.4.32.0/22 Valid RIR databaseRIPE 673 100% 66
185.4.32.0/24 Valid RIR databaseRIPE 673 100% 66
185.4.33.0/24 Valid RIR databaseRIPE 673 100% 66
185.4.35.0/24 Valid RIR databaseRIPE 673 100% 66
185.70.152.0/22 Valid RIR databaseRIPE 673 100% 66
185.70.152.0/24 Valid RIR databaseRIPE 673 100% 66
185.70.153.0/24 Valid RIR databaseRIPE 673 100% 66
185.85.255.0/24 Valid RIR databaseRIPE 673 100% 66
185.102.204.0/22 Valid RIR databaseRIPE 673 100% 66
185.103.148.0/22 Valid RIR databaseRIPE 673 100% 66
185.153.17.0/24 Valid RIR databaseRIPE 673 100% 66
185.153.18.0/24 Valid RIR databaseRIPE 673 100% 66
185.176.105.0/24 Valid RIR databaseRIPE 673 100% 66
185.176.106.0/24 Valid RIR databaseRIPE 673 100% 66
185.176.107.0/24 Valid RIR databaseRIPE 673 100% 66
185.205.253.0/24 Valid RIR databaseRIPE 673 100% 66
185.205.254.0/24 Valid RIR databaseRIPE 673 100% 66
185.228.124.0/22 Valid RIR databaseRIPE 673 100% 66
185.228.124.0/24 Valid RIR databaseRIPE 673 100% 66
185.228.125.0/24 Valid RIR databaseRIPE 673 100% 66
185.228.127.0/24 Valid RIR databaseRIPE 673 100% 66
185.239.160.0/22 Valid RIR databaseRIPE 673 100% 66
185.239.160.0/24 Valid RIR databaseRIPE 673 100% 66
185.239.161.0/24 Valid RIR databaseRIPE 673 100% 66
185.239.162.0/23 Valid RIR databaseRIPE 673 100% 66
185.243.138.0/24 Valid RIR databaseRIPE 673 100% 66
185.243.139.0/24 Valid RIR databaseRIPE 673 100% 66
193.108.230.0/23 Valid RIR databaseRIPE 673 100% 66
2.59.110.0/24 Valid RIR databaseRIPE 672 100% 66
2.59.111.0/24 Valid RIR databaseRIPE 672 100% 66
46.28.160.0/24 Valid RIR databaseRIPE 672 100% 66
46.28.164.0/24 Valid RIR databaseRIPE 672 100% 66
46.28.165.0/24 Valid RIR databaseRIPE 672 100% 66
89.40.84.0/24 Valid RIR databaseRIPE 672 100% 66
89.40.85.0/24 Valid RIR databaseRIPE 672 100% 66
89.40.86.0/24 Valid RIR databaseRIPE 672 100% 66
89.40.87.0/24 Valid RIR databaseRIPE 672 100% 66
91.242.148.0/22 Valid RIR databaseRIPE 672 100% 66
91.242.149.0/24 Valid RIR databaseRIPE 672 100% 66
91.242.150.0/24 Valid RIR databaseRIPE 672 100% 66
176.56.73.0/24 Valid RIR databaseRIPE 672 100% 66
185.4.34.0/24 Valid RIR databaseRIPE 672 100% 66
185.5.84.0/22 Valid RIR databaseRIPE 672 100% 66
185.5.84.0/24 Valid RIR databaseRIPE 672 100% 66
185.5.86.0/24 Valid RIR databaseRIPE 672 100% 66
185.5.87.0/24 Valid RIR databaseRIPE 672 100% 66
185.142.44.0/22 Valid RIR databaseRIPE 672 100% 66
193.246.156.0/24 Valid RIR databaseRIPE 672 100% 66
193.246.157.0/24 Valid RIR databaseRIPE 672 100% 66
194.156.72.0/22 Valid RIR databaseRIPE 672 100% 66
194.156.73.0/24 Valid RIR databaseRIPE 672 100% 66
194.156.75.0/24 Valid RIR databaseRIPE 672 100% 66
194.156.72.0/24 Valid RIR databaseRIPE 671 100% 66
45.92.132.0/23 Valid RIR databaseRIPE 669 99% 66
2a02:5dc0::/32 Valid RIR databaseRIPE 634 100% 68
2a02:5fc0::/32 Valid RIR databaseRIPE 634 100% 68
2a03:440::/32 Valid RIR databaseRIPE 634 100% 68
2a05:9b00::/29 Valid RIR databaseRIPE 633 100% 68
2a05:a800::/29 Valid RIR databaseRIPE 633 100% 68
2a06:3c00::/29 Valid RIR databaseRIPE 633 100% 68
2a09:eac0::/29 Valid RIR databaseRIPE 633 100% 68
2a0a:1280::/29 Valid RIR databaseRIPE 633 100% 68
2a0b:c40::/29 Valid RIR databaseRIPE 633 100% 68
185.153.19.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.223.216.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.228.126.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.142.44.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.142.45.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.142.46.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.142.47.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS34471: AS-EXCOM. 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 (AS34471 isn't in the set, or no route object for AS34471 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 objectsAS34471 in itNot covered
AS-EXCOM RIPE 243358 Yes 15

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

  • ROA: origin11
  • ROA: none1
  • Route object: none25
  • Route object: not announced83
ChangePrefix or setDetailFull-table peers
ROA: origin5.182.160.0/24ROAs covering it name AS42241, AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none5.182.160.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin5.182.161.0/24ROAs covering it name AS42241, AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none5.182.161.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin5.182.162.0/24ROAs covering it name AS42241, AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none5.182.162.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin5.182.163.0/24ROAs covering it name AS42241, AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none5.182.163.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin185.218.252.0/24ROAs covering it name AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none185.218.252.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin185.218.253.0/24ROAs covering it name AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none185.218.253.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin185.218.254.0/24ROAs covering it name AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none185.218.254.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin185.218.255.0/24ROAs covering it name AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.2 of 673
Route object: none185.218.255.0/24Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
ROA: origin5.182.160.0/22ROAs covering it name AS42241, AS203641, not AS34471. If AS34471 should announce it, add a ROA for AS34471.1 of 673
Route object: none5.182.160.0/22Route objects for it name AS203641. Add a route object with origin AS34471 in the RIR database for the space.1 of 673
ROA: origin193.111.196.0/24ROAs covering it name AS152179, not AS34471. If AS34471 should announce it, add a ROA for AS34471.1 of 673
Route object: none193.111.196.0/24Route objects for it name AS152179. Add a route object with origin AS34471 in the RIR database for the space.1 of 673
ROA: origin193.111.197.0/24ROAs covering it name AS152179, not AS34471. If AS34471 should announce it, add a ROA for AS34471.1 of 673
Route object: none193.111.197.0/24Route objects for it name AS152179. Add a route object with origin AS34471 in the RIR database for the space.1 of 673
ROA: none193.111.171.0/24No ROA covers it. Add a ROA for AS34471, maxLength 24.2 of 673
Route object: none193.111.171.0/24Route objects for it name AS834. Add a route object with origin AS34471 in the RIR database for the space.2 of 673
Route object: none46.28.166.0/23No route object for it. A route object for 46.28.164.0/22 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none176.56.78.0/23No route object for it. A route object for 176.56.64.0/20 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none176.56.80.0/22Route objects for it name AS48624. A route object for 176.56.64.0/19 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none176.56.85.0/24No route object for it. A route object for 176.56.84.0/22 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none176.56.86.0/23No route object for it. A route object for 176.56.84.0/22 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none185.243.136.0/23Route objects for it name AS202334. A route object for 185.243.136.0/22 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.673 of 673
Route object: none176.56.88.0/24No route object for it. A route object for 176.56.64.0/19 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.672 of 673
Route object: none176.56.92.0/24No route object for it. A route object for 176.56.92.0/23 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.672 of 673
Route object: none185.223.216.0/22No route object for it. Add a route object with origin AS34471 in the RIR database for the space.672 of 673
Route object: none185.157.4.0/24Route objects for it name AS207185. Add a route object with origin AS34471 in the RIR database for the space.671 of 673
Route object: none185.157.7.0/24Route objects for it name AS207185. Add a route object with origin AS34471 in the RIR database for the space.671 of 673
Route object: none193.108.206.0/24No route object for it. A route object for 193.108.206.0/23 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.671 of 673
Route object: none185.107.162.0/23No route object for it. A route object for 185.107.160.0/22 with origin AS34471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34471 in the RIR database for the space.2 of 673

Route objects not announced

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

2.59.108.0/24RIPEValid
2.59.109.0/24RIPEValid
31.25.176.0/22RIPEValid
31.25.176.0/24RIPEValid
31.25.177.0/24RIPEValid
31.25.178.0/24RIPEValid
31.25.179.0/24RIPEValid
31.25.180.0/22RIPEValid
31.25.180.0/24RIPEValid
31.25.181.0/24RIPEValid
31.25.182.0/24RIPEValid
31.25.183.0/24RIPEValid
45.92.132.0/22RIPEValid
45.92.132.0/24RIPEValid
45.92.133.0/24RIPEValid
45.92.134.0/24RIPEValid
45.92.135.0/24RIPEValid
46.28.160.0/21RIPEValid
46.28.160.0/22RIPEValid
46.28.163.0/24RIPEValid
46.28.164.0/22RIPEValid
46.28.166.0/24RIPEValid
46.28.167.0/24RIPEValid
89.40.84.0/23RIPEValid
89.40.86.0/23RIPEValid
91.242.148.0/23RIPEValid
91.242.148.0/24RIPEValid
91.242.150.0/23RIPEValid
91.242.151.0/24RIPEValid
109.235.16.0/22RIPEValid
109.235.16.0/23RIPEValid
109.235.16.0/24RIPEValid
109.235.17.0/24RIPEValid
109.235.18.0/23RIPEValid
109.235.18.0/24RIPEValid
109.235.19.0/24RIPEValid
109.235.20.0/22RIPEValid
109.235.20.0/24RIPEValid
109.235.21.0/24RIPEValid
109.235.22.0/24RIPEValid
176.56.64.0/19RIPEValid
176.56.64.0/20RIPEValid
176.56.80.0/24RIPEValid
176.56.84.0/22RIPEValid
176.56.92.0/23RIPEValid
176.56.95.0/24RIPEValid
178.156.122.0/24RIPEInvalid: origin
185.4.34.0/23RIPEValid
185.5.84.0/23RIPEValid
185.5.85.0/24RIPEValid
185.5.86.0/23RIPEValid
185.70.154.0/24RIPEValid
185.70.155.0/24RIPEValid
185.103.148.0/24RIPEValid
185.103.149.0/24RIPEValid
185.103.150.0/24RIPEValid
185.103.151.0/24RIPEValid
185.107.160.0/22RIPEValid
185.107.162.0/24RIPEValid
185.107.163.0/24RIPEValid
185.110.212.0/22RIPEValid
185.110.212.0/24RIPEValid
185.110.213.0/24RIPEValid
185.110.214.0/24RIPEValid
185.110.215.0/24RIPEValid
185.153.16.0/22RIPEValid
185.153.16.0/23RIPEValid
185.153.16.0/24RIPEValid
185.176.104.0/22RIPEValid
185.176.104.0/24RIPEValid
185.223.219.0/24RIPEInvalid: maxLength
185.239.162.0/24RIPEInvalid: maxLength
185.239.163.0/24RIPEInvalid: maxLength
185.243.136.0/22RIPEValid
185.243.136.0/24RIPEValid
185.243.137.0/24RIPEValid
193.108.206.0/23RIPEValid
193.108.230.0/24RIPEValid
193.108.231.0/24RIPEValid
193.151.246.0/24RIPEValid
193.246.156.0/23RIPEValid
194.156.74.0/24RIPEValid
2a02:5fc0::/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.