What an IP address explains, and what only the platform knows.

What IP-side evidence can I include in a support request?

Provide the checked address, time, named findings and coverage gaps alongside your own error message. This supports investigation without asserting that the address caused the challenge; account, browser and destination-private signals are outside this record.

Source availability depends on the current deployment and each returned record. These review dates do not establish when a particular IP was observed. Method axis-scope-2026-09-15 · Score ipjury-score-v3.

Unusual activity detected. Verify you are human. This content is not available in your region. Your account has been restricted. Four different messages, and the question underneath all of them is the same: is it my IP, or is it me?

What is observable about an address

Six things can be established from public and licensed evidence, and IPJury reports them separately rather than blending them:

• Network role. Residential, mobile, business, hosting, public infrastructure. The role does not identify what caused a particular challenge.
• Anonymity evidence. Covered proxy, Tor and privacy-relay findings, with unsupported VPN and residential-proxy fields explicitly withheld.
• Abuse evidence. Whether a record exists against this exact address, against its prefix, or not at all in the sources that answered.
• Geolocation context. Named location estimates and any registration-country difference, not a measured explanation of region-related friction.
• Routing. The source-reported origin and range. RPKI validity is withheld under the active source permissions.
• Coverage. Which jurors answered, which abstained, and how fresh the evidence is.

What no IP tool can see

These are examples of other inputs a service may consider. This lookup does not measure their relative importance or attribute a particular decision to one:

• Account age and history. A week-old account and a six-year-old account with the same IP get treated differently, and should be.
• Device and client integrity. Browser fingerprint, automation markers, emulator traits, app attestation.
• Behavior. Request rate, navigation shape, timing, and how closely a session resembles previous ones from that account.
• Payment history. Chargebacks, card country, prior disputes, billing-address consistency.
• Session continuity. Cookies, stored tokens, and whether this login looks like a continuation or a fresh unknown.
• Private reputation data. Internal signals the service never publishes, plus commercial feeds it does not name.
• Policy. Licensing territory, sanctions, age gating, and product rules that are decisions rather than detections.

How the friction differs by service family

Use these as questions to investigate, not measured brand behavior or a claim about unpublished weights.

AI and model services

Ask whether the reported error concerns quota, account policy or network traffic. A hosting label alone does not distinguish these explanations.

Video and audio streaming

A region message makes location estimates relevant context, but the tool cannot inspect the service’s territorial rights or account settings.

Payments and fintech

Keep IP evidence separate from instrument, transaction and account facts that this tool does not have. Do not use the IPJury index as a payment decision.

Social platforms and communities

A support request can include IP-side evidence, but the tool cannot see private moderation, account or device records.

What an evidence record is legitimately for

Nothing here obliges any service to do anything, and IPJury has no visibility into any service's decision. IPJury does not claim that a platform uses this index or identify which outside data it consumes. What the record does do:

• Documents address-side findings. A named finding can support investigation. A quiet record cannot exclude the IP as a factor or prove that another cause is more likely.
• Documents a support contact. Named sources, stated bases, and a timestamp are a better attachment to a ticket than a screenshot of a number.
• Separates what you can change from what you cannot. Different kinds of issues call for different evidence; this record cannot diagnose an account problem from a network label.