bgpreport

Network · data from 2026-11-12

AS57325 AS204765 123Telcom BV trading as Partell

Registry name: AS204765 123Telcom BV trading as Partell, NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57325, 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.
86.58.202.0/24 No ROA Nonecovered by 86.58.200.0/22 673 100% 67
185.41.136.0/24 No ROA Nonecovered by 185.41.136.0/22 673 100% 67
185.41.137.0/24 No ROA Nonecovered by 185.41.136.0/22 673 100% 67
185.41.138.0/24 No ROA Nonecovered by 185.41.136.0/22 673 100% 67
185.41.139.0/24 No ROA Nonecovered by 185.41.136.0/22 673 100% 67
86.58.200.0/22 No ROA RIR databaseRIPE 673 100% 67
2a01:52e0::/32 No ROA RIR databaseRIPE 634 100% 67
185.41.136.0/22 No ROA RIR databaseRIPE 28 4%low visibility 22
185.239.60.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none86.58.202.0/24No ROA covers it. Add a ROA for AS57325, maxLength 24.673 of 673
Route object: none86.58.202.0/24No route object for it. A route object for 86.58.200.0/22 with origin AS57325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57325 in the RIR database for the space.673 of 673
ROA: none185.41.136.0/24No ROA covers it. Add a ROA for AS57325, maxLength 24.673 of 673
Route object: none185.41.136.0/24No route object for it. A route object for 185.41.136.0/22 with origin AS57325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57325 in the RIR database for the space.673 of 673
ROA: none185.41.137.0/24No ROA covers it. Add a ROA for AS57325, maxLength 24.673 of 673
Route object: none185.41.137.0/24No route object for it. A route object for 185.41.136.0/22 with origin AS57325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57325 in the RIR database for the space.673 of 673
ROA: none185.41.138.0/24No ROA covers it. Add a ROA for AS57325, maxLength 24.673 of 673
Route object: none185.41.138.0/24No route object for it. A route object for 185.41.136.0/22 with origin AS57325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57325 in the RIR database for the space.673 of 673
ROA: none185.41.139.0/24No ROA covers it. Add a ROA for AS57325, maxLength 24.673 of 673
Route object: none185.41.139.0/24No route object for it. A route object for 185.41.136.0/22 with origin AS57325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57325 in the RIR database for the space.673 of 673
ROA: none86.58.200.0/22No ROA covers it. Add a ROA for AS57325, maxLength 22.673 of 673
ROA: none2a01:52e0::/32No ROA covers it. Add a ROA for AS57325, maxLength 32.634 of 636
ROA: none185.41.136.0/22No ROA covers it. Add a ROA for AS57325, maxLength 22.28 of 673

Route objects not announced

Every route object with origin AS57325 is announced.

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.