AwanCerahBGP
Home/Nepal/AS23752
Autonomous System

Nepal Telecommunications Corporation, Internet Services,

AS23752NepalAPNIC · since 2003NSPPeering: Selective

NPTELECOM-NP-AS

A95/100Excellent

BGP report

Ranked 12 of 152 networks in Nepal, 6 of 25 ISPs and transit networks. World rank 5,679.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/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

Good
30/30

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

Good
20/20

122 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

4 upstream, 0 peer, 9 downstream.

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

Upstream (4)

Global visibility

Needs work
10/10

120 of 122 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 (2)

IPv6

Good
10/10

16 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

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

106 IPv4 prefixes could be summarized into 11.

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