A+ Bufferbloat but Still Lagging? What to Test Next

Your bufferbloat test shows A+. Your game still rubber-bands, your ping spikes, or your voice chat breaks up. Does that mean the test is wrong?

Not necessarily. A bufferbloat grade answers a specific question: How much extra delay did this test measure while your connection was busy? It is not a complete assessment of your game, device, Wi-Fi or route to the game server.

The next step is not to chase a better letter grade. It is to find out what kind of lag remains and test that problem directly.

Quick answer: why can you still lag with an A+ score?

You can have an A+ bufferbloat score and still experience gaming lag because:

• Your baseline latency to the game server is high.
• The test server and game server use different network paths.
• Packet loss or intermittent jitter occurs outside the test window.
• Your Wi-Fi connection behaves differently where you play.
• The test did not fully load the bottleneck you wanted to assess.
• The game is suffering from low frame rates, frame-time spikes or device problems rather than network delay.

An A+ result is useful evidence about the test you ran. It is not a guarantee of lag-free gaming.

What an A+ bufferbloat grade actually means

Bufferbloat is excessive queueing delay that develops when traffic builds up at a bottleneck. A bufferbloat test compares latency while the connection is idle with latency during downloads and uploads.

Waveform, for example, assigns A+ when the measured increase is less than 5 milliseconds. That is its grading threshold—not a universal standard shared by every test. Check the methodology of the tool you use.

The distinction between added latency and absolute latency matters:

Both examples have the same increase under load. Connection B still has a much higher baseline delay. These are illustrative numbers, not VelocityVerify measurements, and neither example establishes latency to a particular game server.

A good grade also does not necessarily summarize every short spike. Test duration, sampling, aggregation, transport and server destination affect what the result captures.

First, identify what “lag” means

Different symptoms need different tests. Start with the symptom you can observe rather than changing router settings at random.

Symptoms are clues, not proof. Rubber-banding can have more than one cause, and several problems can occur together.

Test 1: compare the test server with your game server

A network test measures a connection to its own destination. Your multiplayer game may connect to a different region, provider or route.

Open the game’s network-statistics display if one is available. Record:

• The selected server region.
• Typical ping while playing.
• Any spikes during the problem.
• Packet-loss or network-warning indicators.

Check whether the game selected a distant region. If you can choose a closer region, compare several sessions before drawing a conclusion.

A nearby speed-test server can respond quickly while a distant game server responds slowly. Conversely, your test may use a distant endpoint even though your game connects nearby. Neither measurement is a substitute for the other.

If only one game or region performs badly, check the game’s service-status page and compare another region where practical. A regional routing or server problem is possible, but one test cannot prove your ISP is responsible.

Test 2: separate network delay from low FPS

Enable both the game’s network overlay and its frame-rate or frame-time display.

If the game stutters while ping and packet-loss readings remain stable, look at device performance. Possible contributors include background applications, thermal throttling, graphics settings, storage activity and shader compilation.

If ping spikes or packet-loss warnings coincide with rubber-banding, investigate the network path instead.

Do not treat this as a perfect separation. Some games report network statistics imperfectly, and a busy computer can affect both rendering and network processing. The goal is to choose the next test, not declare the cause from one overlay.

Test 3: compare Wi-Fi with Ethernet

Where possible, connect the same gaming device by Ethernet to the main router. Avoid a mesh satellite, wireless extender or powerline adapter for this comparison because those introduce additional links.

Use the same game region and test during the period when the problem normally occurs. Compare more than one session.

• Ethernet repeatedly improves the problem: investigate the wireless path, including signal quality, interference, access-point placement and mesh backhaul.
• Ethernet does not improve the problem: keep the router, device, access connection and game-server path in scope.

Ethernet removes the Wi-Fi link from this comparison. It does not isolate the ISP or rule out a router fault.

If you cannot use Ethernet, compare the same device close to the main access point and at your usual gaming location. Keep other conditions as similar as possible.

For a broader isolation sequence, see Is It Your Wi-Fi, Router, or ISP? A 15-Minute Diagnostic.

Test 4: check for intermittent packet loss and jitter

A short test can look healthy between episodes of a recurring problem. Run observations while the issue is happening.

Use the game’s own network statistics first. If your operating system supports it, you can also compare repeated pings to:

1. Your router’s local gateway address.
2. An external destination that normally responds to ping.

On Windows, open Command Prompt and replace YOUR_GATEWAY_IP with your actual gateway address:

ping -t YOUR_GATEWAY_IP

Open a second window for an external comparison:

ping -t 1.1.1.1

Press Ctrl+C to stop each test and view its summary. On macOS and Linux, ping generally runs continuously without the -t option; check your system’s help for exact behavior.

Interpret the results cautiously:

• Problems reaching the gateway keep the local device or network in scope.
• A stable gateway with external spikes keeps the upstream connection or destination path in scope.
• One external destination behaving badly is not proof that every internet service is affected.

ICMP ping is not the same traffic as your game. Some devices deprioritize or rate-limit ping replies. Apparent loss at an intermediate traceroute hop does not, by itself, establish loss affecting traffic that reaches the final destination.

A browser-based HTTP latency test, an ICMP ping and a game’s reported latency can produce different numbers. Compare each measurement consistently rather than treating them as interchangeable.

For definitions and interpretation, see What Is Jitter? Ping vs Jitter Explained.

Test 5: confirm that the bufferbloat test loaded the intended bottleneck

A clean grade is less informative if the test never generated enough traffic to stress the link you wanted to assess.

For example, a limited test device or slower wireless link may prevent a test from exercising the full capacity of a faster internet connection. That does not automatically invalidate the result; it changes what the result can tell you.

For a controlled comparison:

1. Use the same capable device for each run.
2. Prefer Ethernet when assessing the access connection.
3. Pause unrelated transfers for the initial baseline.
4. Record download and upload throughput as well as idle and loaded latency.
5. Repeat the test rather than relying on one run.
6. Record whether a VPN, QoS or SQM was enabled.

If the reported throughput is unexpectedly low, investigate that limitation before concluding the whole connection has negligible queueing under load.

Do not compare letter grades across different tools as though their thresholds and measurement methods were identical.

See How to Check Your Internet Speed and Best Internet Speed Tests Compared for related testing topics.

Test 6: reproduce the activity that triggers lag

If your game only lags when someone uploads a video, joins a call or downloads an update, test that particular situation.

Start with a quiet-network session. Then introduce one ordinary activity at a time while watching the game’s network statistics. Avoid running uncontrolled heavy transfers throughout the household at once.

Record whether the problem appears during:

• Uploads.
• Downloads.
• Both directions.
• Ordinary gaming with no deliberate background load.

If delay rises primarily under load, revisit queue management and its configuration. If the problem occurs on a quiet network too, do not assume more aggressive shaping will solve it.

On variable-capacity connections such as mobile broadband, conditions may change between the test and the gaming session. Record the time and repeat comparisons during the usual problem period.

If you already enabled SQM or QoS

SQM can reduce queueing delay when configured appropriately and supported by the router’s processing capacity. It cannot remove geographic distance, fix every radio interruption or repair a game server.

Check:

• Whether the settings apply to the correct interface and traffic direction.
• Whether the configured bandwidth matches repeatable measurements rather than the advertised maximum.
• Whether your router can process the traffic at the selected rate.
• Whether the change improved loaded latency, reduced throughput, or both.

Change one setting at a time and keep a record of the previous value. Avoid stacking multiple traffic-shaping systems without understanding which one controls the bottleneck.

For the setup topic, see How to Fix Bufferbloat. Treat queue management as a measured intervention, not a promise of a permanent A+ grade or zero gaming lag.

Keep a short evidence log

A useful troubleshooting log connects the symptom with the conditions in which it happened.

Keep separate notes for bufferbloat-test results: tool, endpoint if shown, idle latency, loaded latency, throughput and grade.

Repeated observations help you decide whether to investigate the local network, the device, the provider path or the game service. They do not automatically prove who is at fault.

Frequently asked questions

Does an A+ bufferbloat score mean my internet is perfect?

No. It means the test measured a small increase in latency under its grading rules. Your baseline latency, destination route, packet delivery, Wi-Fi and device performance still matter.

Can I have high ping with an A+ bufferbloat score?

Yes. A test can measure little additional delay under load while the baseline delay is already high. Check absolute latency and the game’s own ping, not just the letter grade.

Can packet loss happen with an A+ score?

Yes. A bufferbloat grade is not a universal packet-loss certification. Depending on the tool, loss may be measured separately or not measured at all, and intermittent problems can occur outside the test window.

Should I buy a new router if I still lag?

Not before diagnosing the symptom. A router upgrade will not fix a distant game server, low FPS or every provider-path problem. Compare Ethernet, game-region behavior and performance under load first.

Will lowering my SQM speed limit fix the remaining lag?

Only if the remaining problem is related to queueing that the shaper can control. Lowering the limit unnecessarily can sacrifice throughput without improving the cause of the lag.

Why does my game report different ping from a network test?

The destinations, network routes, traffic protocols and measurement methods can differ. Use the game’s readings to investigate its experience and the network test to assess the connection to that test endpoint.

The bottom line

A+ bufferbloat means low added delay in a particular test—not a guarantee of lag-free gaming.

Start with the game’s symptom. Check its server region and network statistics, separate low FPS from network delay, compare Ethernet with Wi-Fi, and repeat measurements while the problem occurs. Revisit queue management only when the evidence points back to traffic under load.

Run a connection test with VelocityVerify and record the available measurements alongside your in-game observations. The useful outcome is not a better letter grade. It is a clearer understanding of what to test next.

Sources and measurement notes

This is a researched troubleshooting guide, not a report of original laboratory measurements. The numerical examples above are illustrative.

• Waveform: bufferbloat measurement and grading
• Ookla: assessing test results and measurement differences
• LinkSpeed: 5G latency and packet-loss troubleshooting