Gcore

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks251
IPv6 127 prefixes (largest 2a03:97c0::/32)
Registered in United States (21) · Germany (12) · Brazil (8) · Japan (8) · Netherlands (8) · Singapore (5)
All fragments 260 blocks across 5 clusters
Cluster ID213687263
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
251 +2 netblocks since 2026-07-05
2026-07-05 peak 251 2026-07-26

IP Ranges (251)

showing 50 of 251 — see all — ⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.204/32 Gcore PEERINGDB ASSIGNED ● high
27.111.228.222/32 Gcore PEERINGDB ASSIGNED ● high
27.111.230.91/32 Gcore PEERINGDB ASSIGNED ● high
31.44.186.19/32 Gcore PEERINGDB ASSIGNED ● high
36.255.56.162/32 Gcore PEERINGDB ASSIGNED ● high
37.49.232.50/32 Gcore PEERINGDB ASSIGNED ● high
37.49.237.175/32 Gcore PEERINGDB ASSIGNED ● high
45.68.16.239/32 Gcore PEERINGDB ASSIGNED ● high
45.68.24.112/32 Gcore PEERINGDB ASSIGNED ● high
45.68.64.10/32 Gcore PEERINGDB ASSIGNED ● high
45.68.74.59/32 Gcore PEERINGDB ASSIGNED ● high
45.68.80.246/32 Gcore PEERINGDB ASSIGNED ● high
45.68.82.171/32 Gcore PEERINGDB ASSIGNED ● high
45.68.92.13/32 Gcore PEERINGDB ASSIGNED ● high
45.94.12.40/32 Gcore PEERINGDB ASSIGNED ● high
45.127.172.78/32 Gcore PEERINGDB ASSIGNED ● high
45.183.47.184/32 Gcore PEERINGDB ASSIGNED ● high
64.191.233.31/32 Gcore PEERINGDB ASSIGNED ● high
64.191.233.41/32 Gcore PEERINGDB ASSIGNED ● high
77.241.206.110/32 Gcore PEERINGDB ASSIGNED ● high
80.81.193.252/32 Gcore PEERINGDB ASSIGNED ● high
80.81.194.82/32 Gcore PEERINGDB ASSIGNED ● high
80.249.210.150/32 Gcore PEERINGDB ASSIGNED ● high
80.249.214.101/32 Gcore PEERINGDB ASSIGNED ● high
86.104.125.173/32 Gcore PEERINGDB ASSIGNED ● high
91.210.16.223/32 Gcore PEERINGDB ASSIGNED ● high
101.203.78.38/32 Gcore PEERINGDB ASSIGNED ● high
101.203.88.201/32 Gcore PEERINGDB ASSIGNED ● high
101.203.89.26/32 Gcore PEERINGDB ASSIGNED ● high
103.16.102.193/32 Gcore PEERINGDB ASSIGNED ● high
103.26.68.207/32 Gcore PEERINGDB ASSIGNED ● high
103.27.170.21/32 Gcore PEERINGDB ASSIGNED ● high
103.41.12.35/32 Gcore PEERINGDB ASSIGNED ● high
103.77.108.50/32 Gcore PEERINGDB ASSIGNED ● high
103.116.194.63/32 Gcore PEERINGDB ASSIGNED ● high
103.162.254.114/32 Gcore PEERINGDB ASSIGNED ● high
103.203.158.34/32 Gcore PEERINGDB ASSIGNED ● high
103.231.152.34/32 Gcore PEERINGDB ASSIGNED ● high
103.246.232.145/32 Gcore PEERINGDB ASSIGNED ● high
103.247.139.62/32 Gcore PEERINGDB ASSIGNED ● high
116.206.112.47/32 Gcore PEERINGDB ASSIGNED ● high
139.150.100.147/32 Gcore PEERINGDB ASSIGNED ● high
139.150.100.148/32 Gcore PEERINGDB ASSIGNED ● high
149.112.11.3/32 Gcore PEERINGDB ASSIGNED ● high
149.112.48.12/32 Gcore PEERINGDB ASSIGNED ● high
176.126.38.86/32 Gcore PEERINGDB ASSIGNED ● high
178.18.226.230/32 Gcore PEERINGDB ASSIGNED ● high
178.18.236.129/32 Gcore PEERINGDB ASSIGNED ● high
179.0.201.104/32 Gcore PEERINGDB ASSIGNED ● high
185.0.27.3/32 Gcore PEERINGDB ASSIGNED ● high

IPv6 ranges (127)

showing the 15 largest allocations
CIDR
2a03:97c0::/32
2a03:97c1::/32
2a01:4f8:13a:2823::/64
2a01:4f8:161:4208::/64
2a01:4f8:173:16dd::/64
2a01:4f8:202:6467::/64
2a01:4f8:241:49d0::/64
2a01:4f8:a1:10b::/64
2001:12f8:0:2::246/128
2001:12f8:0:2::54:171/128
2001:12f8:0:9::146:59/128
2001:12f8::214:62/128
2001:12f8::217:121/128
2001:12f8::222:16/128
2001:12f8::222:229/128

Customer-delegated space

how is this classified?
Operator infrastructure (named) 239 (95.2%)
Unclassified 12 (4.8%)

Network trust

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

NIC Handles

AS199524 DUMY-RIPE DUMY-RIPE GCL1-MNT HOS-GUN WGIT-MNT