bgpreport

Network · data from 2026-11-12

AS60807 Durcatel-AS Durcatel CB

Registry name: Durcatel-AS Durcatel CB, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60807, 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.
88.148.96.0/23 Invalid: origin Other origin only 18 3%low visibility 16
185.140.212.0/24 No ROA RIR databaseRIPE 673 100% 67
185.140.215.0/24 No ROA RIR databaseRIPE 673 100% 67
89.29.206.0/23 Valid RIR databaseRIPE 673 100% 67
89.29.225.0/24 Valid RIR databaseRIPE 673 100% 67
213.181.89.0/24 Valid RIR databaseRIPE 673 100% 67
213.181.90.0/23 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin88.148.96.0/23ROAs covering it name AS29119, AS209087, not AS60807. If AS60807 should announce it, add a ROA for AS60807.18 of 673
Route object: none88.148.96.0/23Route objects for it name AS209087. Add a route object with origin AS60807 in the RIR database for the space.18 of 673
ROA: none185.140.212.0/24No ROA covers it. Add a ROA for AS60807, maxLength 24.673 of 673
ROA: none185.140.215.0/24No ROA covers it. Add a ROA for AS60807, maxLength 24.673 of 673

Route objects not announced

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

185.250.196.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.