Network · data from 2026-11-12
AS204902 MARITIK INFRAS
Registry name: MARITIK MARITIK SASU, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204902, 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.
| 154.7.0.0/22 | Invalid: origin | None | 2 0%low visibility |
| 154.7.0.0/24 | Invalid: origin | None | 2 0%low visibility |
| 154.7.1.0/24 | Invalid: origin | None | 2 0%low visibility |
| 154.7.2.0/24 | Invalid: origin | None | 2 0%low visibility |
| 154.7.3.0/24 | Invalid: origin | None | 2 0%low visibility |
| 162.12.217.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 2001:978:1b08::/48 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS204902: AS204902:AS-MARITIK. 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 (AS204902 isn't in the set, or no route object for AS204902 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 | AS204902 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS204902:AS-MARITIK | 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 17 are in fix.csv.
- ROA: origin5
- ROA: none2
- Route object: none5
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.7.0.0/22 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS204902 should announce it, add a ROA for AS204902. |
| Route object: none | 154.7.0.0/22 | No route object for it. Add a route object with origin AS204902 in the RIR database for the space. |
| ROA: origin | 154.7.0.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS204902 should announce it, add a ROA for AS204902. |
| Route object: none | 154.7.0.0/24 | No route object for it. Add a route object with origin AS204902 in the RIR database for the space. |
| ROA: origin | 154.7.1.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS204902 should announce it, add a ROA for AS204902. |
| Route object: none | 154.7.1.0/24 | No route object for it. Add a route object with origin AS204902 in the RIR database for the space. |
| ROA: origin | 154.7.2.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS204902 should announce it, add a ROA for AS204902. |
| Route object: none | 154.7.2.0/24 | No route object for it. Add a route object with origin AS204902 in the RIR database for the space. |
| ROA: origin | 154.7.3.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS204902 should announce it, add a ROA for AS204902. |
| Route object: none | 154.7.3.0/24 | No route object for it. Add a route object with origin AS204902 in the RIR database for the space. |
| ROA: none | 162.12.217.0/24 | No ROA covers it. Add a ROA for AS204902, maxLength 24. |
| ROA: none | 2001:978:1b08::/48 | No ROA covers it. Add a ROA for AS204902, maxLength 48. |
| AS-SET: not found | AS204902:AS-MARITIK | PeeringDB names AS204902:AS-MARITIK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS204902 whose prefix no peer sees AS204902 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:6284:4211::/48 | RIPE | Valid |
| 2a0f:85c1:900::/40 | RIPE | Valid |
| 2a0f:85c1:901::/48 | RIPE | Valid |
| 2a0f:85c1:91f::/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.