RISE.ph
Cluster stats
Netblocks45
Cluster ID193384860
RegistryPEERINGDB
Customersfind 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 (45)

⬇ export CSV
CIDR Org name Registry Status Confidence
27.111.228.206/32 RISE.ph PEERINGDB ASSIGNED ● high
36.255.57.40/32 RISE.ph PEERINGDB ASSIGNED ● high
45.114.21.230/32 RISE.ph PEERINGDB ASSIGNED ● high
80.81.195.238/32 RISE.ph PEERINGDB ASSIGNED ● high
80.249.213.247/32 RISE.ph PEERINGDB ASSIGNED ● high
103.16.102.41/32 RISE.ph PEERINGDB ASSIGNED ● high
103.41.12.39/32 RISE.ph PEERINGDB ASSIGNED ● high
103.104.19.5/32 RISE.ph PEERINGDB ASSIGNED ● high
103.104.19.23/32 RISE.ph PEERINGDB ASSIGNED ● high
103.121.64.42/32 RISE.ph PEERINGDB ASSIGNED ● high
103.125.245.4/32 RISE.ph PEERINGDB ASSIGNED ● high
103.125.245.5/32 RISE.ph PEERINGDB ASSIGNED ● high
103.162.254.45/32 RISE.ph PEERINGDB ASSIGNED ● high
116.89.244.3/32 RISE.ph PEERINGDB ASSIGNED ● high
116.89.244.4/32 RISE.ph PEERINGDB ASSIGNED ● high
185.1.47.73/32 RISE.ph PEERINGDB ASSIGNED ● high
194.68.123.5/32 RISE.ph PEERINGDB ASSIGNED ● high
194.68.128.5/32 RISE.ph PEERINGDB ASSIGNED ● high
195.66.227.11/32 RISE.ph PEERINGDB ASSIGNED ● high
198.32.172.114/32 RISE.ph PEERINGDB ASSIGNED ● high
203.190.231.34/32 RISE.ph PEERINGDB ASSIGNED ● high
206.72.211.183/32 RISE.ph PEERINGDB ASSIGNED ● high
210.173.177.124/32 RISE.ph PEERINGDB ASSIGNED ● high
2001:478:172::114/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:504:13::211:183/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8::f9b7:0:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8:1::a506:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8:4::f9b7:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8:d:fe::5/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8:d:ff::5/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7f8:36::f9b7:0:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:7fa:7:1:0:6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:de8:4::6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:de8:5::6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:de8:7::6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:de8:12:100::41/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:ded::27/128 RISE.ph PEERINGDB ASSIGNED ● high
2001:df6:480::f9b7:0:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2400:efa0::6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0::6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0::6:3927:2/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0:0:1:0:6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0:0:1:0:6:3927:2/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0:0:2:0:6:3927:1/128 RISE.ph PEERINGDB ASSIGNED ● high
2401:fdc0:0:2:0:6:3927:2/128 RISE.ph PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
93.3% of checked blocks have valid RPKI ROA coverage (42 of 45)
No discrepancies found among checked blocks.

NIC Handles

AS63927