Data as of Nov 10, 2026

83.136.56.0/22

1 residential-proxy exit · 30 days

Zain Bahrain B.S.C.

Announcement
No RPKI
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
1
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4 observations

Proxy providers listing exits

  • Byteful

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
83.136.56.0/23
since Feb 2008
AS31452Mobile1Zain Bahrain B.S.C.
83.136.58.0/23
since Feb 2025
AS31452MobileZain Bahrain B.S.C.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.136.56.0/212,048BH-MTC-20040127Zain Bahrain B.S.C. (ORG-MVB1-RIPE) · BHALLOCATED PAJan 27, 2004abuse@bh.zain.com
└ 83.136.56.0/24256BH-MTCZain Bahrain IP AllocationASSIGNED PAApr 19, 2016abuse@bh.zain.com
via BH-MTC-20040127
└ 83.136.57.0 - 83.136.63.2551,792BH-MTCMTC Vodafone Bahrain (B.S.C)ASSIGNED PAJan 3, 2008abuse@bh.zain.com
via BH-MTC-20040127

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 83.136.56.0/21

83.136.56.0/21

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1