Block 2.59.40.0

← back to the map index · 2.0.0.0/8

Range2.59.40.0 - 2.59.43.255
Prefix2.59.40.0/22
Size1,024 addresses
Statusallocated — operator-held
Registryripencc
Country (delegation)AE
Date20190325
Opaque idc0fc43fa-92f9-4316-9f77-56dbf2b8d55a
Block UUIDe1688d1e-2a43-5df1-81da-cafa58786d7a
Probes108
RDAP stateown — the registry object is this block
RDAP servicerdap.db.ripe.net
RDAP fetched2026-09-10T22:12:24Z
FlagsC the delegation country and the RDAP country differ

RIR delegation record

registryripencc
countryAE
typeipv4
start2.59.40.0
value1,024
date20190325
statusallocated
extensions['c0fc43fa-92f9-4316-9f77-56dbf2b8d55a']

RDAP summary

handle2.59.40.0 - 2.59.41.255
nameRU-TIMEWEB-20190325
typeASSIGNED PA
parent handle2.59.40.0 - 2.59.43.255
start address2.59.40.0
end address2.59.41.255
countryRU
organizationIP-RIPE
events{"registration": "2019-03-25T15:03:52Z", "last changed": "2019-03-25T15:03:52Z"}
entities4: abuse × 1, administrative × 1, registrant × 2, technical × 1 (contact details are not published)

Probes in this block

108 probes; the first 60 are listed. An asterisk means phase 3 heard something back.

2.59.41.2 2.59.41.3 2.59.41.5 2.59.41.7 2.59.41.11 2.59.41.13 2.59.41.17 2.59.41.19 2.59.41.23 2.59.41.29 2.59.41.31 2.59.41.37 2.59.41.41 2.59.41.43 2.59.41.47 2.59.41.53 2.59.41.59 2.59.41.61 2.59.41.67 2.59.41.71 2.59.41.73 2.59.41.79 2.59.41.83 2.59.41.89 2.59.41.97 2.59.41.101 2.59.41.103 2.59.41.107 2.59.41.109 2.59.41.113 2.59.41.127 2.59.41.131 2.59.41.137 2.59.41.139 2.59.41.149 2.59.41.151 2.59.41.157 2.59.41.163 2.59.41.167 2.59.41.173 2.59.41.179 2.59.41.181 2.59.41.191 2.59.41.193 2.59.41.197 2.59.41.199 2.59.41.211 2.59.41.223 2.59.41.227 2.59.41.229 2.59.41.233 2.59.41.239 2.59.41.241 2.59.41.251 2.59.43.2 2.59.43.3 2.59.43.5 2.59.43.7 2.59.43.11 2.59.43.13

Who operates this: the layers, side by side

Delegation fileallocated, AE, 20190325
Registry objectown — the registry object is this block
Routingnot recorded
Authorizationnot recorded
DNS pointing herenot recorded
Certificatenone presented

The registry's verbatim RDAP answer is kept in the local work product dataflow.out/02_ip_block.json and is not published, because it carries registrant contact details.