meteversecloud

Data as of 2026-08-16
Registry
Cluster stats
Netblocks220
IPv6 106 prefixes (largest 2001:12f8:0:2::53:141/128)
Registered in United States (15) · Singapore (8) · Philippines (7) · Hong Kong (7) · India (6) · Japan (6)
Cluster ID222460076
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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 · report an issue

Footprint over time

8 weekly snapshots · JSON
220 +6 netblocks since 2026-07-05
2026-07-05 peak 220 2026-08-16

IP Ranges (220)

showing 50 of 220 — see all — ⬇ export CSV
CIDR Org name Registry Status Confidence
23.181.208.194/32 meteversecloud PEERINGDB ASSIGNED ● high
27.111.228.55/32 meteversecloud PEERINGDB ASSIGNED ● high
27.111.228.96/32 meteversecloud PEERINGDB ASSIGNED ● high
27.111.229.20/32 meteversecloud PEERINGDB ASSIGNED ● high
27.111.231.71/32 meteversecloud PEERINGDB ASSIGNED ● high
27.254.19.250/32 meteversecloud PEERINGDB ASSIGNED ● high
36.255.56.165/32 meteversecloud PEERINGDB ASSIGNED ● high
37.49.232.145/32 meteversecloud PEERINGDB ASSIGNED ● high
37.49.237.155/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.16.246/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.24.194/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.31.190/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.34.222/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.81.141/32 meteversecloud PEERINGDB ASSIGNED ● high
45.68.88.20/32 meteversecloud PEERINGDB ASSIGNED ● high
45.94.12.31/32 meteversecloud PEERINGDB ASSIGNED ● high
45.127.172.141/32 meteversecloud PEERINGDB ASSIGNED ● high
61.245.0.89/32 meteversecloud PEERINGDB ASSIGNED ● high
61.245.0.90/32 meteversecloud PEERINGDB ASSIGNED ● high
61.245.0.91/32 meteversecloud PEERINGDB ASSIGNED ● high
61.245.0.157/32 meteversecloud PEERINGDB ASSIGNED ● high
64.191.234.62/32 meteversecloud PEERINGDB ASSIGNED ● high
80.81.194.237/32 meteversecloud PEERINGDB ASSIGNED ● high
80.249.213.137/32 meteversecloud PEERINGDB ASSIGNED ● high
86.104.125.139/32 meteversecloud PEERINGDB ASSIGNED ● high
101.203.88.123/32 meteversecloud PEERINGDB ASSIGNED ● high
103.16.102.142/32 meteversecloud PEERINGDB ASSIGNED ● high
103.16.103.50/32 meteversecloud PEERINGDB ASSIGNED ● high
103.16.103.52/32 meteversecloud PEERINGDB ASSIGNED ● high
103.16.103.53/32 meteversecloud PEERINGDB ASSIGNED ● high
103.27.170.47/32 meteversecloud PEERINGDB ASSIGNED ● high
103.104.19.115/32 meteversecloud PEERINGDB ASSIGNED ● high
103.104.19.176/32 meteversecloud PEERINGDB ASSIGNED ● high
103.116.193.7/32 meteversecloud PEERINGDB ASSIGNED ● high
103.116.194.7/32 meteversecloud PEERINGDB ASSIGNED ● high
103.121.64.34/32 meteversecloud PEERINGDB ASSIGNED ● high
103.142.207.62/32 meteversecloud PEERINGDB ASSIGNED ● high
103.156.182.16/32 meteversecloud PEERINGDB ASSIGNED ● high
103.162.82.8/32 meteversecloud PEERINGDB ASSIGNED ● high
103.188.179.31/32 meteversecloud PEERINGDB ASSIGNED ● high
103.203.158.167/32 meteversecloud PEERINGDB ASSIGNED ● high
103.218.247.36/32 meteversecloud PEERINGDB ASSIGNED ● high
103.231.152.125/32 meteversecloud PEERINGDB ASSIGNED ● high
103.231.152.126/32 meteversecloud PEERINGDB ASSIGNED ● high
103.231.152.167/32 meteversecloud PEERINGDB ASSIGNED ● high
103.246.232.142/32 meteversecloud PEERINGDB ASSIGNED ● high
103.246.232.246/32 meteversecloud PEERINGDB ASSIGNED ● high
119.11.186.143/32 meteversecloud PEERINGDB ASSIGNED ● high
123.108.12.34/32 meteversecloud PEERINGDB ASSIGNED ● high
123.255.90.43/32 meteversecloud PEERINGDB ASSIGNED ● high

IPv6 ranges (106)

showing the 15 largest allocations
CIDR
2001:12f8:0:2::53:141/128
2001:12f8::217:184/128
2001:12f8::217:212/128
2001:1497::31/128
2001:43f8:1f0::111/128
2001:43f8:1f1::111/128
2001:43f8:60:1::158/128
2001:43f8:6d0::9:96/128
2001:43f8:9d0::924b:a:1/128
2001:43f8:bb1::165/128
2001:43f8:bb1::166/128
2001:504:0:10:0:5:4994:1/128
2001:504:0:1:0:5:4994:1/128
2001:504:0:2:0:5:4994:1/128
2001:504:0:4:0:5:4994:1/128

Customer-delegated space

how is this classified?
Operator infrastructure (named) 220 (100.0%)

Network trust

what's this?
RPKI hygiene: C how networks compare →
69.5% of checked blocks have valid RPKI ROA coverage (153 of 220)
No discrepancies found among checked blocks.

NIC Handles

AS54994