May 17, 2026 · 8 min read

Why Your iPhone Hotspot Drops to 0.5 Mbps After 15 GB (And Every Way to Actually Fix It in 2026)

If your iPhone hotspot suddenly turned into dial-up speed a few days into the billing cycle, you are not imagining it and your phone is not broken. Your carrier is throttling your hotspot data on purpose, on every "unlimited" plan from Verizon, AT&T, and T-Mobile, after a hidden monthly cap that no one talks about in the ads.

This article explains what is actually happening at the network level, how to confirm you are being throttled in 60 seconds, and every working fix in 2026 — ranked honestly from free to one-click, including the free ones that work and the paid ones that do not.

What is actually happening when your hotspot slows down

Your iPhone has one SIM and one cellular radio, but your carrier sees two different kinds of traffic going through it:

The carrier separates these by inspecting the TTL (time-to-live) field of every IP packet, by checking certain HTTP headers, and on modern networks by passive fingerprinting of TCP/IP stacks. When traffic looks tethered, it gets put into a separate metering bucket. Once you have used your monthly hotspot allowance from that bucket — typically 5 to 60 GB depending on plan — the carrier deprioritizes the bucket to roughly 600 Kbps or 128 Kbps for the rest of the billing cycle.

Your phone keeps running at full speed because on-device traffic is in a different bucket that has not been used up. This is why a speed test on your iPhone reads 200 Mbps while your Mac on the same hotspot crawls along at 0.5 Mbps.

The "unlimited" plan name is technically accurate. Your phone really does get unlimited data. What is limited is hotspot data — and that limit is buried on page seven of the plan details that nobody reads.

The 2026 hotspot caps for the major US carriers

Numbers below are accurate as of May 2026 and apply to postpaid plans on the named carriers' own networks. Prepaid and MVNO subscribers should consult their specific plan.

CarrierPlanFull-speed hotspotAfter cap
VerizonUnlimited Welcome5 GB600 Kbps
VerizonUnlimited Plus30 GB600 Kbps
VerizonUnlimited Ultimate60 GB600 Kbps
AT&TUnlimited Starter5 GB128 Kbps
AT&TUnlimited Extra30 GB128 Kbps
AT&TUnlimited Premium60 GB128 Kbps
T-MobileGo5G15 GB3G (~600 Kbps)
T-MobileGo5G Plus50 GB3G (~600 Kbps)
T-MobileMagenta MAX40 GB3G (~600 Kbps)

If you regularly work from a laptop using your phone's hotspot — digital nomads, RV/van life, anyone in a coverage gap for home internet, anyone whose home ISP is unreliable — 15 to 30 GB lasts about a week of normal work. Then you hit the wall and your "unlimited" plan effectively becomes useless for the next three weeks.

How to confirm you are being throttled in 60 seconds

  1. On your iPhone, open fast.com in Safari. Note the speed (probably 100+ Mbps if you have a decent signal).
  2. Enable Personal Hotspot. Connect your Mac to it (USB or Wi-Fi, doesn't matter).
  3. On your Mac, open fast.com. If the Mac reads less than 5 Mbps while the phone reads 100+ Mbps on the same hotspot, you are being throttled at the tethering bucket — not at the cell tower.

If both the phone and Mac are slow, you are in a congested cell or have poor signal — that is a different problem and no software fix will help. The diagnostic only works when the phone is fast and the Mac is slow.

Every fix that exists, ranked honestly

Fix 1: Switch to a carrier with truly unlimited hotspot

Carriers that do not throttle hotspot at all (as of 2026):

Pros: Real fix at the bill level. No software, no fiddling. Cons: Switching carriers is friction, you may lose a family plan discount or device financing, and coverage can vary even on the "same" underlying network because of priority levels.

This is the highest-leverage fix if you are not locked in. If you are, read on.

Fix 2: The TTL trick (free, works on some carriers, fragile)

The original TTL fingerprint detection used by carriers is bypassed by manually adjusting the IP TTL on your laptop. On macOS:

sudo sysctl -w net.inet.ip.ttl=65

This makes outgoing packets from the Mac look like they originated on the phone (which would have TTL 64 by default; bumping to 65 means the phone decrements to 64 when forwarding, which is what the carrier expects to see for on-device traffic).

Pros: Free. Takes 10 seconds. Works on many carriers — especially older detection systems.

Cons:

Try it first because it is free, but do not be surprised if you still get throttled within a few hours or after the next billing cycle.

Fix 3: PDANet+ (paid, dated, still works for some)

PDANet has been around since the BlackBerry era and still ships. It uses USB tethering plus traffic shaping to disguise hotspot as phone traffic. It works on some carriers but not all — and the user interface and onboarding flow have not been meaningfully updated in over a decade.

Pros: Established product, free trial, works on Android too. Cons: macOS app is from a different era visually; setup is not one-click; effectiveness varies by carrier and seems to degrade as carriers add new detection methods.

Fix 4: iproxy + a manual SOCKS5 server (free, terminal-heavy)

The general principle is sound: if you can get a SOCKS5 proxy running on your iPhone and forward a local port from your Mac through USB to that proxy, all Mac traffic will exit the phone the same way Safari traffic does. The carrier sees only on-device traffic.

The DIY recipe is:

  1. Install libimobiledevice on the Mac (brew install libimobiledevice).
  2. Run a SOCKS5 server on iPhone — there are open-source apps that do this, or you can write one in 200 lines of Swift using the Network framework.
  3. Run iproxy 1082 1082 on the Mac to forward port 1082 over USB.
  4. Set the Mac's system SOCKS proxy to 127.0.0.1:1082 in System Settings → Network → Wi-Fi/Ethernet → Details → Proxies.

Pros: Free. Open standards. You understand and control every layer. Cons: You live in Terminal. The iOS app side has to keep running, which iOS sometimes kills in the background. Re-enabling everything after a reboot is a chore. If you are the kind of person who already wrote a launchd plist or two, you will love this. If not, the daily overhead is real.

Fix 5: A native one-click app for the same approach

This is the gap FastNet fills — same proxy-over-USB architecture as the iproxy recipe, but packaged as two apps you install and forget. The iOS app runs a SOCKS5 proxy in the background. The Mac menu bar app handles the USB tunnel via libimobiledevice and toggles the system proxy on and off with one click.

To the carrier, traffic exits the phone with the same TTL, the same TCP fingerprint, and the same HTTPS SNI distribution as if you opened Safari on the phone and browsed the same sites yourself. There is no TTL trickery to detect because it is not a trick — the traffic literally originates from the phone's network stack.

FastNet — the one-click version of the iproxy recipe

iOS app is free. Mac menu bar app is $29 one-time, 30-day no-questions refund. Works on Verizon, AT&T, T-Mobile, and most MVNOs.

See FastNet on the homepage

Honest disclosure: I built FastNet. If iproxy works for you, save the $29.

Why the proxy approach is the most durable fix

Carriers detect hotspot in three layers:

  1. Layer 1 — TTL fingerprint. Old technique, bypassed by Fix 2 above.
  2. Layer 2 — TCP/IP stack fingerprint. Mac and iPhone produce slightly different TCP window sizes, options ordering, MSS values. Carriers passively compare against a library of known stacks.
  3. Layer 3 — HTTPS SNI and DNS patterns. The mix of domains a phone normally talks to differs from a laptop. iCloud, Apple Push, App Store, Maps versus Slack, GitHub, npm, AWS.

The TTL trick only beats Layer 1. PDANet and similar shapers attempt Layer 2 (with mixed results). The proxy-over-USB approach beats all three at once, because the packets really do come from the phone's network stack — same TTL, same TCP fingerprint, same SNI distribution — because Safari and FastNet on the phone share the same iOS network code.

This is also why the approach is durable over time: you are not playing whack-a-mole with new detection methods. You are routing traffic the way the carrier expects on-device traffic to be routed, because it is on-device traffic, just initiated by an app that happens to forward bytes from your laptop.

Why USB matters (and the speed ceilings)

Wi-Fi hotspot is what most people think of, but it has two problems for this use case:

USB tethering, on the other hand:

For most people on cellular, USB is faster than Wi-Fi hotspot and the speed ceiling is way above what your cellular connection can deliver anyway. You are network-bound, not USB-bound.

FAQ

Does this violate carrier ToS?

Most carrier terms of service forbid using more tethered data than your plan includes. The proxy approach makes tethered traffic look like on-device traffic, so the carrier's automated systems do not flag it. Whether this violates the spirit of the ToS depends on how strictly you read it. We are not lawyers and we are not going to claim "100% undetectable" — your data volume patterns can still be inferred. Use your own judgment.

Will the carrier ban me?

Account suspension for tethering use is rare and typically only happens for extreme cases (hundreds of GB per month, clearly running a home internet replacement). Normal laptop use — a few hours of work per day, 50 to 100 GB per month — has not, to our knowledge, triggered enforcement on any major US carrier.

Why is my hotspot slow even before the cap?

If your hotspot is slow from day one of the billing cycle, you are likely in a congested cell. Hotspot users are deprioritized on most networks below regular phone users, so during peak hours you may get slower speeds even within your hotspot allowance. There is no software fix for cell congestion — the proxy approach makes your Mac traffic look like phone traffic, which is in the higher-priority queue, so it can help here too.

Does this work on iPad or Apple TV?

The proxy approach as implemented in FastNet works on macOS only today. iPad and Apple TV do not have a system SOCKS proxy setting in the same way and need a different approach. If there is demand we may add support — feel free to email and let us know.

Does this work on Windows or Linux?

FastNet is Mac-only today. The same architecture would work on Windows and Linux because libimobiledevice is cross-platform — it is on the roadmap based on demand.

Will Apple stop this from working in a future iOS update?

Possible but unlikely. The SOCKS5 server is a normal iOS app using the public Network framework. USB-over-libimobiledevice has been stable since iOS 7. Apple has no business incentive to break this — it is the carriers, not Apple, who care about tethering caps, and Apple has historically pushed back on carrier-driven iOS restrictions.

The short version

Every major US carrier throttles hotspot after a hidden cap. The cleanest fix is to switch to a carrier that doesn't (Visible, US Mobile). If you can't switch, a SOCKS5 proxy running on the phone with USB forwarding to the Mac is the most durable software fix — because it doesn't try to disguise tethered traffic, it routes traffic through the phone's own network stack so the carrier sees on-device traffic.

The DIY recipe with iproxy is free and works if you don't mind the terminal. FastNet is the same architecture packaged as two one-click apps, for people who'd rather pay $29 than maintain a launchd plist.

Either way, you no longer need to put up with 0.5 Mbps for three weeks out of every month.