Pangram verdict · v3.3
We believe that this text is a mix of AI and human-written content.
AI likelihood · overall
MixedArticle text · 1,603 words · 9 segments analyzed
Benchmark: Wi-Fi on the moveLive video on the move over Wi-Fi, and not one packet lateWe carried a laptop through a 30 m lab that no single Wi-Fi access point covers, sending live video the whole minute. On its own, each of the three networks got too slow as the laptop walked away from it. With NanoPing using all three at once, every packet arrived within 100 ms.Try NanoPing freeContact salesNanoPing, all threeIn timeAP A 0%AP B 100%AP C 0%Slowest packet now29 msToo late so farneverAP A aloneToo lateSignal-65 dBmSlowest packet now143 msToo late so far4 times, 2.1 sAP B aloneIn timeSignal-46 dBmSlowest packet now28 msToo late so far3 times, 0.5 sAP C aloneToo lateSignal-72 dBmSlowest packet now1137 msToo late so far3 times, 0.8 s0:46 / 1:00Walking back towards AP BThe whole 60-second walk, replayed. Red marks when a network on its own would have made the video wait more than 100 ms. The lines from the laptop show how much of the video NanoPing was sending over each network. The laptop’s position is read from the signal: it passed AP C at 9 s and 35 s and turned by AP A at 22 s.0times the video had to wait, against 3 to 12 on one network0 of 1,800video frames late or lost, against up to 208 on one network49 msfor 99 of 100 packets to arrive, against up to 941 ms91 msfor the slowest packet, still inside the 100 ms limitThe scorecardOne walk, four ways to carry the videoThe same laptop, the same walk and the same minute. NanoPing used all three networks at once. Each network on its own is worked out from how it handled the packets NanoPing sent over it. Even the best of them, AP B, would have spoiled 8 frames. On every line, lower is better.One walk; a check marks the best on the line. A network on its own counts as too slow in any tenth of a second in which a packet NanoPing sent over it arrived after 100 ms or never, or the laptop had no connection to it. Moments less than half a second apart count as one time. Frames: a frame counts as late or lost on a network if a packet sent over it during that frame was.The whole minuteEach network faded in turn, never all at onceAs the laptop moved, each network got weaker the further it went from its access point, and on its own would have made the video wait. NanoPing moved the video to whichever networks were good at that moment. In none of the 600 tenths of a second were all three too slow at once.AP A, 2.4 GHz ch 9AP B, 5 GHz ch 100AP C, 5 GHz ch 36Over the 100 ms limitSwipe sideways to see the whole minute.Passes AP CTurns at AP APasses AP C againBack at AP BSIGNAL AT THE LAPTOP, DBM-30-50-70-90AP AAP BAP CWHERE NANOPING SENT THE VIDEO, SHARE OF EACH SECOND100%0OVER THE 100 MS LIMIT, ON ITS OWNAP A alone12 times, 5.8 sAP B alone3 times, 0.5 sAP C alone5 times, 8.1 sNanoPingnever0102030405060seconds into the walkTop: each network’s signal at the laptop, averaged over half a second. Middle: the share of each second’s video that NanoPing sent over each network. Bottom: the moments each network on its own would have made the video wait. Hover the chart to read any moment.How long packets tookThe slowest packets decide whether the picture stuttersThe video waits at most 100 ms for each packet. NanoPing's packets all came in well inside that. On its own, each network had slow packets that ran far past it: AP C needed 941 ms to get 99 of 100 packets through.NanoPingevery video packet, end to endhalfhalf of the packets9 ms9 of 109 of 10 packets21 ms99 of 10099 of 100 packets49 ms999 of 1,000999 of 1,000 packets87 msAP A aloneevery packet sent over this networkhalfhalf of the packets9 ms9 of 109 of 10 packets23 ms99 of 10099 of 100 packets177 ms999 of 1,000999 of 1,000 packets543 msAP B aloneevery packet sent over this networkhalfhalf of the packets10 ms9 of 109 of 10 packets22 ms99 of 10099 of 100 packets50 ms999 of 1,000999 of 1,000 packets114 msAP C aloneevery packet sent over this networkhalfhalf of the packets10 ms9 of 109 of 10 packets57 ms99 of 10099 of 100 packets941 ms999 of 1,000999 of 1,000 packets1,137 msEach bar runs from zero to the time within which that share of packets had arrived, red where it passes the limit and with an arrow where it runs off the chart. NanoPing: every video packet, from the sending program to the receiving one. Each network on its own: every packet NanoPing sent over it.Packets in time at 100 msNanoPing100%none too late or lostAP A alone97.89%2.11% too late or lostAP B alone99.87%0.13% too late or lostAP C alone91.48%8.52% too late or lostAll latency figuresNanoPingAP A aloneAP B aloneAP C aloneHalf of the packets within9 ms9 ms10 ms10 ms9 of 10 packets within21 ms23 ms22 ms57 ms99 of 100 packets within49 ms177 ms50 ms941 ms999 of 1,000 packets within87 ms543 ms114 ms1,137 msSlowest packet91 ms580 ms208 ms1,137 msIn time at 100 ms100.00%97.89%99.87%91.48%One-way times.
NanoPing's include the whole path from the sending program to the receiving one; each network's include only its own part, which flatters the networks.How NanoPing did itThree networks, used togetherNormally a laptop sticks to one Wi-Fi network and only moves on once that one gets bad. NanoPing used all three at the same time and leaned on whichever were good.It steered around the weak spotsIn the moments a network on its own would have been too slow, NanoPing was sending it almost none of the video: 2% over AP A, 0% over AP B and 0% over AP C.It made up for losses using the othersOn their own, the three networks lost 108 of the packets sent over them and delivered 2,429 more too late. NanoPing sent 1,251 packets again and 7,943 repair packets over the other networks, so none of it reached the video.There was no switching to wait forEach Wi-Fi adapter stayed connected to its own access point the whole time.
The laptop never had to drop one network and join the next.Packets NanoPing sent over each networkAP A aloneAP B aloneAP C alonePackets sent26,32531,76122,765Arrived after 100 ms554421,833Lost20106Lowest link speed6 Mbit/s8.6 Mbit/s6 Mbit/sVideo, repair and check packets over the 60 seconds.
Lowest link speed: the slowest the laptop's adapter sent at during the minute. At that speed a network carrying the whole 7 Mbit/s would have done worse than the figures here.Test setupHow the test was runOne laptop was both ends of the stream. It sent the video over three Wi-Fi networks at once and got it back over its Ethernet port, through the router all three access points hang off.
It was carried from one end of the 30 m lab to the other and back during the minute of video.Laptop, sendingthree Wi-Fi adapters, NanoPingAP A2.4 GHz ch 9AP B5 GHz ch 100AP C5 GHz ch 36, the routerRouterone local networkEthernetLaptop, receivingits Ethernet portThe videoA live stream at 7 Mbit/s and 30 frames a second for 60 seconds, 43,980 packets in all.
Each packet carries the time it was sent, and both ends run on the same laptop clock, so every packet's travel time is exact.The networksThree access points on three different channels, so they never share airtime: AP A on 2.4 GHz channel 9, AP B on 5 GHz channel 100 and AP C on 5 GHz channel 36. AP C is the router's own radio. The laptop had one Wi-Fi adapter for each.What is measuredWhether each packet arrived within 100 ms of being sent. A frame is late or lost if any of its packets is. For each network on its own, every packet NanoPing sent over it shows what that network did at that moment.Reading these numbers fairlyA floor, not a forecast. NanoPing gave each network only part of the video, and least when it was weak. A network carrying all 7 Mbit/s on its own would have done worse than the figures here.The networks get the benefit of the doubt. Their times are the network's own travel time only, while NanoPing's are measured application to application.One frame is left out.
19 packets of one frame, sent 31 s in, never reached the receiving test program. NanoPing lost nothing during the video, so it had delivered them; they were dropped on the receiving machine.The whole test as a PDFEvery number on this page, with the setup, the lab and how each network on its own was worked out.Read the full report (PDF)Measured 30 September 2026, one 60-second walk.
The results for each network on its own are worked out from the same walk, from how each network handled the packets NanoPing sent over it, and are a lower bound on what one network carrying the whole video would have gone through.
Results reflect the equipment, lab and settings described on this page.Get startedReliable real-time connectivity in just a few stepsEvery signup includes 30 days of full Pro access, no credit card. Spin up NanoPing on your device in just two commands and watch your traffic become reliable and stable right away.Try NanoPing freeContact sales~/nanopingbash$ curl -sS https://get.nanoping.com/latest | shInstalling latest version of np (NanoPing) …✓ finished downloading✓ installed np to /usr/local/bin/np✓ configuration storage defaults to /home/user/nanoping (override with --app-data)Go to https://docs.nanoping.com for documentation.Now run "sudo np up" to start NanoPing as a daemon$ sudo np upYou need to activate this device. Go to the following link to sign in: https://user.nanoping.com/auth/claim?id=…Started. Serving dashboard on http://127.0.0.1:8081↵open dashboard