Network · data from 2026-11-12
AS134467 Syangja Media
Registry name: SMPL-AS-AP - Syangja Media, NP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134467, 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.160.82.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS134467: AS-SET. 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 (AS134467 isn't in the set, or no route object for AS134467 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 | AS134467 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET | RADB | 0 | 1 | No | 1 |
| AFRINIC (also) | 1 | 1 | No | 1 | |
| ARIN (also) | 0 | 1 | No | 1 | |
| RIPE (also)1 member set in no database: AS200105:AS-HK | 38 | 15 | No | 1 |
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 2 are in fix.csv.
- AS-SET: own ASN1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | AS-SET | AS134467 isn't in AS-SET (RADB) once expanded. Add AS134467 to it. |
Route objects not announced
Route objects with origin AS134467 whose prefix no peer sees AS134467 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df4:b540::/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.