Navice Communications B.V.
BGP inherited
Cluster stats
| Netblocks | 61 |
| All fragments | 102 blocks across 2 clusters |
| Cluster ID | 191479948 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
61
0 netblocks since 2026-07-05
2026-07-05
peak 61
2026-07-06
IP Ranges (61)
showing 50 of 61 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 149.112.50.53/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 149.112.60.34/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.0.30.65/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.134.44/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.138.16/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.60/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.61/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.62/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.63/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.155.24/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.170.138/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.69/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.225.46/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 193.189.83.168/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 193.201.150.204/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 193.239.116.76/32 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::53/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e2::34/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a503:8230:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:33::a103:8230:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:93:1:0:3:8230:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:9e:0:2:1912:0:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a513:7490:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1::60/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1::61/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1::62/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1::63/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d8::38:230/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:11c:1:0:38:2301:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:11f:1:0:382:30:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:11f:be00:38:230:0:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0c:b641:700::137:490/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0c:b641:701:0:a5:137:490:1/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:7::109/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:10::10f/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:11::10d/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:24::118/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:25::10b/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:32::103/128 | Navice Communications B.V. | PEERINGDB | ASSIGNED | ● high |
| 2a0e:46c4:4000::/34 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46::/36 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:800::/38 | Navice Communications LLC | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1000::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1200::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1400::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1600::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1800::/39 | Navice Communications LLC | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1a00::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1c00::/39 | Navice Communications LLC | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:7d46:1e00::/39 | Navice Communications B.V. | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
60.7%
of checked blocks have valid RPKI ROA coverage
(37 of 61)
No discrepancies found among checked blocks.
NIC Handles
AS38230
DUMY-RIPE
DUMY-RIPE
MNT-BOOT
NAVICE
ORG-NCB6-RIPE
ORG-NCL40-RIPE