AwanCerahBGP
Autonomous System

WORLD FIRST COMMUNICATION LTD

AS213607United KingdomRIPE NCC · since 2025Cable/DSL/ISPPeering: Open

WORLD-FIRST-COMMUNICATION-LTD

A97/100Excellent

BGP report

Ranked 237 of 2,318 networks in United Kingdom. World rank 4,027.

  • RPKI ROA30/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB8/10
  • Prefix aggregation5/5

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

RPKI ROA

Good
30/30

108 of 108 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
19/20

93 prefixes have an exact route object, 12 are covered by a larger one, 3 only have objects with another origin, 0 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.
Route object with another origin (3)
Covered by a larger object (12)

Global visibility

Needs work
10/10

107 of 108 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 (1)

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
8/10

Profile exists. Missing: IX connections.

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

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Good
5/5

107 IPv4 prefixes could be summarized into 72.

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

Put the badge on your website

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