AwanCerahBGP
Home/Indonesia/AS155021
Autonomous System

PT Access Jaringan Nusantara

AS155021IndonesiaAPNIC · since 2026Cable/DSL/ISPPeering: Open

IDNIC-AJNSKD-ID

ptajn.net
PT Access Jaringan Nusantara website
A90/100Excellent

BGP report

Ranked 538 of 3,003 networks in Indonesia. World rank 11,818.

  • RPKI ROA30/30
  • IRR route objects10/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/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

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

Needs work
10/20

1 prefixes have an exact route object, 0 are covered by a larger one, 1 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.
No route object (1)

Upstream redundancy

Good
15/15

3 upstream, 10 peer, 0 downstream.

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

Upstream (3)

Global visibility

Good
10/10

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

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 3 IX.

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

Prefix aggregation

Good
5/5

1 IPv4 prefixes could be summarized into 1.

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

Put the badge on your website

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