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

109.232.248.0/21

1 residential-proxy exit · 30 days

Mitigator Cloud LLC

Announcement
this exact prefix
No RPKI
Announced by
AS51464
Type
Business

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
1
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

8 observations

Proxy providers listing exits

  • NovaProxy

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
109.232.248.0/22
since Nov 2023
AS43048BusinessMitigator Cloud LLC
109.232.248.0/24
since Jul 2022
AS43048BusinessMitigator Cloud LLC
109.232.249.0/24
since Jul 2022
AS43048BusinessMitigator Cloud LLC
109.232.250.0/24
since Jul 2022
AS43048BusinessMitigator Cloud LLC
109.232.251.0/24
since Jul 2022
AS43048BusinessMitigator Cloud LLC
109.232.252.0/24
since Sep 2010
AS51464BusinessMitigator Cloud LLC
109.232.253.0/24
since Jan 2017
AS51464BusinessMitigator Cloud LLC
via IBANK2.RU, Ltd.
109.232.254.0/24
since Jan 2017
AS51464BusinessMitigator Cloud LLC
109.232.255.0/24
since Jan 2017
AS51464Business1Mitigator Cloud 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
109.232.248.0/212,048RU-IBANK2RU-20091211Mitigator Cloud LLC (ORG-IL186-RIPE) · RUALLOCATED PADec 11, 2009abuse@mitigator.cloud
└ 109.232.248.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PAFeb 18, 2010abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.249.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PAFeb 18, 2010abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.250.0/24256IBANK2RU-SSLIBANK2.RU, Ltd.ASSIGNED PAOct 8, 2012abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.251.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PAOct 8, 2012abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.252.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PAApr 7, 2010abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.253.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.LIR-PARTITIONED PAFeb 22, 2017abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.254.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PASep 17, 2012abuse@mitigator.cloud
via RU-IBANK2RU-20091211
└ 109.232.255.0/24256IBANK2RU-NETWORKIBANK2.RU, Ltd.ASSIGNED PASep 17, 2012abuse@mitigator.cloud
via RU-IBANK2RU-20091211

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
Stable
First seen
Dec 2009
Current origin since
Jan 2018 · 8.9 yr
Origin networks
4
Last change of origin
Jan 2018
Recorded history

History

Handoffs
4