bgpreport

Network · data from 2026-11-12

AS214954 CATALUNYATELECOM CATALUNYA TELECOM S.L.

Registry name: CATALUNYATELECOM CATALUNYA TELECOM S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214954, 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.246.68.0/23 No ROA Nonecovered by 185.246.68.0/22 670 100% 67
2a11:ca00:101::/48 No ROA None 633 100% 67
2a11:ca00:201::/48 No ROA None 633 100% 67
2a11:ca00::/29 No ROA Other origin only 631 99% 67
185.71.137.0/24 No ROA RIR databaseRIPE 672 100% 67
185.246.68.0/22 No ROA RIR databaseRIPE 672 100% 67
195.18.25.0/24 No ROA RIR databaseRIPE 672 100% 67
185.152.164.0/24 No ROA RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none185.246.68.0/23No ROA covers it. Add a ROA for AS214954, maxLength 23.670 of 673
Route object: none185.246.68.0/23No route object for it. A route object for 185.246.68.0/22 with origin AS214954 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214954 in the RIR database for the space.670 of 673
ROA: none2a11:ca00:101::/48No ROA covers it. Add a ROA for AS214954, maxLength 48.633 of 636
Route object: none2a11:ca00:101::/48No route object for it. Add a route object with origin AS214954 in the RIR database for the space.633 of 636
ROA: none2a11:ca00:201::/48No ROA covers it. Add a ROA for AS214954, maxLength 48.633 of 636
Route object: none2a11:ca00:201::/48No route object for it. Add a route object with origin AS214954 in the RIR database for the space.633 of 636
ROA: none2a11:ca00::/29No ROA covers it. Add a ROA for AS214954, maxLength 29.631 of 636
Route object: none2a11:ca00::/29Route objects for it name AS29119. Add a route object with origin AS214954 in the RIR database for the space.631 of 636
ROA: none185.71.137.0/24No ROA covers it. Add a ROA for AS214954, maxLength 24.672 of 673
ROA: none185.246.68.0/22No ROA covers it. Add a ROA for AS214954, maxLength 22.672 of 673
ROA: none195.18.25.0/24No ROA covers it. Add a ROA for AS214954, maxLength 24.672 of 673
ROA: none185.152.164.0/24No ROA covers it. Add a ROA for AS214954, maxLength 24.670 of 673

Route objects not announced

Every route object with origin AS214954 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.