AwanCerahBGP
Home/Iran/AS48147
Autonomous System

Asre Pardazeshe Ettelaate Amin Institute

AS48147IranRIPE NCC · since 2016ContentPeering: Restrictive

AminIDC

A87/100Excellent

BGP report

Ranked 60 of 609 networks in Iran, 36 of 94 ISPs and transit networks. World rank 16,216.

  • RPKI ROA29/30
  • IRR route objects20/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB8/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Needs work
29/30

41 of 42 prefixes have a matching ROA (valid). 1 without a ROA.

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

How to fix
  1. Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
  2. The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Prefixes without a ROA (1)

IRR route objects

Good
20/20

39 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

Problem
7/15

1 upstream, 0 peer, 9 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Good
10/10

42 of 42 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.

IPv6

Good
10/10

7 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
8/10

Profile exists. Missing: IX connections.

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

Needs work
3/5

35 IPv4 prefixes could be summarized into 19.

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

How to fix
  1. Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.

Dropping invalid routes (ROV)

Note

Seen passing on 1 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (1)

Put the badge on your website

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