Network · data from 2026-11-12
AS43925 MOLDCELL_AS MOLDCELL S.A.
Registry name: MOLDCELL_AS MOLDCELL S.A., MD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43925, 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.
| 178.76.96.0/22 | Valid | Nonecovered by 178.76.96.0/21 | 0 0%low visibility |
| 178.76.100.0/22 | Valid | Nonecovered by 178.76.96.0/21 | 0 0%low visibility |
| 37.34.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.96.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.98.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.112.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 79.170.224.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 79.170.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.45.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.45.0.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.45.2.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.113.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.132.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.134.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.140.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.144.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.148.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.152.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.154.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.158.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 178.76.76.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 178.76.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 178.76.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 178.76.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 178.76.112.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 37.34.105.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.34.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.34.107.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 79.170.228.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 93.113.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 93.113.116.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 79.170.226.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 2a00:f900::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS43925 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 30 are in fix.csv.
- Route object: none2
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 178.76.96.0/22 | No route object for it. A route object for 178.76.96.0/21 with origin AS43925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43925 in the RIR database for the space. |
| Route object: none | 178.76.100.0/22 | No route object for it. A route object for 178.76.96.0/21 with origin AS43925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43925 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43925 whose prefix no peer sees AS43925 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.34.96.0/19 | RIPE | Valid |
| 37.34.96.0/20 | RIPE | Valid |
| 37.34.104.0/21 | RIPE | Valid |
| 37.34.104.0/24 | RIPE | Valid |
| 94.139.128.0/21 | RIPE | Valid |
| 94.139.128.0/23 | RIPE | Valid |
| 94.139.130.0/23 | RIPE | Valid |
| 94.139.136.0/21 | RIPE | Valid |
| 94.139.136.0/23 | RIPE | Valid |
| 94.139.138.0/23 | RIPE | Valid |
| 94.139.142.0/23 | RIPE | Valid |
| 94.139.143.0/24 | RIPE | Valid |
| 94.139.144.0/20 | RIPE | Valid |
| 94.139.144.0/23 | RIPE | Valid |
| 94.139.146.0/23 | RIPE | Valid |
| 94.139.150.0/23 | RIPE | Valid |
| 94.139.156.0/22 | RIPE | Valid |
| 94.139.156.0/23 | RIPE | Valid |
| 178.76.64.0/18 | RIPE | No ROA |
| 178.76.80.0/21 | RIPE | Valid |
| 178.76.88.0/21 | RIPE | Valid |
| 178.76.96.0/21 | RIPE | Valid |
| 178.76.104.0/21 | RIPE | Valid |
| 178.76.112.0/21 | RIPE | Valid |
| 178.76.120.0/21 | RIPE | Valid |
| 2a00:f900::/29 | RIPE | No ROA |
| 2a00:f901::/32 | RIPE | No ROA |
| 2a00:f902::/32 | RIPE | 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.