Residential Proxy
Real residential IPs. Choose rotation or a sticky session in the dashboard.
- Rotation or sticky session
- Country, state and city
- HTTP and SOCKS5
- GB never expires

Global proxy infrastructure
from US$0.89/GB
90M+ IPs. 180+ countries. Pay as you go, no subscription. Card, crypto and 24/7 human support from Brazil.
90M+ IPs
180+ countries
99.98% uptime
Four products, priced per GB, paid by card or crypto. The bigger the package, the lower the price per GB.
Real residential IPs. Choose rotation or a sticky session in the dashboard.
A new Brazilian IP on every request, fast, for CPA and data collection.
Real 4G/5G carrier IPs with high trust on apps and social media.
A dedicated IP that is only yours, the same from start to finish, for ad accounts.
Find the right proxy for your next project.
Check campaigns and landing pages across markets.
View solutionCollect public data with flexible IP rotation.
View solutionReview SERPs, redirects and page availability from the markets you serve.
View solutionTrack prices and availability across regions.
View solutionTest applications and content from different locations.
View solutionCreate an account or choose a product and buy a data package. Your access is delivered after payment confirmation.
No. Pay as you go for the data you buy, with no monthly subscription.
No. Your purchased GB never expires.
Pay in USD by card or cryptocurrency.
No. Both use the same residential pool and per-GB pricing. Rotation changes the IP between requests; a sticky session keeps the same IP during a sequence of actions, subject to availability. A sticky session is not a permanently assigned IP.
Residential IPs come from residential internet connections, mobile IPs from carrier networks, and Rotativa CPA IPs from servers. Choose by the connection your task needs. Rotativa CPA plans are available in your account; dedicated residential IPv4 has its own pricing.
RH7 Proxys is based in Brazil, with 24/7 human support and coverage in more than 180 countries.
Use proxies in accordance with our acceptable-use policy.
Buying a proxy starts with a practical question: what must your team observe, and under which conditions? A proxy forwards a client's connection through an intermediary, giving the destination a different connection context from the client's direct route. That can be useful for authorised regional research, owned application testing and other permitted workflows. It does not replace a browser, a dataset or permission to access a service. RH7 buyers should select a product by the work it needs to support rather than by a broad promise about what proxies can achieve. Start with the destination, required market and evidence you expect to obtain.
Residential and mobile are different connection categories, not an automatic ranking from basic to premium. Residential access may be relevant when examining regional web presentation. Mobile deserves consideration when a cellular network context is part of the test itself. Neither label promises that a website will accept a connection or display particular content. For a useful comparison, hold the client, destination and observation method constant. Change the connection category only when it helps answer the question. This makes the evaluation easier to interpret and prevents an unnecessary product upgrade from becoming a substitute for diagnosing the actual source of a problem.
Independent observations and connected journeys need different session planning. A rotating workflow may suit separate page checks, while a sequence that depends on continuity can call for sticky configuration. The RH7 static residential product is residential access in sticky mode. It is not a guarantee of a permanently assigned ISP address. Keep that distinction in the procurement brief, especially if an application expects a long lived connection identity. Ask what the available session controls mean for your client, then test the full journey. Browser cookies, authentication state and application preferences remain separate responsibilities even when a proxy session seeks connection affinity.
A country selector is a requested input, not conclusive evidence about how a destination will classify the connection. Decide whether the project needs a national view or a more precise regional condition, and confirm currently available options before purchase. Record the requested market alongside the page's observed currency, language and market selection. For a Brazilian research project, for example, a saved delivery preference could influence the result as much as the connection location. Do not assume comprehensive city coverage or carrier availability. A smaller set of well documented observations is more valuable than a large set whose geographic meaning cannot be explained.
Prepare a short pilot with representative tasks and an explicit definition of a usable result. A completed connection can still return an unexpected page, an incomplete record or a different market. Track accepted observations, failures and traffic consumed, with enough redacted evidence for another team member to review. Include normal rendering resources if the intended workflow uses a browser. If a destination refuses access, stop and consider an approved API or permission process instead of treating more rotation as the answer. The pilot should establish whether the selected configuration contributes useful evidence within the boundaries of the destination's rules.
Check that your chosen application supports the connection configuration and authentication details supplied for the product. Keep credentials in an appropriate secret store, not in source code, screenshots or shared research sheets. Assign someone to own retry limits, error classification and credential changes. Separate connection failures from content validation failures so that support requests contain a reproducible problem rather than an unexplained statement that a site did not work. A concise diagnostic record can include the time, client version and redacted error. Operational discipline matters because even a suitable connection category can produce unreliable research when session handling and evidence collection are inconsistent.
Use the current product and checkout display for actual amounts; this guide does not substitute for a live quote. English international pricing is displayed in USD, and the configured 3.5% payment fee is already included in the displayed total. Do not add that percentage again when preparing a purchase request. US and UK teams should also distinguish the merchant's USD amount from any conversion or charges their own payment provider may apply. Build a budget around measured traffic per accepted task rather than raw request volume. Compare the operational effort needed to produce useful results, not merely the apparent cost of sending traffic.
Proxy access must be used lawfully and consistently with destination rules. It does not authorise bypassing authentication, security controls or restrictions. RH7 does not guarantee compatibility with third party services. Review the existing Terms before ordering: the seven day withdrawal provision requires consumption below 100 MB and no prior refund on the same account, with support review and stated exclusions. Third party blocking or incompatibility is not a general refund entitlement. Once the pilot has established fit, document the product choice, observed limits and stop conditions. That creates a purchasing decision colleagues can understand and a workflow that can be reviewed before further spending.
Before handing the service to an analyst or engineer, save a short operating brief containing the selected product, permitted destinations, evidence standard and spending owner. Include unresolved questions rather than turning assumptions into requirements that appear already verified. This makes later reviews faster and gives new colleagues a clear explanation of why the configuration was selected.
Start with the required connection context and session behaviour. Compare residential, mobile and sticky residential against the same authorised task rather than assuming one category is universally better.
No. Your client, test design, collection permissions and validation process remain separate. A proxy contributes a connection path; it does not automatically supply a complete research workflow.
No. Third party rules and technical controls remain outside the proxy service. Validate the permitted workflow and review the existing compatibility and refund terms before committing to a larger purchase.