AwanCerahBGP
Autonomous System

Muscatine Power and Water

AS33734United StatesARIN · since 2005Cable/DSL/ISPPeering: Open

MPW-MACHLINK-NET

mpw.org
Muscatine Power and Water website
D48/100Poor

BGP report

Ranked 11,942 of 19,166 networks in United States. World rank 70,362.

  • RPKI ROA0/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility3/10
  • IPv60/10
  • PeeringDB10/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 49 prefixes have a matching ROA (valid). 49 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 (49)

IRR route objects

Good
20/20

48 prefixes have an exact route object, 1 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 (1)

Upstream redundancy

Good
15/15

4 upstream, 7 peer, 0 downstream.

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

Upstream (4)

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 2 IX.

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

Prefix aggregation

Problem
0/5

49 IPv4 prefixes could be summarized into 2.

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