AwanCerahBGP
Autonomous System

Austin

AS403201United StatesARIN · since 2026EnterprisePeering: Selective

STEFAN

B72/100Good

BGP report

Ranked 5,420 of 19,165 networks in United States. World rank 38,688.

  • RPKI ROA30/30
  • IRR route objects0/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Good
30/30

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

Needs work
0/20

0 prefixes have an exact route object, 0 are covered by a larger one, 1 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

How to fix
  1. Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
No route object (1)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Good
10/10

1 of 1 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.

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 1 IX.

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

Prefix aggregation

Good
5/5

No IPv4 prefixes.

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

Put the badge on your website

BGP report AS403201The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS403201/rapor"><img src="https://bgp.awancerah.cloud/en/AS403201/rapor.svg" alt="BGP report AS403201"></a>
Markdown
[![BGP report AS403201](https://bgp.awancerah.cloud/en/AS403201/rapor.svg)](https://bgp.awancerah.cloud/en/AS403201/rapor)