Network · data from 2026-11-12
AS142014 MARVEL LINK
Registry name: MARVELLINKLIMITED-AS-AP - MARVEL LINK LIMITED, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142014, 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.246.228.0/24 | No ROA | Other origin only | 673 100% |
| 103.246.229.0/24 | No ROA | Other origin only | 673 100% |
| 103.246.230.0/24 | No ROA | Other origin only | 673 100% |
| 103.246.231.0/24 | No ROA | Other origin only | 673 100% |
| 103.246.228.0/23 | No ROA | Other origin only | 461 68% |
| 103.246.230.0/23 | No ROA | Other origin only | 460 68% |
| 103.164.224.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.164.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.164.225.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS142014: AS-SET-MARVELLINKLIMITED. 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 (AS142014 isn't in the set, or no route object for AS142014 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 | AS142014 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET-MARVELLINKLIMITED | APNIC | 3 | 1 | Yes | 6 |
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 13 are in fix.csv.
- ROA: none6
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.246.228.0/24 | No ROA covers it. Add a ROA for AS142014, maxLength 24. |
| Route object: none | 103.246.228.0/24 | Route objects for it name AS24088, AS38082, AS45348, AS64050, AS134829, AS152194. Add a route object with origin AS142014 in the RIR database for the space. |
| ROA: none | 103.246.229.0/24 | No ROA covers it. Add a ROA for AS142014, maxLength 24. |
| Route object: none | 103.246.229.0/24 | Route objects for it name AS24088, AS45348, AS134829, AS141761, AS152194. Add a route object with origin AS142014 in the RIR database for the space. |
| ROA: none | 103.246.230.0/24 | No ROA covers it. Add a ROA for AS142014, maxLength 24. |
| Route object: none | 103.246.230.0/24 | Route objects for it name AS24088, AS45348, AS134829, AS152194. Add a route object with origin AS142014 in the RIR database for the space. |
| ROA: none | 103.246.231.0/24 | No ROA covers it. Add a ROA for AS142014, maxLength 24. |
| Route object: none | 103.246.231.0/24 | Route objects for it name AS24088, AS45348, AS134829, AS152194. Add a route object with origin AS142014 in the RIR database for the space. |
| ROA: none | 103.246.228.0/23 | No ROA covers it. Add a ROA for AS142014, maxLength 23. |
| Route object: none | 103.246.228.0/23 | Route objects for it name AS24088, AS45348, AS134829. Add a route object with origin AS142014 in the RIR database for the space. |
| ROA: none | 103.246.230.0/23 | No ROA covers it. Add a ROA for AS142014, maxLength 23. |
| Route object: none | 103.246.230.0/23 | Route objects for it name AS24088, AS45348, AS134829. Add a route object with origin AS142014 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS142014 whose prefix no peer sees AS142014 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2407:4340::/32 | APNIC, RADB | 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.