Network · data from 2026-11-12
AS56140 ModernOne Data Solutions Sdn Bhd
Registry name: NOCSER-MY - ModernOne Data Solutions Sdn. Bhd., MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56140, 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.
| 42.0.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 42.0.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 42.0.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 42.0.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 2407:c600:1::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS56140: AS56140:AS-NOCSER-NET. 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 (AS56140 isn't in the set, or no route object for AS56140 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 | AS56140 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS56140:AS-NOCSER-NET | In no IRR database read today. | |||||
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.
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS56140:AS-NOCSER-NET | PeeringDB names AS56140:AS-NOCSER-NET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS56140 whose prefix no peer sees AS56140 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 42.0.28.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.140.6.0/24 | APNIC | Valid |
| 103.140.7.0/24 | APNIC | Valid |
| 2407:c600::/32 | APNIC | Valid |
| 2407:c600:2::/48 | APNIC | Valid |
| 2407:c600:3::/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.