Network · data from 2026-11-12
AS205329 Muilties Network
Registry name: Kai-Jung-Chen Kai-Jung Chen, TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205329, 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.
| 36.50.249.62/32 | Valid | Nonecovered by 36.50.248.0/23 | 6 1%low visibility |
| 140.235.12.0/23 | Valid | RIR databaseARIN, RADB | 668 99% |
| 2001:67c:2800::/48 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a0c:9a40:8443::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:9a40:8444::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:9a40:8447::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:9a40:8441::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0c:9a40:8440::/44 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a0c:9a40:8440::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a0c:9a40:8446::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2401:5f20::/32 | Valid | RIR databaseAPNIC, RADB | 631 99% |
| 2a0c:9a40:8449::/48 | Valid | RIR databaseRIPE | 333 52% |
| 36.50.248.0/23 | Valid | RIR databaseAPNIC, RADB | 167 25% |
AS-SET
PeeringDB's irr_as_set for AS205329: AS-MUILTIES. 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 (AS205329 isn't in the set, or no route object for AS205329 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 | AS205329 in it | Not covered |
|---|---|---|---|---|---|
| AS-MUILTIES | RADB | 26 | 5 | Yes | 1 |
| ALTDB (also)3 member sets in no database: AS205329:AS-DOWNSTREAM, AS205329:AS-MAIN, AS205329:AS-SHIJICOLTD | 1 | 1 | Yes | 1 | |
| RIPE (also) | 26 | 5 | Yes | 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 11 are in fix.csv.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 36.50.249.62/32 | No route object for it. A route object for 36.50.248.0/23 with origin AS205329 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS205329 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205329 whose prefix no peer sees AS205329 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 36.50.248.0/24 | APNIC | Valid |
| 140.235.13.0/24 | ARIN, RADB | Valid |
| 2001:67c:2be8::/48 | RADB, RIPE | Valid |
| 2401:5f20::/36 | APNIC, RADB | Valid |
| 2401:5f20:f000::/48 | RADB | Valid |
| 2a0c:9a40:8442::/48 | RIPE | Valid |
| 2a0c:9a40:8445::/48 | RIPE | Valid |
| 2a0c:9a40:8448::/48 | RIPE | Valid |
| 2a0c:9a40:844a::/48 | RIPE | Valid |
| 2a14:7581:6d00::/40 | RIPE | 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.