Data as of Nov 22, 2026

205.220.208.0/21

36 residential-proxy exits · 30 days

Fatbeam, LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
98% of it

Residential-proxy exits

Proxy exits
36
1.8% of its addresses · 30 days
Always-on exits
4
11% of its exits
Spread
5 of 8
/24s with at least one exit
Providers
66
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

40K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
205.220.208.0/24
since Mar 2020
AS23263Residential14
2 always on
Fatbeam, LLC
205.220.209.0/24
since Nov 2019
AS55039ResidentialFatbeam, LLC
205.220.210.0/24
since Dec 2020
AS55039ResidentialFatbeam, LLC
205.220.211.0/24
since Mar 2026
AS55039ResidentialFatbeam, LLC
205.220.212.0/23
since Apr 2026
AS55039Residential15
1 always on
Fatbeam, LLC
205.220.215.0/24
since Aug 2025
AS399676Residential6
1 always on
Fatbeam, LLC

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
205.220.208.0/212,048FL-379Fatbeam, LLC (FL-379) · USDirect AllocationAug 3, 2018abuse@fatbeam.com
└ 205.220.211.0/24256FB-LMFQDLLC-205-220-211-0Lmfqd, LLC (C11192653) · USReassignedMay 2, 2025abuse@fatbeam.com
via FL-379
└ 205.220.212.0/2732FB-HMS-OR-205-220-212-0unknown———
└ 205.220.212.32/298FB-H4Y-OR-205-220-212-32unknown———
└ 205.220.212.40/298FB-SILIPINT-OR-205-220-212-40unknown———
└ 205.220.212.48/304FB-STCHARLES-HEALTH-OR-205-220-212-48unknown———
└ 205.220.212.52/304FB-5TALENT-OR-205-220-212-52unknown———
└ 205.220.212.56/298FB-IOU-INV-OR-205-220-212-56unknown———
└ 205.220.212.64/2816FB-MANZAMA-OR-205-220-212-64unknown———
└ 205.220.214.0/2732FB-ENCODER-ID-205-220-214-0unknown———
└ 205.220.214.32/2732FB-REDAL-LAW-01unknown———
└ 205.220.214.64/298FB-H2O-ID-205-220-214-64unknown———
└ 205.220.214.72/298FB-MAMMOTH-205-220-214-72unknown———
└ 205.220.214.80/298FB-GVH-ID-205-220-214-80unknown———
└ 205.220.214.88/298FB-RBORTHO-ID-205-220-214-88unknown———
└ 205.220.214.96/298FB-UNICEP-ID-205-220-214-96unknown———
└ 205.220.214.104/304FB-FWFAB-WA-205-220-214-104unknown———
└ 205.220.214.108/304FB-RAMADA-ID-205-220-214-108unknown———
└ 205.220.214.112/298FB-TAYLOR-ID-205-220-214-112unknown———
└ 205.220.214.120/304FB-JRINVEST-205-220-214-120unknown———
└ 205.220.214.136/298FB-EARNEST-PROP-ID-205-220-214-136unknown———
└ 205.220.214.144/298FB-ASMP-ID-205-220-214-144unknown———
└ 205.220.214.152/298FB-CCS-ID-205-220-214-152unknown———
└ 205.220.214.160/2816FB-LOG-INN-ID-205-220-214-160unknown———
└ 205.220.214.176/2816FB-CABINETS-NW-ID-205-220-214-176unknown———
└ 205.220.214.192/298FB-PROX-ID-205-220-214-192unknown———
└ 205.220.214.200/298FB-NSBB-ID-205-220-214-200unknown———
└ 205.220.214.208/298FB-BODEN-ARCH-ID-205-220-214-208unknown———
└ 205.220.214.216/298FB-STEVE-M-ID-205-220-214-216unknown———
└ 205.220.214.232/298FB-WARREN-HOT-ID-205-220-214-232unknown———
└ 205.220.215.0/24256FATBEAM-KANIKSU-01Kaniksu, LLC (KANIK-1) · USReassignedNov 26, 2018support@kaniksu.com

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

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential2,01698%8
Business321.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2023
Current origin since
Mar 2023 · 3.7 yr
Origin networks
1