bgpreport

Network · data from 2026-11-12

AS47134 ECZ-NET Eczacibasi Bilisim San.ve Tic. A.S.

Registry name: ECZ-NET Eczacibasi Bilisim San.ve Tic. A.S., TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47134, 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.
93.91.71.0/24 Invalid: maxLength Nonecovered by 93.91.64.0/21 3 0%low visibility 2
93.91.67.0/24 Valid Nonecovered by 93.91.64.0/21 672 100% 67
93.91.64.0/20 Valid RIR databaseRIPE 673 100% 67
93.91.65.0/24 Valid RIR databaseRIPE 672 100% 67
93.91.73.0/24 Valid RIR databaseRIPE 672 100% 67
93.91.74.0/24 Valid RIR databaseRIPE 672 100% 67
93.91.75.0/24 Valid RIR databaseRIPE 672 100% 67
93.91.76.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength93.91.71.0/24ROA 93.91.64.0/20 AS47134 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 93.91.71.0/24.3 of 673
Route object: none93.91.71.0/24No route object for it. A route object for 93.91.64.0/21 with origin AS47134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47134 in the RIR database for the space.3 of 673
Route object: none93.91.67.0/24No route object for it. A route object for 93.91.64.0/21 with origin AS47134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47134 in the RIR database for the space.672 of 673

Route objects not announced

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

93.91.64.0/21RIPEInvalid: maxLength
93.91.72.0/24RIPEInvalid: maxLength
93.91.77.0/24RIPEInvalid: maxLength
93.91.78.0/24RIPEInvalid: maxLength
93.91.79.0/24RIPEInvalid: maxLength
188.213.32.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.