AwanCerahBGP
Home/France/AS39421
Autonomous System

Sapinet SAS

AS39421FranceRIPE NCC · since 2017NSPPeering: Open

SAPINET-AS

A98/100Excellent

BGP report

Ranked 121 of 1,501 networks in France, 66 of 238 ISPs and transit networks. World rank 2,453.

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

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

7 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

Good
15/15

12 upstream, 15 peer, 3 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

Upstream (12)

Global visibility

Good
10/10

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

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 3 IX.

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

Prefix aggregation

Needs work
3/5

6 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.

Dropping invalid routes (ROV)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

Put the badge on your website

BGP report AS39421The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS39421/rapor"><img src="https://bgp.awancerah.cloud/en/AS39421/rapor.svg" alt="BGP report AS39421"></a>
Markdown
[![BGP report AS39421](https://bgp.awancerah.cloud/en/AS39421/rapor.svg)](https://bgp.awancerah.cloud/en/AS39421/rapor)