MiyaIP Short-Term Proxy: Answers to 35 Essential Questions

This guide explains the current MiyaIP Short-Term Proxy rules. Where no contractual guarantee or published SLA exists, the answer says so explicitly.

1. What do I receive with the 60-IP package? You receive 60 Short-Term IP binding units in your account, not 60 IPs generated immediately. Each successful new binding consumes one unit and, subject to inventory and capacity, up to 60 bindings may be active together.

2. Are the IPs generated immediately after payment? No. Payment adds quota to your Short-Term IP balance. You bind selected IPs later in MiyaClient or through an approved generation and binding interface.

3. When does the 24-hour validity period begin? The timer begins when each individual IP is successfully bound. It does not begin at purchase and does not wait for the first proxy connection.

4. Does each IP remain the same for the full 24 hours? The product is designed as a fixed binding for up to 24 hours without automatic rotation during normal use. Exceptional edge-device or upstream-network conditions can still interrupt availability or change the upstream public IP.

5. Is an early offline or unusable IP replaced for free? A failure during initial binding does not consume quota. After a successful binding, self-service Refresh IP consumes another unit and starts a new 24-hour term. Any goodwill replacement for a verified early failure requires support review.

6. What happens after an IP expires? The expired binding is removed and the consumed unit is not returned. Creating another binding consumes another unit; after one successful 24-hour binding from a 60-unit package, 59 unbound units remain.

7. Can all 60 IPs be active simultaneously? The account model does not set a lower active-IP limit than the purchased quota, so 60 successful bindings may be active, subject to live inventory and platform capacity. One binding or generation request is limited to 100 IPs, and no separate contractual connection-concurrency SLA is published.

8. What targeting can I choose? Current inventory can be filtered by country, state or province, ASN, ISP type, online time, unchanged-IP time, and speed-related fields. City, ISP name, and ASN are displayed when available, but exact ZIP-code targeting and cable-or-fiber subtypes are not documented options.

9. Can targeting differ for each IP? Yes. Manually selected IPs can have different country, state, city, ISP, and ASN attributes. Automatic generation uses one country and state condition per request, so use separate requests for different regions.

10. Are location, ISP, and ASN selections guaranteed? Selections use live inventory metadata. Availability is not guaranteed, and third-party geolocation or risk databases may classify an IP differently. There is no contractual guarantee of identical city, ISP, or ASN recognition across every external database.

11. What if the requested location or ISP is unavailable? The inventory list shows available candidates before binding. Automatic generation returns the successful count and a failure list when matches are insufficient. Failed bindings do not consume quota, and the system should not silently substitute another country or state condition.

12. Are all IPs residential? No. Candidates may be classified as residential, cellular, business, or hosting. Select the residential filter when required and verify the displayed classification, while remembering that third-party databases may disagree.

13. Are IPs dedicated during the 24-hour period? MiyaIP prevents the same edge resource from being bound again while it is active, providing allocation exclusivity inside the platform. This does not guarantee that an ISP, NAT environment, upstream provider, or outside party never shares the underlying public IP.

14. Are all purchased IPs unique and from different networks? Active bindings are separate resources, but there is no guarantee that 60 IPs come from 60 different subnets, ISPs, ASNs, cities, or non-consecutive ranges. Diversity depends on the live pool and your filters.

15. Are duplicates prevented in my active list? The system rejects duplicate edge selections in one request and filters already-active resources. Distinct edge devices can still temporarily present the same NAT or public IP in exceptional upstream-network scenarios.

16. What quality or reputation guarantees are provided? Inventory records expose operational data such as RTT, packet loss, online time, unchanged-IP time, and speed fields. No guarantee is published for fraud score, abuse score, blacklist status, prior-use history, or identical third-party classification.

17. Do you pre-check with named reputation databases? The customer-facing workflow does not document mandatory pre-screening by IPQualityScore, Scamalytics, MaxMind, IPinfo, IP2Location, or IP2Proxy. Do not assume every IP has passed all named services.

18. Can a high-risk, blacklisted, proxy-detected, or wrongly located IP be replaced free of charge? There is no automatic free replacement based only on a third-party result. Initial binding failures do not consume quota; a normal refresh consumes another unit. Material metadata errors or immediate failures can be submitted to support with the binding ID, time, target location, and evidence.

19. What is the refund, replacement, or credit policy for problem IPs? Failed initial bindings are returned to the quota balance. A successfully bound IP later reported as offline, misclassified, high-risk, or blacklisted is not automatically refunded or credited and requires support review under the applicable terms.

20. Do the proxies support HTTP/HTTPS and SOCKS5? The product provides host, port, username, and password credentials but does not publish a reliable dual-protocol guarantee. Confirm the current gateway protocol with support before purchase when SOCKS5 or specific HTTP CONNECT behavior is mandatory.

21. Can the protocol be selected per IP? No protocol-selection field exists in the current binding workflow. The gateway service determines the protocol rather than allowing a separate choice for every binding.

22. What authentication methods are available? Each binding receives a gateway host, port, username, and password, so username-and-password authentication is supported. IP-whitelist authentication is not documented for this product.

23. Is bandwidth unlimited? Quota is counted by successful bindings rather than purchased gigabytes, but there is no contractual unlimited-bandwidth, speed, request, or concurrency SLA. Platform capacity, acceptable-use, network, destination, and security controls still apply.

24. What are the average speed, latency, uptime, and success rate? There is no single published guaranteed average or SLA. Candidate records may show RTT, packet loss, online duration, download speed, and upload speed, while actual results depend on the edge device, route, destination, time, and network conditions.

25. Are websites, ports, software, or traffic types restricted? Credentials generally work in compatible software subject to MiyaIP acceptable-use rules, gateway security policy, destination restrictions, and law. Obtain written confirmation for SMTP, P2P, scanning, payment sites, streaming, or other sensitive traffic.

26. Must I install MiyaClient? For the standard workflow, yes. The web console handles purchase and read-only viewing, while MiyaClient browses inventory, selects and binds IPs, and generates credentials. Backend interfaces are not a generally published automation product unless access is approved.

27. Can the proxies be used without keeping MiyaClient open? Yes. After binding, the gateway credentials can be used in compatible browsers, applications, servers, or proxy managers. The binding is maintained server-side, so MiyaClient does not need to remain open.

28. Which operating systems does MiyaClient support? The reviewed materials do not contain an authoritative public OS support matrix. Confirm current Windows, macOS, Linux, and Android downloads with support instead of assuming all platforms are available.

29. Can I use the proxy on a remote server or VPS? Yes. Once bound, gateway credentials are not technically tied to the device running MiyaClient and may be configured on a compatible remote server or VPS, subject to account security and acceptable-use rules.

30. Can the same credentials be used on more than one device? The credential format is not device-bound, but no published multi-device or connection-concurrency guarantee exists. Sharing credentials increases security and capacity risks; confirm high-concurrency use with support.

31. What is CDKEY Generation used for? CDKEY Generation converts existing Short-Term IP quota into redeemable codes. The creator's balance is deducted when codes are generated and the recipient gains quota on redemption. Codes transfer quota rather than bind IPs, with a current minimum of five units per code.

32. Is there an API for automated binding, extraction, checking, and replacement? Authenticated backend endpoints can list inventory, bind up to 100 IPs, generate 1–100 proxies by country and state, list active bindings, and refresh a binding. They require an account JWT and are not a formally supported public API with an SLA unless access and terms are confirmed. No third-party reputation-check API is documented.

33. How long does unused quota remain valid? Unbound units are stored as an account balance and currently have no individual expiry timestamp. Their 24-hour terms do not begin until binding, subject to account terms and future product-policy notices.

34. Is a trial available? The current registration flow grants two Short-Term IP units where that registration benefit is available, providing a small functional trial. Confirm current package availability or additional samples with sales or support.

35. Can you provide a screenshot or video of the complete binding process? The flow is: sign in to MiyaClient, open Short-Term IP, choose country, state, and inventory filters, review candidates, select and bind resources, then copy the generated gateway credentials. Screenshots or videos should come from the current live client because filters and inventory can change.

In short: purchase adds quota; each successful binding consumes one unit; each binding lasts 24 hours from successful binding; initial failures do not consume quota; expiry does not return quota; and self-service refresh consumes another unit.