Network · data from 2026-11-12
AS134886 Super Sonic Broadband Pvt Ltd
Registry name: SUPERSON-AS - Super Sonic Broadband Pvt Ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134886, 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.121.72.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.73.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.74.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.75.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.156.236.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.156.237.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.181.208.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.190.96.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.190.97.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.61.96.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.173.14.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2406:47c0::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS134886: AS134886: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 (AS134886 isn't in the set, or no route object for AS134886 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 | AS134886 in it | Not covered |
|---|---|---|---|---|---|
| AS134886:AS-CUSTOMERS | APNIC | 0 | 1 | No | 12 |
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 26 are in fix.csv.
- AS-SET: own ASN1
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | AS134886:AS-CUSTOMERS | AS134886 isn't in AS134886:AS-CUSTOMERS (APNIC) once expanded. Add AS134886 to it. |
Route objects not announced
Route objects with origin AS134886 whose prefix no peer sees AS134886 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.93.21.0/24 | APNIC | Valid |
| 103.121.72.0/22 | APNIC, RADB | Valid |
| 103.121.72.0/23 | APNIC | Valid |
| 103.121.74.0/23 | APNIC | Valid |
| 103.142.199.0/24 | APNIC | Valid |
| 103.156.18.0/24 | APNIC | Valid |
| 103.156.236.0/23 | APNIC | Valid |
| 103.179.123.0/24 | APNIC, RADB | Valid |
| 103.190.96.0/23 | APNIC | Valid |
| 2406:47c0::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:1000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:2000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:3000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:4000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:5000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:6000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:7000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:8000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:9000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:a000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:b000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:c000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:d000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:e000::/36 | APNIC | Invalid: maxLength |
| 2406:47c0:f000::/36 | APNIC | Invalid: maxLength |
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.