AwanCerahBGP
Home/Turkiye/AS60607
Autonomous System

ICENET TELEKOM HIZMETLERI ANONIM SIRKETI

AS60607TurkiyeRIPE NCC · since 2013

ICENET-AS

B74/100Good

BGP report

Ranked 420 of 907 networks in Turkiye. World rank 36,266.

  • RPKI ROA30/30
  • IRR route objects16/20
  • Upstream redundancy15/15
  • Global visibility8/10
  • IPv60/10
  • PeeringDB0/10
  • Prefix aggregation5/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Good
30/30

4 of 4 prefixes have a matching ROA (valid). 0 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

IRR route objects

Good
16/20

1 prefixes have an exact route object, 3 are covered by a larger one, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

Covered by a larger object (3)

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

Upstream (2)

Global visibility

Needs work
8/10

3 of 4 prefixes are seen by at least half of the full-table feeds worldwide.

Prefixes seen only partly are usually caught by filters (no ROA or route object), too specific, or announced to domestic IXPs only.

How to fix
  1. Check the ROA and route object of those prefixes, and keep them no longer than /24 for IPv4 or /48 for IPv6.
Prefixes with low visibility (1)

IPv6

Problem
0/10

No IPv6 prefix is announced.

Most mobile users and large services already run on IPv6.

How to fix
  1. Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.

PeeringDB

Problem
0/10

No PeeringDB profile.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Good
5/5

4 IPv4 prefixes could be summarized into 3.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

Put the badge on your website

BGP report AS60607The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS60607/rapor"><img src="https://bgp.awancerah.cloud/en/AS60607/rapor.svg" alt="BGP report AS60607"></a>
Markdown
[![BGP report AS60607](https://bgp.awancerah.cloud/en/AS60607/rapor.svg)](https://bgp.awancerah.cloud/en/AS60607/rapor)