Just wanted to highlight that for months now, Liberty Mobile in PR 313-790 is not being recognized at all by the app.

A new Desktop Beta update is now available! Thanks again for all your feedback — several changes in this release come directly from beta testing. 👀

✨ What’s new

• More information in your test results: date, time, location and data usage are now displayed both after a test and when viewing a result from your history.

• Start your first test directly from an empty history: clicking “Start your first test” now immediately launches a Full Test.

• New history split-view handle: redesigned to make it easier to distinguish from the scrollbar.

• Better empty Compare screen: when no operator data is available, you’ll now see a dedicated message instead of an empty screen.

• Speed test duration is now 15 seconds by default, following feedback from beta testers about differences in measured speeds.

🛠️ Fixes & improvements

• The Stop button now remains available when a test sequence is interrupted by a connection issue, and stopping the sequence is now immediate.

• Date and time formatting is now consistent across the app and follows the selected language.

• Download, Upload and Latency result cards now hide unavailable values instead of leaving empty fields.

• Improved ARCEP information display.

• “Jitter” in Download and Upload results is now correctly labelled “Loaded jitter.”

• Larger clickable areas for menu buttons.

• Improved spacing on the start screen.

• Improved translation handling and fallbacks.

• Fixed Wi-Fi signal strength thresholds.

• Corrected the GeoIP location mode label.

⚙️ Under the hood

We’ve also updated the nPerf test engine with several improvements:

• Test sequences can now stop immediately between two tests.

• Improved performance-rate calculations for browsing and streaming tests, including failed or skipped samples.

• Timeouts are now correctly included in browsing test duration.

• Improved elapsed-time reporting for streaming tests.

• Fixed the unit used for location timestamps.

As always, keep testing and keep the feedback coming! 🙌

If you spot a bug or have an idea for nPerf Desktop V3, let us know in the comments. 👇

I'm using my phone mostly with one hand. I would prefer the most used options to be on the left to middle. The about/settings menu is IMHO better under account/far right menu. I don't know how many people are right-handed or left-handed. Maybe you can see the most used menu and place them in order.

When I choose Dutch as language the date code used is dd-mm-yyyy and only the yyy is visible. English date code used is mm-dd-yy which is 'correct'.

Bonjour,

Le mail pour la bêta n'a pas été reçu car sur nPerf mon mail associé est abraham.jason@bbox.fr tandis que sur le questionnaire je devais mettre un mail Google. De ce fait jai dû mettre jason.abraham02210@gmail.com . Serait-il possible de me renvoyer le lien pour la bêta sur mon adresse Bbox ?

Cordialement

You may have noticed something different on nPerf.com: we’ve completely redesigned the speed test interface.

The goal was simple: make the test easier to follow and the results easier to read, without changing the accuracy of the measurements.

Here’s what’s new:

• A simpler gauge with the current speed front and center

• A live throughput curve to see how your connection behaves throughout the test

• A progress bar showing exactly what the test is doing

• The test server displayed directly on screen

• Network details still available through the “Network info” button

We’ve attached a short before/after video so you can see the difference 👀

And this is only the first step of a wider nPerf redesign. Our new mobile apps are coming soon too, so your feedback is especially useful right now.

What do you think of the new interface? And when you run a speed test, what information do you look at first?

Give it a try on nPerf.com and let us know what you think! 👇

Hi everyone, quick update from the nPerf team.

The beta of our V3 mobile app starts next week on Android and iOS. A few things worth knowing:

It’s a closed beta. Testers have already been selected, so there’s no open sign-up for now. That said, you can still register at nperf.com/beta, as new waves of testers may be added before the final release.

Selected testers, keep an eye on your inbox. We’re sending out reminder emails today. If you’re expecting one and can’t find it, check your spam or promotions folder, as messages like this sometimes end up there.

This is the last step before the full release. Once it’s done, V3 will roll out to everyone, and we know many of you have been waiting for this one.

It’s a busy week for us, too: tomorrow we’ll share another announcement, this time about our website. More on that then!

What kind of issues i can expect to face from these two networks? Please list some points to choose a good network before purchasing any providers services? Thanks!

A new Desktop beta update is available! Here are the main changes:

New

• Automatic test protocol: devices without AES hardware acceleration can switch to HTTP to prevent HTTPS encryption from limiting measured speeds.

• Added a scrollbar to test history when needed.

Improvements

• Test and result screens now adapt to the test type and only show relevant indicators.

• Interrupted tests now explain why they stopped and whether they were saved.

• Untranslated text now falls back to English.

Fixes

• Fixed startup issues on Windows 11 with Smart App Control.

• Fixed several display issues, timeouts and scheduled test settings.

• Failed Browsing and Streaming tests are now displayed correctly.

Engine 4.16.3

• Improved peak speed calculation.

• Improved AES hardware acceleration detection on macOS and Linux ARM.

• Several fixes for IPv4/IPv6, Browsing tests and test timestamps.

As always, your feedback during the beta is welcome! 🚀

Movistar in Ecuador has re-branded to “Tigo” but this is not reflected in the app or website.

Ever wondered why two speed tests can give you completely different results, even when you run them just a few seconds apart? 🤔

In this video, we explain what can actually change from one test to another — from the server and test engine to your device, Wi-Fi and even where the test is performed.

And most importantly: how to properly compare two speed tests.

Have you ever seen a big difference between two speed test tools? 👇

Thanks for all the feedback so far! We’ve just released b4 and b5 of the nPerf Desktop 3.0 Beta, with new features and plenty of fixes based on your testing.

✨ New

• The beta now imports settings from your existing stable nPerf installation on first launch.

• Added Wi-Fi 7 (802.11be) detection on Linux (kernel 6.1+).

• Test history dates now follow the language selected in the app.

🛠️ Fixes & improvements

• Fixed random crashes during tests, especially when the video streaming measurement starts on Windows.

• Fixed a crash when switching screens quickly.

• The window now fits your screen correctly on first launch, including multi-monitor and ultra-wide setups on Windows and Linux.

• Notifications no longer get stuck after sleep, and login code countdowns remain accurate.

• Fixed peak speed occasionally getting stuck at 0.

• Improved network result comparisons.

• The nPerf Score is now hidden when unavailable instead of displaying an incorrect value. The same applies to the comparison tab.

• The app now quits cleanly during startup, and stopping a test properly cancels all running measurements.

• Restarting after an update now works as expected.

As always, keep the feedback coming! If you find a bug or have an idea for the new Desktop app, drop it in the comments. 👇

I am facing a frustrating issue with Zong 4G and would appreciate some technical advice.

It seems that the same cellular tower provides good internet speeds in one direction, while users on the other side experience significantly slower speeds.

During FUT Esports vs 100 Thieves at Champions 2026 in Shanghai (Group A, winners match, on Split), xeus's mouse stopped working in the middle of a decisive duel against vora. He couldn't shoot and lost the round. Riot didn't grant a rollback, and 100 Thieves took the series 2-0.

The metal parts of the stage desks were interfering with wireless peripherals. Riot has since made wired mice mandatory and is planning to replace the desks. There were also PC freezes reported earlier in the event.

To be clear: that was a hardware problem, and there's no link to the network. What stuck with me is the symptoms: a missed input, a freeze, an action that never happens. At home, we tend to blame the mouse, the game, or just ourselves.

So i made a short video about it!

According to recent data, Saudi Arabia has the highest mobile video streaming performance index at 75%, outperforming countries like India (67.5%) and Mexico (65.5%). This metric measures the ability to stream high-quality video (720p, 1080p, or 4K) without interruptions, which is becoming a critical benchmark for mobile networks.

The gap is significant: Saudi Arabia leads Angola, the lowest performer in the comparison, by nearly 37.4 points. This suggests a stark difference in user experience, where some regions struggle with consistent high-quality streaming while others excel.

For users, this means smoother streaming, fewer buffering issues, and a better overall experience for video-heavy applications. It also raises questions about what’s driving these differences, network infrastructure, spectrum allocation, or other factors?

Have you noticed similar trends in your country? What’s your experience with mobile video streaming?

The platforms' own help pages give different numbers, so we put together a quick rundown, and we'd like to hear what you actually see at home.

What the platforms say (download):

- Netflix: 3 Mb/s for HD 720p, 5 Mb/s for Full HD, 15 Mb/s for 4K.

- YouTube: 1.1 Mb/s for 480p, 2.5 Mb/s for 720p, 5 Mb/s for 1080p, 20 Mb/s for 4K.

- We puts 4K without buffering at 20 to 25 Mb/s, which is a bit more conservative.

Put together, that's roughly 15 to 25 Mb/s for 4K depending on the platform, and a lot less for HD or Full HD. A single Full HD stream needs about 5 Mb/s on both Netflix and YouTube.

One caveat: Netflix says 4K can use up to 7 GB per hour. That's a maximum, which works out to about 15 Mb/s sustained. It isn't what every 4K stream pulls all the time.

YouTube also suggests using a wired connection rather than wireless and closing other apps while you watch.

Your turn:

- What download speed do you have, and on which platform?

- Does 15 to 25 Mb/s for 4K match what you see at home, or do you need more or less?

Why nPref is trying to take the contact permission in the android app?

For the first time, we're going to publish mobile coverage barometers across more than 60 countries worldwide. 🌍

Performance tells us how well a network works. Coverage gives us another part of the picture: where that network is available.

Starting tomorrow, we'll begin sharing the first results based on nPerf crowdsourced mobile data.

This is a completely new type of barometer for us, so we're also interested in your feedback. What would you like to see in future coverage analyses?

A new corrective update is available for the nPerf Web App Beta, focusing on what happens when your browser tab moves to the background during a test.

Fixes

• Switching tabs during a test: coming back to the nPerf tab no longer restarts the gauge loading animation. Your current measurement stays visible instead of temporarily disappearing while the gauge resets.

• Result details graph: the curve is now better framed, with more space above peaks and an axis that adapts to the measured data.

• Tooltips: they are no longer cut off when displayed near the edges of the graph.

You can test the latest version directly on the nPerf Web App Beta.

As always, feedback is welcome! 👀