Development & Automation

Even the Movers Gave Up on This Wi-Fi. Claude Code Made It 112x More Responsive.

A Japanese AI startup CEO used Claude Code to diagnose his home Wi-Fi and improved responsiveness 112x. Here's the hands-on account and the measured numbers.

· Huuush

Even the Movers Gave Up on This Wi-Fi. Claude Code Made It 112x More Responsive

Key takeaways

  1. 1Using a SoftBank fiber line with PPPoE for over a year was the cause of the bottleneck.
  2. 2Claude Code did five steps, from writing a diagnostic script to pinpointing the cause and guiding the setup.
  3. 3After adding a Hikari BB unit and switching to IPv6 IPoE, responsiveness under load improved about 112x.
Before-and-after diagram of a home internet line setup changing from PPPoE to IPv6 IPoE

The CEO of a Japanese AI startup fixed his home Wi-Fi with Claude Code.
Responsiveness got up to 112x faster.

This was a connection that a mover's technician had told him "this is the best speed you'll get, no matter what you do."

PPPoE Held It at 184 Mbps

This is a hands-on account that Masahiro Chaen, CEO of Japanese AI company Digirise, posted on X at 12:03 PM (KST) on August 18, 2026.
Digirise helps businesses adopt and train on AI, and Chaen also advises several companies, including GMO AI & Web3.

The line was contracted at 1 gigabit (Gbps) but was actually stuck at 184 Mbps.
The cause was that he had used a SoftBank fiber line for over a year with the old PPPoE method.

What Claude Code Did

Chaen gave Claude Code five steps.

StepWhat happened
1Wrote a diagnostic script that measures Wi-Fi signal, IPv6, routing, DNS, and bufferbloat in one go
2Pinpointed the cause with traceroute: the Hikari BB unit was missing from the path
3Ruled out ineffective fixes such as changing channels
4Looked at a photo of the device and diagrammed how to connect the ports
5Re-measured with the same script after the change

The fix was to add a Hikari BB unit (513 yen a month) and switch to IPv6 IPoE.
The existing router had its routing function turned off and was left to broadcast the signal only (AP mode).

Measured Numbers

He compared before and after with the same diagnostic script.

MetricBeforeAfterChange
Responsiveness under load (RPM)11.01231.0about 112x
Download under load6.5 Mbps335.9 Mbpsabout 52x
Idle latency36.5 ms10.1 msabout 3.6x better
IPv6NoneYes-

Chaen explains that the real cause of the slowness wasn't the speed itself but bufferbloat.
When the line is congested, packets pile up in device buffers and latency grows.
It doesn't show up on a speed test, but in daily use it felt constantly clogged.

On a Mac, Start With networkQuality

If your own internet feels slow, the same approach is worth trying.
Chaen also published the diagnostic prompt in a follow-up post.
But the prompt assumes macOS's networkQuality command, so it can be used as is only on a Mac.
Original: post sharing the prompt

112x Is One Household's Measurement

This figure is a result Chaen measured on his own line, not material officially verified by SoftBank or a third party.
Results can vary with your line setup (whether you use PPPoE, how the Hikari BB unit works on a SoftBank fiber line).

Frequently asked questions

How do you diagnose home Wi-Fi with Claude Code?
You have Claude Code write a diagnostic script that measures Wi-Fi signal, IPv6 connectivity, routing (traceroute), DNS, throughput, and bufferbloat in one go, then pinpoint the cause from the results.
Why did responsiveness get 112x faster?
The problem was bufferbloat (accumulating packet delay) from the PPPoE method, not the line speed itself. Switching to IPv6 IPoE bypassed the bottleneck and cut latency sharply.
Can you use this method on any internet connection?
Not officially confirmed. This case is one person's measurement on a SoftBank fiber line and macOS, and conditions and results can differ by carrier and environment.
What do you need to switch to IPv6 IPoE?
In this case, he added a Hikari BB unit (513 yen a month) and switched the existing router to AP (signal-broadcast-only) mode.

Related articles