Network · data from 2026-11-12
AS213404 YESONGIT NETWORK
Registry name: YstronTek-Networks Suzhou Yesong Information Technology Co., Ltd., CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213404, 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.
| 84.54.2.0/24 | Valid | Other origin onlycovered by 84.54.2.0/23 | 667 99% |
| 84.54.3.0/24 | Valid | Other origin onlycovered by 84.54.2.0/23 | 667 99% |
| 2a14:67c1:a041::/48 | Valid | None | 635 100% |
| 2a14:67c1:a040::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS213404: AS213404:AS-YESONGIT-NETWORKS. 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 (AS213404 isn't in the set, or no route object for AS213404 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 | AS213404 in it | Not covered |
|---|---|---|---|---|---|
| AS213404:AS-YESONGIT-NETWORKS | RIPE | 1 | 1 | 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 7 are in fix.csv.
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 84.54.2.0/24 | Route objects for it name AS51847. A route object for 84.54.2.0/23 with origin AS213404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213404 in the RIR database for the space. |
| Route object: none | 84.54.3.0/24 | Route objects for it name AS51847. A route object for 84.54.2.0/23 with origin AS213404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213404 in the RIR database for the space. |
| Route object: none | 2a14:67c1:a041::/48 | No route object for it. Add a route object with origin AS213404 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213404 whose prefix no peer sees AS213404 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.57.10.0/24 | RADB, RIPE | Valid |
| 84.54.2.0/23 | RADB, RIPE | Valid |
| 154.19.43.0/24 | RADB | No ROA |
| 2a0f:9400:6110::/48 | 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.