AwanCerahBGP
Autonomous System

Safe Swiss Cloud AG

AS62320SwitzerlandRIPE NCC · since 2013Peering: Open

SSC-AS

D43/100Poor

BGP report

Ranked 727 of 794 networks in Switzerland. World rank 74,822.

  • RPKI ROA0/30
  • IRR route objects15/20
  • Upstream redundancy7/15
  • Global visibility5/10
  • IPv610/10
  • PeeringDB5/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Problem
0/30

4 of 8 prefixes have a matching ROA (valid). 4 invalid, 0 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
  2. 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.
  3. 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.
Invalid prefixes (4)

IRR route objects

Needs work
15/20

3 prefixes have an exact route object, 4 are covered by a larger one, 1 only have objects with another origin, 0 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.
Route object with another origin (1)
Covered by a larger object (4)

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
5/10

4 of 8 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 (4)

IPv6

Good
10/10

1 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

Problem
1/5

7 IPv4 prefixes could be summarized into 2.

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