Network · data from 2026-11-12
AS214351 FEMOIT FEMO IT SOLUTIONS LIMITED
Registry name: FEMOIT FEMO IT SOLUTIONS LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214351, 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.
| 196.251.122.0/24 | No ROA | None | 667 99% |
| 62.60.226.111/32 | No ROA | Nonecovered by 62.60.226.0/24 | 1 0%low visibility |
| 62.60.226.0/24 | No ROA | RIR databaseRIPE | 664 99% |
| 196.251.107.0/24 | No ROA | RIR databaseAFRINIC | 664 99% |
| 192.162.199.0/24 | Valid | RIR databaseRIPE | 664 99% |
AS-SET
AS214351 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 6 are in fix.csv.
- ROA: none4
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.251.122.0/24 | No ROA covers it. Add a ROA for AS214351, maxLength 24. |
| Route object: none | 196.251.122.0/24 | No route object for it. Add a route object with origin AS214351 in the RIR database for the space. |
| ROA: none | 62.60.226.111/32 | No ROA covers it. Add a ROA for AS214351, maxLength 32. |
| Route object: none | 62.60.226.111/32 | No route object for it. A route object for 62.60.226.0/24 with origin AS214351 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214351 in the RIR database for the space. |
| ROA: none | 62.60.226.0/24 | No ROA covers it. Add a ROA for AS214351, maxLength 24. |
| ROA: none | 196.251.107.0/24 | No ROA covers it. Add a ROA for AS214351, maxLength 24. |
Route objects not announced
Every route object with origin AS214351 is announced.
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.