AwanCerahBGP
Home/Indonesia/AS150488
Autonomous System

PT Teknologi Gema Informasi

AS150488IndonesiaAPNIC · since 2022NSPPeering: Open

IDNIC-TGIF-AS-ID

tgif.net.id
PT Teknologi Gema Informasi website
B83/100Good

BGP report

Ranked 1,154 of 3,006 networks in Indonesia. World rank 20,851.

  • RPKI ROA30/30
  • IRR route objects13/20
  • Upstream redundancy10/15
  • Global visibility7/10
  • IPv610/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

3 of 3 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
13/20

2 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

Needs work
10/15

1 upstream, 3 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

Needs work
7/10

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

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 6 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 AS150488The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS150488/rapor"><img src="https://bgp.awancerah.cloud/en/AS150488/rapor.svg" alt="BGP report AS150488"></a>
Markdown
[![BGP report AS150488](https://bgp.awancerah.cloud/en/AS150488/rapor.svg)](https://bgp.awancerah.cloud/en/AS150488/rapor)