AwanCerahBGP
Home/Indonesia/AS152017
Autonomous System

PT Digtel Tech Solutions

AS152017IndonesiaAPNIC · since 2023Cable/DSL/ISPPeering: Open

IDNIC-DIGTELTECH-AS-ID

digteltech.co.id
PT Digtel Tech Solutions website
B80/100Good

BGP report

Ranked 1,351 of 3,003 networks in Indonesia. World rank 26,238.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy7/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

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

Good
20/20

2 prefixes have an exact route object, 0 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.

Upstream redundancy

Problem
7/15

1 upstream, 2 peer, 0 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

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

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 2 IX.

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

Prefix aggregation

Needs work
3/5

2 IPv4 prefixes could be summarized into 1.

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.

Put the badge on your website

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