Network · data from 2026-11-12
AS139759 FSMTC - AS139759
Registry name: FMTELECOM-AS-AP - FSM Telecommunications Corporation, FM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139759, 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.
| 2407:4800::/32 | No ROA | RIR databaseAPNIC | 635 100% |
| 2407:4800::/34 | No ROA | RIR databaseAPNIC | 632 99% |
| 119.252.112.0/20 | No ROA | RIR databaseAPNIC | 0 0%low visibility |
| 119.252.112.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 124.109.8.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 119.252.122.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 119.252.112.0/24 | Valid | RIR databaseAPNIC | 0 0%low visibility |
AS-SET
AS139759's PeeringDB record names no 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 6 are in fix.csv.
- ROA: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2407:4800::/32 | No ROA covers it. Add a ROA for AS139759, maxLength 32. |
| ROA: none | 2407:4800::/34 | No ROA covers it. Add a ROA for AS139759, maxLength 34. |
| ROA: none | 119.252.112.0/20 | No ROA covers it. Add a ROA for AS139759, maxLength 20. |
Route objects not announced
Route objects with origin AS139759 whose prefix no peer sees AS139759 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.252.116.0/22 | APNIC | Valid |
| 119.252.118.0/24 | APNIC | Invalid: maxLength |
| 2407:4800::/36 | 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.