Block 179.109.16.0

← back to the map index · 179.0.0.0/8

Range179.109.16.0 - 179.109.31.255
Prefix179.109.16.0/20
Size4,096 addresses
Statusallocated — operator-held
Registrylacnic
Country (delegation)BR
Date20130806
Opaque id140574
Block UUID25f22657-14dd-56ce-854b-bf949456855b
Probes270
RDAP stateown — the registry object is this block
RDAP servicerdap.lacnic.net
RDAP fetched2026-09-10T23:20:22Z
Flagsnone

RIR delegation record

registrylacnic
countryBR
typeipv4
start179.109.16.0
value4,096
date20130806
statusallocated
extensions['140574']

RDAP summary

handle179.109.16.0/20
name208615
typeALLOCATED
parent handle—
start address179.109.16.0
end address179.109.31.255
countryBR
organizationNipBr - NipCable do Brasil Telecom LTDA
events{"registration": "2013-08-06T16:59:08Z", "last changed": "2013-08-06T17:00:06Z"}
entities2: abuse × 1, registrant × 1, technical × 1 (contact details are not published)

Probes in this block

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

179.109.17.2 179.109.17.3 179.109.17.5 179.109.17.7 179.109.17.11 179.109.17.13 179.109.17.17 179.109.17.19 179.109.17.23 179.109.17.29 179.109.17.31 179.109.17.37 179.109.17.41 179.109.17.43 179.109.17.47 179.109.17.53 179.109.17.59 179.109.17.61 179.109.17.67 179.109.17.71 179.109.17.73 179.109.17.79 179.109.17.83 179.109.17.89 179.109.17.97 179.109.17.101 179.109.17.103 179.109.17.107 179.109.17.109 179.109.17.113 179.109.17.127 179.109.17.131 179.109.17.137 179.109.17.139 179.109.17.149 179.109.17.151 179.109.17.157 179.109.17.163 179.109.17.167 179.109.17.173 179.109.17.179 179.109.17.181 179.109.17.191 179.109.17.193 179.109.17.197 179.109.17.199 179.109.17.211 179.109.17.223 179.109.17.227 179.109.17.229 179.109.17.233 179.109.17.239 179.109.17.241 179.109.17.251 179.109.19.2 179.109.19.3 179.109.19.5 179.109.19.7 179.109.19.11 179.109.19.13

Who operates this: the layers, side by side

Delegation fileallocated, BR, 20130806
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.