Block 2.59.176.0

← back to the map index · 2.0.0.0/8

Range2.59.176.0 - 2.59.179.255
Prefix2.59.176.0/22
Size1,024 addresses
Statusallocated — operator-held
Registryripencc
Country (delegation)SC
Date20190326
Opaque ida78d93a2-3f9a-44aa-bd4f-1524b7ebe532
Block UUIDd9eb6834-5b4c-515f-9876-bfff1afaf13d
Probes54
RDAP stateown — the registry object is this block
RDAP servicerdap.db.ripe.net
RDAP fetched2026-09-10T22:30:55Z
FlagsC the delegation country and the RDAP country differ

RIR delegation record

registryripencc
countrySC
typeipv4
start2.59.176.0
value1,024
date20190326
statusallocated
extensions['a78d93a2-3f9a-44aa-bd4f-1524b7ebe532']

RDAP summary

handle2.59.176.0 - 2.59.177.255
nameRU-NET259176
typeASSIGNED PA
parent handle2.59.176.0 - 2.59.179.255
start address2.59.176.0
end address2.59.177.255
countryRU
organizationAbuse-C Role
events{"registration": "2019-05-07T09:54:23Z", "last changed": "2024-04-17T18:22:28Z"}
entities4: abuse × 1, administrative × 1, registrant × 2, technical × 1 (contact details are not published)

Probes in this block

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

2.59.179.2 2.59.179.3 2.59.179.5 2.59.179.7 2.59.179.11 2.59.179.13 2.59.179.17 2.59.179.19 2.59.179.23 2.59.179.29 2.59.179.31 2.59.179.37 2.59.179.41 2.59.179.43 2.59.179.47 2.59.179.53 2.59.179.59 2.59.179.61 2.59.179.67 2.59.179.71 2.59.179.73 2.59.179.79 2.59.179.83 2.59.179.89 2.59.179.97 2.59.179.101 2.59.179.103 2.59.179.107 2.59.179.109 2.59.179.113 2.59.179.127 2.59.179.131 2.59.179.137 2.59.179.139 2.59.179.149 2.59.179.151 2.59.179.157 2.59.179.163 2.59.179.167 2.59.179.173 2.59.179.179 2.59.179.181 2.59.179.191 2.59.179.193 2.59.179.197 2.59.179.199 2.59.179.211 2.59.179.223 2.59.179.227 2.59.179.229 2.59.179.233 2.59.179.239 2.59.179.241 2.59.179.251

Who operates this: the layers, side by side

Delegation fileallocated, SC, 20190326
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.