bgpreport

Network · data from 2026-11-12

AS39551 CTTI

Registry name: GENCAT-AS Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39551, 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.
83.247.131.0/28 Invalid: maxLength Nonecovered by 83.247.131.0/24 1 0%low visibility 1
83.247.131.192/26 Invalid: maxLength Nonecovered by 83.247.131.0/24 1 0%low visibility 1
83.247.144.200/29 Invalid: maxLength Nonecovered by 83.247.144.0/24 1 0%low visibility 1
83.247.146.128/27 Invalid: maxLength Nonecovered by 83.247.146.0/24 1 0%low visibility 1
83.247.200.0/21 Valid Nonecovered by 83.247.192.0/18 669 99% 67
83.247.208.0/20 Valid Nonecovered by 83.247.192.0/18 669 99% 67
83.247.224.0/19 Valid Nonecovered by 83.247.192.0/18 669 99% 67
83.247.144.0/24 Valid RIR databaseRIPE 671 100% 67
83.247.190.0/24 Valid RIR databaseRIPE 671 100% 67
83.247.199.0/24 Valid RIR databaseRIPE 671 100% 67
83.247.128.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.129.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.130.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.131.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.132.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.133.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.134.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.135.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.136.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.137.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.138.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.139.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.140.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.141.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.142.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.143.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.145.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.146.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.147.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.148.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.149.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.150.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.151.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.152.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.153.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.154.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.155.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.156.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.157.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.158.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.159.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.160.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.161.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.162.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.163.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.164.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.165.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.166.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.167.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.168.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.169.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.170.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.171.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.172.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.173.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.174.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.175.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.176.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.177.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.178.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.179.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.180.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.181.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.182.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.183.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.184.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.185.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.186.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.187.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.188.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.189.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.191.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.192.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.193.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.194.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.195.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.196.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.197.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.198.0/24 Valid RIR databaseRIPE 669 99% 67
83.247.200.0/24 Valid RIR databaseRIPE 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS39551: AS-GENCAT. 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 (AS39551 isn't in the set, or no route object for AS39551 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 objectsAS39551 in itNot covered
AS-GENCAT RIPE 41109 Yes 4

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

  • ROA: maxLength4
  • Route object: none7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength83.247.131.0/28ROA 83.247.131.0/24 AS39551 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 83.247.131.0/28.1 of 673
Route object: none83.247.131.0/28No route object for it. A route object for 83.247.131.0/24 with origin AS39551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39551 in the RIR database for the space.1 of 673
ROA: maxLength83.247.131.192/26ROA 83.247.131.0/24 AS39551 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 83.247.131.192/26.1 of 673
Route object: none83.247.131.192/26No route object for it. A route object for 83.247.131.0/24 with origin AS39551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39551 in the RIR database for the space.1 of 673
ROA: maxLength83.247.144.200/29ROA 83.247.144.0/24 AS39551 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 83.247.144.200/29.1 of 673
Route object: none83.247.144.200/29No route object for it. A route object for 83.247.144.0/24 with origin AS39551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39551 in the RIR database for the space.1 of 673
ROA: maxLength83.247.146.128/27ROA 83.247.146.0/24 AS39551 has maxLength 24; the route is a /27. Raise the maxLength, or add a ROA for 83.247.146.128/27.1 of 673
Route object: none83.247.146.128/27No route object for it. A route object for 83.247.146.0/24 with origin AS39551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39551 in the RIR database for the space.1 of 673
Route object: none83.247.200.0/21No route object for it. A route object for 83.247.192.0/18 with origin AS39551 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39551 in the RIR database for the space.669 of 673
Route object: none83.247.208.0/20No route object for it. A route object for 83.247.192.0/18 with origin AS39551 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39551 in the RIR database for the space.669 of 673
Route object: none83.247.224.0/19No route object for it. A route object for 83.247.192.0/18 with origin AS39551 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39551 in the RIR database for the space.669 of 673

Route objects not announced

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

83.247.152.0/21RIPENo ROA
83.247.160.0/21RIPENo ROA
83.247.178.0/23NTTCOMNo ROA
83.247.192.0/18RIPENo ROA
2a00:f380::/32RIPENo 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.