Network · data from 2026-11-12
AS136636 Sharplink Wireless Solution
Registry name: RSBI-AS - Sharplink Wireless Solution Pvt Ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136636, 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.
| 103.101.108.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.101.108.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.101.110.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df4:5a40::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 103.101.108.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
| 103.101.109.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
| 103.101.110.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
| 103.101.111.0/24 | Valid | RIR databaseAPNIC | 43 6%low visibility |
AS-SET
AS136636's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS136636 is announced.
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.