Blog · How-to

How to copy your IP for support tickets

Quick steps:

  1. Open What Is My IP Address IP.
  2. Wait for your IPv4 (and IPv6 if your network shows one).
  3. Click Copy, then paste into your ticket or email.

Tips

If support asks for IP “right now,” avoid VPN unless they want the VPN exit IP. After network changes, click Refresh before copying. More detail: check IP in browser.

Include protocol and context

Paste both IPv4 and IPv6 if shown, or label which one the ticket needs. Say whether you were on Wi‑Fi or mobile data and whether a VPN was connected—otherwise engineers reproduce the wrong path.

Sanitize before public posts

Pasting into a private ticket is normal; posting IPs on open forums reveals coarse location metadata. Read is it safe to share my IP address? for a proportionate view.

People also ask

Should I copy IPv4 or IPv6? If the ticket does not specify, include both lines and label them. Some backends only ingest dotted-decimal IPv4; others are dual-stack aware.

My clipboard pasted the wrong thing—why? You might have copied from Wi‑Fi settings (private IP) instead of our checker. Always copy from the big IPv4 line on the homepage, then verify it is not 192.168.x.x or 10.x.x.x unless support asked for LAN details.

Do I need a screenshot? Usually text is better: searchable, accessible, and smaller. Add a screenshot only if they explicitly want proof of the UI state.

Corporate proxy users: mention that you are on a corporate network; the IP may be an office egress, not your home ISP. That changes how they reproduce firewall issues.

Gamers: if matchmaking asks for IP after a disconnect, grab a fresh copy after you re-queue—some sessions bind to the address at login time.

International travelers: roaming can change carrier IPs often; note timezone and whether you used hotel Wi‑Fi vs LTE when the issue occurred.

Extended guide: ticket quality

Great tickets include: the exact IP text, time window, VPN on/off, network type, and what you already tried. That reduces back-and-forth and gets you to resolution faster than a single line saying “it broke.”

If engineers ask for a traceroute or MTR later, that is complementary to IP text—not a replacement for knowing your public address at a point in time.

Redact unrelated PII, but do not redact the IP if they asked for it—that defeats the purpose.

Follow up after network changes: paste a new reading instead of referencing yesterday’s IP if the issue is intermittent.

Formatting tips that reduce confusion

Paste IPv4 and IPv6 on separate lines with labels. If only one family appears, write “IPv6: not shown by checker” so engineers do not assume you forgot it.

Avoid smart quotes or locale-specific separators when copying into ticketing systems—some parsers strip non-ASCII characters oddly.

When threads get long, reply with a fresh copy of the current IP rather than saying “same as before” if more than a day passed—DHCP might have rotated overnight.

For mobile tickets, mention airplane mode toggles or SIM swaps explicitly; those actions change carrier assignments faster than home broadband.

After you send: what to expect

Good teams acknowledge receipt and map your IP against their logs within a predictable window. If they ask for another reading later, they are not doubting you—correlation often needs multiple timestamps, especially during intermittent failures.

If someone requests a traceroute or MTR, that complements your IP snapshot; run it from the same machine and network path you used when copying the address. Mixing Wi‑Fi diagnostics with a cellular IP in the ticket confuses everyone.

Escalations sometimes move between tiers; re-paste the IP block when the thread changes owners so the new engineer does not hunt through scrollback.

When issues close, save the final IP your ticket referenced—useful if the problem returns weeks later and you need to compare whether your assignment strategy changed.

Frustration is normal when round three still asks “what is your IP?”—calmly paste again with the date. Automated systems do not always surface earlier messages to every human reader.

Finally, thank people who explain what they found: it helps you learn whether the next outage looks similar or entirely new.

Copy, label, send

Three verbs cover ninety percent of successful tickets: grab the exact text from our checker, label IPv4 vs IPv6, send it through the channel the vendor asked for. Fancy diagnostics can wait until someone requests them.

Summary checklist

Open checker → wait for load → refresh if you changed networks → click Copy → paste into ticket → add context lines about VPN and link type → send.

Related guides