AwanCerahBGP
Home/Singapore/AS55430
Autonomous System

Starhub Ltd

AS55430SingaporeAPNIC · since 2010Peering: Selective

STARHUB-NGNBN

A85/100Excellent

BGP report

Ranked 107 of 468 networks in Singapore. World rank 18,486.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB5/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

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

270 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, 0 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
10/10

264 of 270 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 (6)

IPv6

Good
10/10

154 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
5/10

Profile exists. Missing: IRR as-set, IX connections, prefix counts.

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

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Needs work
3/5

116 IPv4 prefixes could be summarized into 42.

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