Network · data from 2026-11-12
AS24550 Websurfer Nepal Communication System Pvt. Ltd.
Registry name: WEBSURFERNP-AS-NP - Websurfer Nepal Internet Service Provider, NP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24550, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 43.228.192.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 43.228.192.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.228.194.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.228.195.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.252.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.252.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.254.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.254.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.255.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.244.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.245.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.246.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.247.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.32.0/19 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.32.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.32.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.34.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.35.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.36.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.36.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.37.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.38.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.119.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.224.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.224.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.224.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.225.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.226.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.226.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.227.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.228.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.229.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.230.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.231.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.232.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.232.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.233.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.234.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.235.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.237.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.238.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.90.239.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.160.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.160.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.160.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.161.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.162.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.163.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.164.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.165.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.166.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.167.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.168.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.168.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.168.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.169.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.170.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.171.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.172.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.173.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.174.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.91.175.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.94.252.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.225.244.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.225.246.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 116.90.236.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2400:9700::/32 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:5::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:6::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:7::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:8::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:100::/44 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:100::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:101::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:103::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:110::/44 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:110::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:111::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:113::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9700:120::/44 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS24550: AS24550:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS24550 isn't in the set, or no route object for AS24550 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS24550 in it | Not covered |
|---|---|---|---|---|---|
| AS24550:AS-CUSTOMERS | APNIClists itself further down3 member sets in no database: AS-FIRSTLINK-DOWN, AS135327:AS-CUSTOMERS, AS55915:AS-CUSTOMERS | 186 | 19 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 69 are in fix.csv.
- AS-SET: missing member3
- Route object: not announced66
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS24550:AS-CUSTOMERS | AS24550:AS-CUSTOMERS (APNIC) lists AS-FIRSTLINK-DOWN; no IRR database read has it. |
| AS-SET: missing member | AS24550:AS-CUSTOMERS | AS24550:AS-CUSTOMERS (APNIC) lists AS135327:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS24550:AS-CUSTOMERS | AS24550:AS-CUSTOMERS (APNIC) lists AS55915:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS24550 whose prefix no peer sees AS24550 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.228.192.0/23 | APNIC | Valid |
| 43.228.193.0/24 | APNIC | Valid |
| 43.228.194.0/23 | APNIC | Valid |
| 103.94.253.0/24 | APNIC | Valid |
| 103.225.244.0/22 | APNIC | Valid |
| 111.119.32.0/21 | APNIC | Valid |
| 111.119.32.0/23 | APNIC | Valid |
| 111.119.33.0/24 | APNIC | Valid |
| 111.119.34.0/23 | APNIC | Valid |
| 111.119.36.0/23 | APNIC | Valid |
| 111.119.38.0/23 | APNIC | Valid |
| 111.119.48.0/20 | APNIC | Valid |
| 111.119.48.0/21 | APNIC | Valid |
| 111.119.48.0/22 | APNIC | Valid |
| 111.119.48.0/23 | APNIC | Valid |
| 111.119.48.0/24 | APNIC | Valid |
| 111.119.49.0/24 | APNIC | Valid |
| 111.119.50.0/23 | APNIC | Valid |
| 111.119.50.0/24 | APNIC | Valid |
| 111.119.51.0/24 | APNIC | Valid |
| 111.119.52.0/22 | APNIC | Valid |
| 111.119.52.0/23 | APNIC | Valid |
| 111.119.52.0/24 | APNIC | Valid |
| 111.119.53.0/24 | APNIC | Valid |
| 111.119.54.0/23 | APNIC | Valid |
| 111.119.54.0/24 | APNIC | Valid |
| 111.119.55.0/24 | APNIC | Valid |
| 111.119.56.0/21 | APNIC | Valid |
| 111.119.56.0/22 | APNIC | Valid |
| 111.119.56.0/23 | APNIC | Valid |
| 111.119.56.0/24 | APNIC | Valid |
| 111.119.57.0/24 | APNIC | Valid |
| 111.119.58.0/23 | APNIC | Valid |
| 111.119.58.0/24 | APNIC | Valid |
| 111.119.59.0/24 | APNIC | Valid |
| 111.119.60.0/22 | APNIC | Valid |
| 111.119.60.0/23 | APNIC | Valid |
| 111.119.60.0/24 | APNIC | Valid |
| 111.119.61.0/24 | APNIC | Valid |
| 111.119.62.0/23 | APNIC | Valid |
| 111.119.62.0/24 | APNIC | Valid |
| 111.119.63.0/24 | APNIC | Valid |
| 116.90.224.0/22 | APNIC | Valid |
| 116.90.224.0/23 | APNIC | Valid |
| 116.90.228.0/22 | APNIC | Valid |
| 116.90.228.0/23 | APNIC | Valid |
| 116.90.230.0/23 | APNIC | Valid |
| 116.90.232.0/22 | APNIC | Valid |
| 116.90.232.0/23 | APNIC | Valid |
| 116.90.234.0/23 | APNIC | Valid |
| 116.90.236.0/22 | APNIC | Valid |
| 116.90.236.0/23 | APNIC | Valid |
| 116.90.238.0/23 | APNIC | Valid |
| 118.91.160.0/22 | APNIC | Valid |
| 118.91.160.0/23 | APNIC | Valid |
| 118.91.162.0/23 | APNIC | Valid |
| 118.91.164.0/22 | APNIC | Valid |
| 118.91.164.0/23 | APNIC | Valid |
| 118.91.166.0/23 | APNIC | Valid |
| 118.91.168.0/23 | APNIC | Valid |
| 118.91.170.0/23 | APNIC | Valid |
| 118.91.172.0/22 | APNIC | Valid |
| 118.91.172.0/23 | APNIC | Valid |
| 118.91.174.0/23 | APNIC | Valid |
| 2400:9700:20::/44 | APNIC | Valid |
| 2400:9700:120::/48 | APNIC | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.