Network · data from 2026-11-12
AS215672 MoeChuang Network
Registry name: MoeChuang-Network MoeChuang Network Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215672, 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.
| 162.213.0.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 151.242.10.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 151.243.25.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2a14:67c1:8000::/44 | Valid | None | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS215672: AS215672:AS-MOECHUANG. 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 (AS215672 isn't in the set, or no route object for AS215672 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 | AS215672 in it | Not covered |
|---|---|---|---|---|---|
| AS215672:AS-MOECHUANG | RIPE | 2 | 1 | Yes | 4 |
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 10 are in fix.csv.
- ROA: origin3
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 162.213.0.0/24 | ROAs covering it name AS834, not AS215672. If AS215672 should announce it, add a ROA for AS215672. |
| Route object: none | 162.213.0.0/24 | Route objects for it name AS834. Add a route object with origin AS215672 in the RIR database for the space. |
| ROA: origin | 151.242.10.0/24 | ROAs covering it name AS213347, not AS215672. If AS215672 should announce it, add a ROA for AS215672. |
| Route object: none | 151.242.10.0/24 | Route objects for it name AS213347. Add a route object with origin AS215672 in the RIR database for the space. |
| ROA: origin | 151.243.25.0/24 | ROAs covering it name AS834, AS213347, not AS215672. If AS215672 should announce it, add a ROA for AS215672. |
| Route object: none | 151.243.25.0/24 | Route objects for it name AS213347. Add a route object with origin AS215672 in the RIR database for the space. |
| Route object: none | 2a14:67c1:8000::/44 | No route object for it. Add a route object with origin AS215672 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS215672 whose prefix no peer sees AS215672 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 141.11.219.0/24 | RADB, RIPE | Valid |
| 2a13:9500:fb::/48 | RIPE | Valid |
| 2a14:67c1:8030::/44 | 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.