bgpreport

Network · data from 2026-11-12

AS60713 EXEA

Registry name: TARRCI-AS EXEA Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60713, 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.
153.92.16.0/21 No ROA RIR databaseRIPE 672 100% 66
153.92.24.0/23 No ROA RIR databaseRIPE 672 100% 66
185.15.44.0/22 No ROA RIR databaseRIPE 672 100% 66
153.92.21.0/24 No ROA RIR databaseRIPE 671 100% 66
193.239.44.0/22 No ROA RIR databaseRIPE 671 100% 66
195.246.126.0/23 No ROA RIR databaseRIPE 671 100% 66
2a02:f8c0::/29 No ROA RIR databaseRIPE 634 100% 70
2001:67c:267c::/48 No ROA RIR databaseRIPE 633 100% 69
82.160.50.0/24 Valid RIR databaseRIPE 672 100% 66
91.236.131.0/24 Valid RIR databaseRIPE 672 100% 66
95.143.101.0/24 Valid RIR databaseRIPE 672 100% 66
185.235.68.0/23 Valid RIR databaseRIPE 672 100% 66
212.7.212.0/24 Valid RIR databaseRIPE 672 100% 66
212.7.213.0/24 Valid RIR databaseRIPE 672 100% 66
213.199.246.0/23 Valid RIR databaseRIPE 672 100% 66
213.239.130.0/23 Valid RIR databaseRIPE 672 100% 66
213.239.132.0/22 Valid RIR databaseRIPE 672 100% 66
2a12:68c0::/32 Valid RIR databaseRIPE 633 100% 69

AS-SET

AS60713'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 10 are in fix.csv.

  • ROA: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none153.92.16.0/21No ROA covers it. Add a ROA for AS60713, maxLength 21.672 of 673
ROA: none153.92.24.0/23No ROA covers it. Add a ROA for AS60713, maxLength 23.672 of 673
ROA: none185.15.44.0/22No ROA covers it. Add a ROA for AS60713, maxLength 22.672 of 673
ROA: none153.92.21.0/24No ROA covers it. Add a ROA for AS60713, maxLength 24.671 of 673
ROA: none193.239.44.0/22No ROA covers it. Add a ROA for AS60713, maxLength 22.671 of 673
ROA: none195.246.126.0/23No ROA covers it. Add a ROA for AS60713, maxLength 23.671 of 673
ROA: none2a02:f8c0::/29No ROA covers it. Add a ROA for AS60713, maxLength 29.634 of 636
ROA: none2001:67c:267c::/48No ROA covers it. Add a ROA for AS60713, maxLength 48.633 of 636

Route objects not announced

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

153.92.26.0/24RIPENo ROA
185.15.44.0/24RIPENo 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.