bgpreport

Network · data from 2026-11-12

AS49467 EUROTA-ASN INETMAR INTERNET HIZMETLERI BILISM TEKNOLOJILERI SANAYI VE TICARET LIMITED

Registry name: EUROTA-ASN INETMAR INTERNET HIZMETLERI BILISM TEKNOLOJILERI SANAYI VE TICARET LIMITED, TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49467, 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.
37.152.72.0/21 Valid None 2 0%low visibility 2
37.152.72.0/24 Valid RIR databaseRIPE 673 100% 67
37.152.73.0/24 Valid RIR databaseRIPE 673 100% 67
37.152.74.0/24 Valid RIR databaseRIPE 673 100% 67
37.152.75.0/24 Valid RIR databaseRIPE 673 100% 67
37.152.76.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.224.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.225.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.226.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.228.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.230.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.231.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.232.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.233.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.234.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.235.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.236.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.247.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.248.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.249.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.250.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.251.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.252.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.32.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.33.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.34.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.35.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.36.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.37.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.38.0/24 Valid RIR databaseRIPE 673 100% 67
92.42.39.0/24 Valid RIR databaseRIPE 673 100% 67
85.95.245.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
85.95.246.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none37.152.72.0/21No route object for it. Add a route object with origin AS49467 in the RIR database for the space.2 of 673

Route objects not announced

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

37.152.77.0/24RIPEValid
37.152.78.0/24RIPEValid
85.95.227.0/24RIPEValid
85.95.229.0/24RIPEValid
85.95.253.0/24RIPEValid
85.95.254.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.