AwanCerahBGP
Autonomous System

Equinix, Inc.

AS32550United StatesARIN · since 2012

EQUINIX-EC-SE

D45/100Poor

BGP report

Ranked 12,880 of 19,171 networks in United States, 1,852 of 2,089 ISPs and transit networks. World rank 73,510.

  • RPKI ROA0/30
  • IRR route objects15/20
  • Upstream redundancy15/15
  • Global visibility0/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Needs work
0/30

0 of 71 prefixes have a matching ROA (valid). 71 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 (71)

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 4 downstream.

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

Upstream (2)

Global visibility

Problem
0/10

2 of 71 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 (69)

IPv6

Good
10/10

5 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

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

Good
5/5

66 IPv4 prefixes could be summarized into 59.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

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