AwanCerahBGP
Home/Spain/AS2134
Autonomous System

Santander Global Technology and Operations, S.L.

AS2134SpainRIPE NCC · since 1993EnterprisePeering: Open

GSVNET-AS

santanderdigitalservices.com
Santander Global Technology and Operations, S.L. website
B75/100Good

BGP report

Ranked 433 of 977 networks in Spain. World rank 35,157.

  • RPKI ROA20/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv60/10
  • PeeringDB10/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Needs work
20/30

90 of 133 prefixes have a matching ROA (valid). 43 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 (43)

IRR route objects

Good
19/20

117 prefixes have an exact route object, 16 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.

Covered by a larger object (16)

Global visibility

Good
10/10

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

Good
10/10

Profile exists, listed at 6 IX.

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

Prefix aggregation

Problem
1/5

133 IPv4 prefixes could be summarized into 34.

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