AwanCerahBGP
Home/Italy/AS13113
Autonomous System

ISI Line srl

AS13113ItalyRIPE NCC · since 2000Cable/DSL/ISPPeering: Selective

ISILINE-AS

A86/100Excellent

BGP report

Ranked 367 of 1,138 networks in Italy, 144 of 199 ISPs and transit networks. World rank 17,042.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility1/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Good
30/30

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

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

Global visibility

Problem
1/10

13 of 148 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 (135)
5.172.208.0/240.8%5.172.209.0/240.8%5.172.210.0/240.8%5.172.211.0/240.8%5.172.212.0/240.8%5.172.213.0/240.8%5.172.215.0/240.8%5.198.224.0/240.8%5.198.225.0/240.8%5.198.226.0/240.8%5.198.227.0/240.8%5.198.228.0/240.8%5.198.229.0/240.8%5.198.230.0/240.8%5.198.231.0/240.8%5.198.232.0/240.8%5.198.233.0/240.8%5.198.234.0/240.8%5.198.235.0/240.8%5.198.236.0/240.8%5.198.237.0/240.8%5.198.238.0/240.8%5.198.239.0/240.8%37.60.32.0/240.8%37.60.33.0/240.8%37.60.34.0/240.8%37.60.35.0/240.8%37.60.36.0/240.8%37.60.37.0/240.8%37.60.38.0/240.8%37.60.39.0/240.8%87.253.96.0/240.8%87.253.97.0/240.8%87.253.98.0/240.8%87.253.99.0/240.8%87.253.100.0/240.8%87.253.101.0/240.8%87.253.102.0/240.8%87.253.103.0/240.8%87.253.104.0/240.8%87.253.105.0/240.8%87.253.106.0/240.8%87.253.107.0/240.8%87.253.108.0/240.8%87.253.109.0/240.8%87.253.110.0/240.8%87.253.111.0/240.8%87.253.112.0/240.8%87.253.113.0/240.8%87.253.114.0/240.8%87.253.115.0/240.8%87.253.116.0/240.8%87.253.117.0/240.8%87.253.118.0/240.8%87.253.119.0/240.8%87.253.120.0/240.8%87.253.121.0/240.8%87.253.122.0/240.8%87.253.123.0/240.8%87.253.124.0/240.8%87.253.125.0/240.8%87.253.126.0/240.8%87.253.127.0/240.8%93.88.112.0/240.8%93.88.113.0/240.8%93.88.114.0/240.8%93.88.115.0/240.8%93.88.116.0/240.8%93.88.117.0/240.8%93.88.118.0/240.8%93.88.119.0/240.8%93.88.120.0/240.8%93.88.121.0/240.8%93.88.122.0/240.8%93.88.123.0/240.8%93.88.124.0/240.8%93.88.125.0/240.8%93.88.126.0/240.8%93.88.127.0/240.8%109.75.112.0/240.8%109.75.113.0/240.8%109.75.114.0/240.8%109.75.115.0/240.8%109.75.116.0/240.8%109.75.117.0/240.8%109.75.118.0/240.8%109.75.119.0/241.1%109.75.120.0/240.8%109.75.121.0/240.8%109.75.122.0/240.8%109.75.123.0/240.8%109.75.124.0/240.8%109.75.125.0/240.8%109.75.126.0/240.8%109.75.127.0/240.8%185.3.252.0/240.8%185.3.253.0/240.8%185.3.254.0/240.8%185.3.255.0/240.8%185.145.84.0/240.8%185.145.85.0/240.8%185.145.86.0/240.8%185.145.87.0/240.8%213.144.64.0/240.8%213.144.65.0/240.8%213.144.66.0/240.8%213.144.67.0/240.8%213.144.68.0/240.8%213.144.69.0/240.8%213.144.70.0/240.8%213.144.71.0/240.8%213.144.72.0/240.8%213.144.73.0/240.8%213.144.74.0/240.8%213.144.75.0/240.8%213.144.76.0/240.8%213.144.77.0/240.8%213.144.78.0/240.8%213.144.79.0/240.8%213.144.80.0/240.8%213.144.81.0/240.8%213.144.82.0/240.8%213.144.83.0/240.8%213.144.84.0/240.8%213.144.85.0/240.8%213.144.86.0/240.8%213.144.87.0/240.8%213.144.88.0/240.8%213.144.89.0/240.8%213.144.90.0/240.8%213.144.91.0/240.8%213.144.92.0/240.8%213.144.93.0/240.8%213.144.94.0/240.8%213.144.95.0/240.8%

IPv6

Good
10/10

2 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

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
0/5

146 IPv4 prefixes could be summarized into 10.

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