bgpreport

Network · data from 2026-11-12

AS200810 CONECTA 3 TELECOM

Registry name: Conecta3 CONECTA 3 TELECOM S.L., ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200810, 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.
45.93.120.0/24 No ROA RIR databaseRIPE 672 100% 66
45.93.121.0/24 No ROA RIR databaseRIPE 672 100% 66
89.36.80.0/21 Valid RIR databaseRIPE 673 100% 66
89.36.80.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.81.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.82.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.83.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.84.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.85.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.86.0/24 Valid RIR databaseRIPE 673 100% 66
89.36.87.0/24 Valid RIR databaseRIPE 673 100% 66
185.77.176.0/22 Valid RIR databaseRIPE 673 100% 66
185.77.176.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.188.0/22 Valid RIR databaseRIPE 673 100% 66
185.245.188.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.189.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.190.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.191.0/24 Valid RIR databaseRIPE 673 100% 66
185.246.248.0/22 Valid RIR databaseRIPE 673 100% 66
185.246.248.0/24 Valid RIR databaseRIPE 673 100% 66
185.246.249.0/24 Valid RIR databaseRIPE 673 100% 66
185.246.250.0/24 Valid RIR databaseRIPE 673 100% 66
2a05:6580::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS200810'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 11 are in fix.csv.

  • ROA: none2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none45.93.120.0/24No ROA covers it. Add a ROA for AS200810, maxLength 24.672 of 673
ROA: none45.93.121.0/24No ROA covers it. Add a ROA for AS200810, maxLength 24.672 of 673

Route objects not announced

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

81.28.240.0/22RIPENo ROA
89.36.80.0/22RIPEValid
89.36.84.0/22RIPEValid
185.77.177.0/24RIPEValid
185.77.178.0/24RIPEValid
185.77.179.0/24RIPEValid
185.246.248.0/23RIPEValid
185.246.250.0/23RIPEValid
185.246.251.0/24RIPEValid

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.