Network · data from 2026-11-12
AS47798 FR-MTVC Martinique TV Cable SAS
Registry name: FR-MTVC Martinique TV Cable SAS, MQ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47798, 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.
| 94.124.216.0/22 | Valid | Nonecovered by 94.124.216.0/21 | 672 100% |
| 89.3.240.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.124.216.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.124.220.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS47798 isn't in PeeringDB, where networks name their AS-SET.
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 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 94.124.216.0/22 | No route object for it. A route object for 94.124.216.0/21 with origin AS47798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47798 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS47798 whose prefix no peer sees AS47798 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.124.216.0/24 | RIPE | Invalid: maxLength |
| 94.124.217.0/24 | RIPE | Invalid: maxLength |
| 94.124.218.0/24 | RIPE | Invalid: maxLength |
| 94.124.219.0/24 | RIPE | Invalid: maxLength |
| 109.203.224.0/19 | RIPE | Valid |
| 212.198.242.0/23 | RIPE | Invalid: origin |
| 212.198.254.0/23 | RIPE | Invalid: origin |
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.