bgpreport

Network · data from 2026-11-12

AS205827 conectat-as ConectaT Servicios de Banda Ancha SL

Registry name: conectat-as ConectaT Servicios de Banda Ancha SL, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205827, 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.
154.58.8.0/21 No ROA Other IRR onlyRADB 673 100% 67
154.58.25.0/24 No ROA Other IRR onlyRADB 673 100% 67
80.91.75.0/24 No ROA RIR databaseRIPE 672 100% 67
185.202.160.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none3
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none154.58.8.0/21No ROA covers it. Add a ROA for AS205827, maxLength 21.673 of 673
Route object: RIR154.58.8.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.58.25.0/24No ROA covers it. Add a ROA for AS205827, maxLength 24.673 of 673
Route object: RIR154.58.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none80.91.75.0/24No ROA covers it. Add a ROA for AS205827, maxLength 24.672 of 673

Route objects not announced

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

44.31.134.0/24RADBNo 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.