Network · data from 2026-11-12
AS41833 Moscanet
Registry name: MOSCANET Moscanet SAL, LB · PeeringDB
82IPv4 routes
100.0% RPKI valid · 98.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS41833, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS41833, 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.
| 185.58.200.0/22 | Valid | None | 672 100% |
| 89.249.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.49.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.51.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.59.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.141.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.187.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.188.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.138.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.58.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.58.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.58.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.58.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.227.248.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.227.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.249.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 93.185.224.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 93.185.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.141.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 141.138.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.141.57.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS41833'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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.58.200.0/22 | No route object for it. Add a route object with origin AS41833 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41833 whose prefix no peer sees AS41833 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a02:f50::/32 | 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.