AwanCerahBGP
Home/Thailand/AS4621
Autonomous System

UNINET-TH

AS4621ThailandAPNIC · since 1995Educational/ResearchPeering: Open

UNINET-AS-AP

A85/100Excellent

BGP report

Ranked 103 of 470 networks in Thailand, 46 of 77 ISPs and transit networks. World rank 18,259.

  • RPKI ROA25/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility6/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Needs work
25/30

68 of 82 prefixes have a matching ROA (valid). 14 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 (14)

IRR route objects

Needs work
19/20

75 prefixes have an exact route object, 6 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)
Covered by a larger object (6)

IPv6

Good
10/10

3 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 4 IX.

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

Prefix aggregation

Problem
0/5

79 IPv4 prefixes could be summarized into 10.

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