Network · data from 2026-11-12
AS24039 Marlink - ITC Global (Australia)
Registry name: MARLINK-AS-NET-AP - Marlink AS, NO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24039, 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.19.218.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 103.193.208.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.193.209.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.190.223.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS24039: AS24039:AS-ITC-GLOBAL. 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 (AS24039 isn't in the set, or no route object for AS24039 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 | AS24039 in it | Not covered |
|---|---|---|---|---|---|
| AS24039:AS-ITC-GLOBAL | APNIC | 0 | 1 | No | 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 9 are in fix.csv.
- ROA: none1
- Route object: none1
- AS-SET: own ASN1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.19.218.0/24 | No ROA covers it. Add a ROA for AS24039, maxLength 24. |
| Route object: none | 103.19.218.0/24 | Route objects for it name AS7545, AS24130. Add a route object with origin AS24039 in the RIR database for the space. |
| AS-SET: own ASN | AS24039:AS-ITC-GLOBAL | AS24039 isn't in AS24039:AS-ITC-GLOBAL (APNIC) once expanded. Add AS24039 to it. |
Route objects not announced
Route objects with origin AS24039 whose prefix no peer sees AS24039 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.193.208.0/23 | APNIC | Valid |
| 103.193.208.0/24 | APNIC | Valid |
| 103.193.210.0/23 | APNIC | Valid |
| 103.193.210.0/24 | APNIC | Valid |
| 103.193.211.0/24 | APNIC | Valid |
| 203.190.222.0/23 | RADB | No ROA |
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.