AwanCerahBGP
Home/Poland/AS201640
Autonomous System

Patryk Kulikowski trading as psHost

AS201640PolandRIPE NCC · since 2026ContentEnterpriseNetwork ServicesPeering: Selective

PSHOST-PL

D51/100Poor

BGP report

Ranked 1,494 of 2,170 networks in Poland, 270 of 304 ISPs and transit networks. World rank 63,166.

  • RPKI ROA0/30
  • IRR route objects15/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

Problem
0/30

4 of 62 prefixes have a matching ROA (valid). 58 invalid, 0 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
  2. 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.
  3. 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.
Invalid prefixes (58)

Upstream redundancy

Good
15/15

3 upstream, 0 peer, 5 downstream.

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

Upstream (3)

Global visibility

Problem
1/10

4 of 62 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 (58)

IPv6

Good
10/10

3 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

Problem
0/5

59 IPv4 prefixes could be summarized into 1.

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