AwanCerahBGP
Autonomous System

Vodacom

AS29975South AfricaAFRINIC · since 2003

Vodacom

C62/100Fair

BGP report

Ranked 389 of 669 networks in South Africa. World rank 49,787.

  • RPKI ROA27/30
  • IRR route objects17/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv60/10
  • PeeringDB0/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Needs work
27/30

116 of 127 prefixes have a matching ROA (valid). 11 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 (11)

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

Good
10/10

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

Problem
0/10

No PeeringDB profile.

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

Problem
1/5

127 IPv4 prefixes could be summarized into 26.

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