AwanCerahBGP
Home/Indonesia/AS137366
Autonomous System

PT iForte Solusi Infotek - NAP

AS137366IndonesiaAPNIC · since 2018NSPPeering: Selective

IFORTE-NAP-AS-ID

B76/100Good

BGP report

Ranked 1,790 of 3,004 networks in Indonesia, 414 of 482 ISPs and transit networks. World rank 33,880.

  • RPKI ROA30/30
  • IRR route objects8/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv60/10
  • PeeringDB10/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Good
30/30

8 of 8 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

Problem
8/20

3 prefixes have an exact route object, 0 are covered by a larger one, 5 only have objects with another origin, 0 have none.

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

How to fix
  1. Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (5)

Upstream redundancy

Good
15/15

8 upstream, 0 peer, 128 downstream.

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

Upstream (8)

Global visibility

Good
10/10

8 of 8 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

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

Good
10/10

Profile exists, listed at 1 IX.

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

Prefix aggregation

Needs work
3/5

8 IPv4 prefixes could be summarized into 4.

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 32 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 (4)

Put the badge on your website

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