RASCOM
Cluster stats
| Netblocks | 31 |
| All fragments | 59 blocks across 4 clusters |
| Cluster ID | 193381987 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.49.237.141/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 80.81.193.166/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 80.249.211.84/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 91.213.211.172/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 185.0.27.56/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.160.84/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.200/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.226.148/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.240.192/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 193.110.224.30/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.188/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.188/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 195.66.226.51/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.223/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 195.208.210.34/32 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:29f0::2:764:1/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::511c:0:2/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a502:764:1/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::511c:1/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7:1:0:2:764:1/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7:b:0:2:764:1/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::188/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::188/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:223/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::210:34/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::1:141/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::172/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10f::511c:84/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12a::192/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::c7/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:15e::56/128 | RASCOM | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
77.4%
of checked blocks have valid RPKI ROA coverage
(24 of 31)
No discrepancies found among checked blocks.
NIC Handles
AS20764