Lebara Ltd
Lebara-AS
BGP report
Ranked 708 of 2,317 networks in United Kingdom. World rank 17,317.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good14 of 14 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 work11 prefixes have an exact route object, 0 are covered by a larger one, 3 have none.
Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.
- 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.
- Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
No route object (3)
Upstream redundancy
Good14 upstream, 47 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good14 of 14 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
Good1 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
ProblemNo PeeringDB profile.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
- Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.
Prefix aggregation
Good13 IPv4 prefixes could be summarized into 10.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS33921/rapor"><img src="https://bgp.awancerah.cloud/en/AS33921/rapor.svg" alt="BGP report AS33921"></a>
[](https://bgp.awancerah.cloud/en/AS33921/rapor)