AwanCerahBGP
Autonomous System

Eli Lilly and Company

AS4249United StatesARIN · since 1995

LILLY-AS

D43/100Poor

BGP report

Ranked 13,351 of 19,165 networks in United States. World rank 74,704.

  • RPKI ROA0/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility9/10
  • IPv60/10
  • PeeringDB0/10
  • Prefix aggregation0/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 246 prefixes have a matching ROA (valid). 246 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 (246)
40.0.0.0/1440.0.0.0/1540.0.40.0/2440.0.49.0/2440.0.176.0/2140.0.184.0/2140.0.248.0/2140.1.0.0/1640.2.0.0/1540.6.0.0/1640.6.0.0/1740.6.40.0/2140.6.128.0/1740.6.210.0/2440.6.211.0/2440.6.212.0/2440.6.213.0/2440.6.214.0/2440.8.0.0/1440.8.0.0/1540.10.0.0/1540.12.0.0/1540.12.0.0/1640.13.0.0/1640.15.0.0/1640.15.128.0/1740.16.0.0/1640.16.0.0/1740.16.128.0/1740.18.0.0/1540.18.0.0/1640.19.0.0/1640.28.0.0/1440.28.0.0/1540.30.0.0/1540.44.0.0/1640.44.0.0/1740.44.12.0/2440.44.13.0/2440.46.0.0/1640.46.0.0/1740.49.0.0/1640.49.0.0/1740.49.128.0/1740.50.0.0/1540.50.0.0/1640.51.0.0/1640.52.0.0/1540.52.0.0/1640.53.0.0/1640.55.0.0/1640.56.0.0/1640.56.0.0/1740.56.128.0/1740.58.0.0/1540.58.0.0/1640.59.0.0/1640.60.0.0/1440.60.0.0/1540.62.0.0/1540.144.0.0/1540.144.0.0/1640.145.0.0/1640.147.0.0/1640.147.0.0/1740.147.128.0/1740.151.0.0/1640.151.0.0/1740.151.128.0/1740.156.0.0/1640.156.0.0/1740.184.0.0/1540.184.0.0/1640.184.0.0/1740.184.120.0/2140.184.128.0/1740.184.164.0/2240.184.168.0/2140.184.176.0/2240.185.0.0/1640.185.0.0/1740.185.48.0/2440.185.128.0/1740.185.140.0/2440.185.144.0/2240.185.148.0/2440.185.190.0/2440.190.0.0/1540.190.0.0/1640.190.0.0/1740.190.128.0/1740.190.130.0/2340.190.160.0/2040.190.176.0/2240.190.224.0/2140.191.0.0/1640.191.0.0/1740.191.128.0/1740.197.0.0/1640.197.0.0/1740.197.128.0/1740.198.0.0/1540.198.0.0/1640.198.10.0/2440.198.16.0/2140.198.24.0/2340.198.220.0/2240.199.0.0/1640.200.0.0/1640.200.0.0/2440.200.2.0/2440.200.6.0/2440.200.7.0/2440.200.20.0/2440.200.24.0/2140.200.40.0/2140.200.48.0/2140.200.64.0/2440.200.73.0/2440.200.88.0/2140.200.104.0/2340.200.108.0/2340.200.110.0/2340.200.123.0/2440.200.128.0/2140.200.136.0/2340.200.138.0/2340.200.140.0/2340.204.0.0/1640.204.0.0/1740.204.0.0/1840.204.64.0/1840.204.128.0/1740.204.192.0/1840.206.0.0/1540.206.0.0/1640.206.0.0/1740.206.128.0/1740.207.0.0/1640.207.0.0/1740.207.128.0/1740.209.0.0/1640.209.0.0/1740.209.0.0/1840.209.64.0/1840.209.128.0/1740.209.128.0/1840.209.192.0/1840.213.0.0/1640.213.0.0/1740.213.0.0/1840.213.64.0/1840.213.192.0/1840.226.0.0/1640.226.0.0/1740.226.0.0/1840.226.128.0/1740.226.192.0/1840.228.0.0/1640.228.0.0/1840.228.64.0/1840.228.128.0/1840.228.192.0/1840.231.0.0/1640.231.0.0/1740.231.0.0/1840.231.128.0/1740.231.192.0/1840.232.0.0/1640.232.0.0/1740.232.0.0/1840.232.64.0/1840.232.128.0/1740.232.128.0/1840.236.0.0/1640.236.0.0/1740.236.0.0/1840.236.64.0/1840.236.128.0/1740.236.128.0/1840.236.192.0/1840.248.0.0/1640.248.0.0/1740.248.128.0/1740.248.192.0/1940.248.224.0/2440.248.240.0/2440.248.244.0/2440.248.246.0/2440.248.247.0/2440.248.248.0/2440.248.252.0/2440.248.253.0/2440.248.255.0/2440.250.0.0/1540.250.0.0/1640.250.5.0/2440.250.6.0/2440.250.7.0/2440.250.13.0/24

Upstream redundancy

Good
15/15

5 upstream, 0 peer, 0 downstream.

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

Upstream (5)

Global visibility

Needs work
9/10

216 of 246 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 (30)

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

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

Problem
0/5

246 IPv4 prefixes could be summarized into 38.

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