LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

217.197.97.0/24

6 residential-proxy exits · 30 days

BitCommand LLC · space held by Deployish Limited

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
28
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

514 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • GSocks
  • Geonode
  • Infatica
  • NextProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • Q2IP
  • RH7Proxy
  • RainProxy
  • ResiProxies
  • Shifter
  • ZENPROXY_PREMIUM

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
217.197.97.0/24256UK-DEPLOYISH-20230515Deployish Limited (ORG-DL479-RIPE) · GBALLOCATED PANov 14, 2025report@deployish.com
└ 217.197.97.0/25128BitCommandunknownASSIGNED PAMay 18, 2023report@deployish.com
via UK-DEPLOYISH-20230515
└ 217.197.97.128/25128BitCommandunknownASSIGNED PAMay 18, 2023report@deployish.com
via UK-DEPLOYISH-20230515

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
May 2023
Current origin since
Sep 2024 · 2.2 yr
Origin networks
2
Last change of origin
Sep 2024
Recorded history

History

Handoffs
1