AwanCerahBGP
Home/Czechia/AS63113
Autonomous System

Globecorp Networks

AS63113CzechiaARIN · since 2014NSPPeering: Open

GLOBECORP-NETWORKS

C55/100Fair

BGP report

Ranked 524 of 608 networks in Czechia, 111 of 118 ISPs and transit networks. World rank 59,717.

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

IRR route objects

Good
20/20

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

Upstream redundancy

Good
15/15

14 upstream, 102 peer, 2 downstream.

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

Upstream (14)

Global visibility

Good
10/10

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

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

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