AwanCerahBGP
Home/Chile/AS262256
Autonomous System

Servicios Informaticos Hostname Ltda

AS262256ChileLACNIC · since 2012ContentPeering: Selective

AS262256

A85/100Excellent

BGP report

Ranked 85 of 329 networks in Chile. World rank 18,592.

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

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

25 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

6 upstream, 7 peer, 0 downstream.

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

Upstream (6)

Global visibility

Needs work
9/10

23 of 25 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 (2)

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

Needs work
8/10

Profile exists, listed at 1 IX. Missing: IRR as-set.

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

Needs work
3/5

25 IPv4 prefixes could be summarized into 13.

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