Data as of Nov 14, 2026

31.169.72.0/24

1 residential-proxy exit · 30 days

Netfactor Telekominikasyon ve Teknoloji Hizmetleri San. ve Tic. A.S.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

13 observations

Proxy providers listing exits

  • Ake.net
  • DataImpulse

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.169.69.0 - 31.169.72.2551,024TR-NETFACTORTELAS-20110328Netfactor Telekominikasyon ve Teknoloji Hizmetleri San. ve Tic. A.S. (ORG-NTVT1-RIPE) · TRALLOCATED PAMay 9, 2022abuse@netfactor.net.tr
└ 31.169.72.0/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.16/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.32/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.48/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.64/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.80/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.96/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.112/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.128/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.144/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.160/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.176/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.192/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.208/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.224/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328
└ 31.169.72.240/2816Netfactor-CustomerNetfactor Customer NetworkASSIGNED PADec 17, 2012abuse@netfactor.net.tr
via TR-NETFACTORTELAS-20110328

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2017
Current origin since
Mar 2017 · 9.7 yr
Origin networks
1