Network · data from 2026-11-12
AS135413 SSTNTECHNOLOGY-AS-AP
Registry name: SSTNTECHNOLOGY-AS-AP - SSTN Technology, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135413, 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.77.16.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 203.153.62.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.139.8.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.8.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.9.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.173.107.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 165.101.239.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df0:6180::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS135413: APNIC::AS135413:AS-SSTN. 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 (AS135413 isn't in the set, or no route object for AS135413 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 | AS135413 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS135413:AS-SSTN | APNIC | 0 | 1 | No | 8 |
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 8 are in fix.csv.
- ROA: origin2
- Route object: none2
- AS-SET: own ASN1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.77.16.0/24 | ROAs covering it name AS58689, not AS135413. If AS135413 should announce it, add a ROA for AS135413. |
| Route object: none | 103.77.16.0/24 | Route objects for it name AS58689. Add a route object with origin AS135413 in the RIR database for the space. |
| ROA: origin | 203.153.62.0/24 | ROAs covering it name AS58689, not AS135413. If AS135413 should announce it, add a ROA for AS135413. |
| Route object: none | 203.153.62.0/24 | Route objects for it name AS58689. Add a route object with origin AS135413 in the RIR database for the space. |
| AS-SET: own ASN | APNIC::AS135413:AS-SSTN | AS135413 isn't in AS135413:AS-SSTN (APNIC) once expanded. Add AS135413 to it. |
Route objects not announced
Route objects with origin AS135413 whose prefix no peer sees AS135413 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.132.248.0/22 | APNIC | Valid |
| 103.132.251.0/24 | APNIC | Valid |
| 103.216.134.0/24 | RADB | No ROA |
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.