bgpreport

Network · data from 2026-11-12

AS202654 ASACERKO Acerko Telecom S.L.

Registry name: ASACERKO Acerko Telecom S.L., ES · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 66.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS202654, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202654, 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.147.25.0/24 No ROA RIR databaseRIPE 669 99% 67
45.88.156.0/24 No ROA RIR databaseRIPE 668 99% 67
5.59.94.0/23 Valid Nonecovered by 5.59.92.0/22 673 100% 67
5.59.95.0/24 Valid Nonecovered by 5.59.92.0/22 673 100% 67
5.59.92.0/23 Valid Nonecovered by 5.59.92.0/22 669 99% 67
185.30.163.0/24 Valid RIR databaseRIPE 673 100% 67
185.30.162.0/24 Valid RIR databaseRIPE 669 99% 67
194.8.239.0/24 Valid RIR databaseRIPE 669 99% 67
185.30.162.0/23 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS202654 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none185.147.25.0/24No ROA covers it. Add a ROA for AS202654, maxLength 24.669 of 673
ROA: none45.88.156.0/24No ROA covers it. Add a ROA for AS202654, maxLength 24.668 of 673
Route object: none5.59.94.0/23No route object for it. A route object for 5.59.92.0/22 with origin AS202654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202654 in the RIR database for the space.673 of 673
Route object: none5.59.95.0/24No route object for it. A route object for 5.59.92.0/22 with origin AS202654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202654 in the RIR database for the space.673 of 673
Route object: none5.59.92.0/23No route object for it. A route object for 5.59.92.0/22 with origin AS202654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202654 in the RIR database for the space.669 of 673

Route objects not announced

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

5.59.92.0/22RIPEValid
45.88.156.0/23RIPENo ROA
45.88.157.0/24RIPENo 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.