bgpreport

Network · data from 2026-11-12

AS60609 APFUTURA TELECOM

Registry name: APFUTURA-ASN APFUTURA TELECOM SL, ES · PeeringDB

42IPv4 routes 85.7% RPKI valid · 73.8% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
2No ROA 11 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS60609, seen from no peer

Announced routes

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

185.251.204.0/24 Invalid: maxLength Nonecovered by 185.251.204.0/22 126 19% 51
185.251.205.0/24 Invalid: maxLength Nonecovered by 185.251.204.0/22 126 19% 51
185.251.206.0/24 Invalid: maxLength Nonecovered by 185.251.204.0/22 126 19% 51
5.183.148.0/24 Invalid: maxLength Nonecovered by 5.183.148.0/23 125 19% 51
78.142.248.0/24 No ROA RIR databaseRIPE 669 99% 66
94.231.202.0/24 No ROA RIR databaseRIPE 669 99% 66
185.158.168.0/24 Valid Nonecovered by 185.158.168.0/23 669 99% 66
185.158.169.0/24 Valid Nonecovered by 185.158.168.0/23 669 99% 66
185.232.48.0/24 Valid Nonecovered by 185.232.48.0/22 669 99% 66
185.232.49.0/24 Valid Nonecovered by 185.232.48.0/22 669 99% 66
185.232.50.0/24 Valid Nonecovered by 185.232.48.0/22 669 99% 66
185.232.51.0/24 Valid Nonecovered by 185.232.48.0/22 669 99% 66
5.183.149.0/24 Valid Nonecovered by 5.183.148.0/23 668 99% 66
2.57.100.0/24 Valid RIR databaseRIPE 669 99% 66
2.57.101.0/24 Valid RIR databaseRIPE 669 99% 66
2.57.102.0/24 Valid RIR databaseRIPE 669 99% 66
2.57.103.0/24 Valid RIR databaseRIPE 669 99% 66
5.181.96.0/23 Valid RIR databaseRIPE 669 99% 66
5.183.148.0/23 Valid RIR databaseRIPE 669 99% 66
45.67.148.0/22 Valid RIR databaseRIPE 669 99% 66
134.255.250.0/24 Valid RIR databaseRIPE 669 99% 66
185.37.212.0/24 Valid RIR databaseRIPE 669 99% 66
185.37.213.0/24 Valid RIR databaseRIPE 669 99% 66
185.37.214.0/24 Valid RIR databaseRIPE 669 99% 66
185.37.215.0/24 Valid RIR databaseRIPE 669 99% 66
185.77.157.0/24 Valid RIR databaseRIPE 669 99% 66
185.77.159.0/24 Valid RIR databaseRIPE 669 99% 66
185.86.11.0/24 Valid RIR databaseRIPE 669 99% 66
185.158.168.0/23 Valid RIR databaseRIPE 669 99% 66
185.158.171.0/24 Valid RIR databaseRIPE 669 99% 66
185.204.186.0/24 Valid RIR databaseRIPE 669 99% 66
185.251.204.0/22 Valid RIR databaseRIPE 669 99% 66
194.26.174.0/24 Valid RIR databaseRIPE 669 99% 66
194.63.147.0/24 Valid RIR databaseRIPE 669 99% 66
5.181.98.0/24 Valid RIR databaseRIPE 668 99% 66
37.16.77.0/24 Valid RIR databaseRIPE 668 99% 66
45.10.130.0/24 Valid RIR databaseRIPE 668 99% 66
46.254.104.0/24 Valid RIR databaseRIPE 668 99% 66
45.200.136.0/24 Valid RIR databaseAFRINIC, RADB 667 99% 66
45.200.137.0/24 Valid RIR databaseAFRINIC, RADB 667 99% 66
45.200.138.0/24 Valid RIR databaseAFRINIC, RADB 667 99% 66
45.200.139.0/24 Valid RIR databaseAFRINIC, RADB 667 99% 66

AS-SET

AS60609'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 27 are in fix.csv.

  • ROA: maxLength4
  • ROA: none2
  • Route object: none11
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.251.204.0/24ROA 185.251.204.0/22 AS60609 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.251.204.0/24.126 of 673
Route object: none185.251.204.0/24No route object for it. A route object for 185.251.204.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.126 of 673
ROA: maxLength185.251.205.0/24ROA 185.251.204.0/22 AS60609 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.251.205.0/24.126 of 673
Route object: none185.251.205.0/24No route object for it. A route object for 185.251.204.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.126 of 673
ROA: maxLength185.251.206.0/24ROA 185.251.204.0/22 AS60609 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.251.206.0/24.126 of 673
Route object: none185.251.206.0/24No route object for it. A route object for 185.251.204.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.126 of 673
ROA: maxLength5.183.148.0/24ROA 5.183.148.0/23 AS60609 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 5.183.148.0/24.125 of 673
Route object: none5.183.148.0/24No route object for it. A route object for 5.183.148.0/23 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.125 of 673
ROA: none78.142.248.0/24No ROA covers it. Add a ROA for AS60609, maxLength 24.669 of 673
ROA: none94.231.202.0/24No ROA covers it. Add a ROA for AS60609, maxLength 24.669 of 673
Route object: none185.158.168.0/24No route object for it. A route object for 185.158.168.0/23 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none185.158.169.0/24No route object for it. A route object for 185.158.168.0/23 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none185.232.48.0/24No route object for it. A route object for 185.232.48.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none185.232.49.0/24No route object for it. A route object for 185.232.48.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none185.232.50.0/24No route object for it. A route object for 185.232.48.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none185.232.51.0/24No route object for it. A route object for 185.232.48.0/22 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.669 of 673
Route object: none5.183.149.0/24No route object for it. A route object for 5.183.148.0/23 with origin AS60609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60609 in the RIR database for the space.668 of 673

Route objects not announced

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

5.158.221.0/24RIPEValid
5.158.222.0/24RIPEValid
5.158.223.0/24RIPEValid
5.181.96.0/24RIPEValid
5.181.97.0/24RIPEValid
5.182.172.0/22RIPENo ROA
185.77.156.0/24RIPEValid
185.77.158.0/24RIPEInvalid: origin
185.232.48.0/22RIPENo ROA
2a04:7280::/29RIPENo ROA

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.