JioFiber Bufferbloat: 2024 vs 2026 but the lag spike is EXACTLY the same

[Rhishav]

Bufferbloat is still high on my Connection in Kolkata region just like it was all these years.

 

[Protector]

@frezzy321 Packetloss is not caused by 30 MBPS or even 100 MBPS speed plan.
Idle latency & Jitter is also not caused by such factors too. I am using JioFiber as backup connection thats why it is a 30 MBPS speed. My internet line is totally fine, there is always routing issue with them.

@Skye My friend live at different location with same issues too. We both face issue while using JioFiber to connect with AWS services or Cloudflare Services. Even after providing many information to JIO team, they just redirect to lame fast.com or speedtest.net and says everything okay.

 

[frezzy321]

@Protector I've used 30 Mbps here and it's pretty terrible experience. Packet loss like every 1 minute. So I said that. But if you know it's not speed related problem then keep contacting Jio until its solved is all I can say.

 

[frezzy321]

@Rhishav That's odd. However people of my area and surrounding then do not have bufferbloat.

 

[ipriyank]

@frezzy321 I am from Howrah and using Jio airfiber 100Mbps plan but facing this buffer bloat issue issue regulary.

PS C:\Windows\system32> ping 8.8.8.8 -n 50

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=47ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Request timed out.
Reply from 8.8.8.8: bytes=32 time=44ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=457ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=101ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=36ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=54ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=56ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=36ms TTL=111
Reply from 8.8.8.8: bytes=32 time=49ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111

Ping statistics for 8.8.8.8:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 457ms, Average = 43ms
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 2. PING AZURE UK SOUTH ===" -ForegroundColor Yellow


PS C:\Windows\system32> ping 40.104.66.226 -n 30

Pinging 40.104.66.226 with 32 bytes of data:
Reply from 40.104.66.226: bytes=32 time=60ms TTL=238
Reply from 40.104.66.226: bytes=32 time=60ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=117ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=68ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=60ms TTL=238
Reply from 40.104.66.226: bytes=32 time=62ms TTL=238
Reply from 40.104.66.226: bytes=32 time=59ms TTL=238
Reply from 40.104.66.226: bytes=32 time=63ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=59ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=57ms TTL=238
Reply from 40.104.66.226: bytes=32 time=59ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=69ms TTL=238
Reply from 40.104.66.226: bytes=32 time=62ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=73ms TTL=238
Reply from 40.104.66.226: bytes=32 time=60ms TTL=238
Reply from 40.104.66.226: bytes=32 time=58ms TTL=238
Reply from 40.104.66.226: bytes=32 time=64ms TTL=238
Reply from 40.104.66.226: bytes=32 time=130ms TTL=238

Ping statistics for 40.104.66.226:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 130ms, Average = 64ms
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 3. PING DURING DOWNLOAD (bufferbloat) ===" -ForegroundColor Yellow

=== 3. PING DURING DOWNLOAD (bufferbloat) ===
PS C:\Windows\system32> $job = Start-Job { Invoke-WebRequest -Uri "https://speed.cloudflare.com/__down?bytes=100000000" -UseBasicParsing -OutFile "NUL" -ErrorAction SilentlyContinue }
PS C:\Windows\system32> Start-Sleep -Seconds 3
PS C:\Windows\system32> Write-Host "Pinging WHILE downloading:"
Pinging WHILE downloading:
PS C:\Windows\system32> ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=126ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=51ms TTL=111
Reply from 8.8.8.8: bytes=32 time=33ms TTL=111
Reply from 8.8.8.8: bytes=32 time=29ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=92ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=37ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111

Ping statistics for 8.8.8.8:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 126ms, Average = 40ms
PS C:\Windows\system32> $job | Stop-Job -ErrorAction SilentlyContinue
PS C:\Windows\system32> $job | Remove-Job -ErrorAction SilentlyContinue
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 4. PING DURING UPLOAD (RDP is bidirectional!) ===" -ForegroundColor Yellow


Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=86ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=142ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=55ms TTL=111
Reply from 8.8.8.8: bytes=32 time=52ms TTL=111
Reply from 8.8.8.8: bytes=32 time=82ms TTL=111
Reply from 8.8.8.8: bytes=32 time=57ms TTL=111
Reply from 8.8.8.8: bytes=32 time=30ms TTL=111
Reply from 8.8.8.8: bytes=32 time=38ms TTL=111
Reply from 8.8.8.8: bytes=32 time=31ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=37ms TTL=111
Reply from 8.8.8.8: bytes=32 time=34ms TTL=111
Reply from 8.8.8.8: bytes=32 time=67ms TTL=111
Reply from 8.8.8.8: bytes=32 time=32ms TTL=111
Reply from 8.8.8.8: bytes=32 time=78ms TTL=111

Ping statistics for 8.8.8.8:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 142ms, Average = 50ms
PS C:\Windows\system32> $job2 | Stop-Job -ErrorAction SilentlyContinue
PS C:\Windows\system32> $job2 | Remove-Job -ErrorAction SilentlyContinue
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 5. PING GATEWAY (WiFi jitter) ===" -ForegroundColor Yellow

 

[ipriyank]

=== 5. PING GATEWAY (WiFi jitter) ===
PS C:\Windows\system32> ping 192.168.31.1 -n 30

Pinging 192.168.31.1 with 32 bytes of data:
Reply from 192.168.31.1: bytes=32 time=4ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=66ms TTL=64
Reply from 192.168.31.1: bytes=32 time=43ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=43ms TTL=64
Reply from 192.168.31.1: bytes=32 time=20ms TTL=64
Reply from 192.168.31.1: bytes=32 time=10ms TTL=64
Reply from 192.168.31.1: bytes=32 time=3ms TTL=64
Reply from 192.168.31.1: bytes=32 time=6ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=6ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64
Reply from 192.168.31.1: bytes=32 time=2ms TTL=64
Reply from 192.168.31.1: bytes=32 time=3ms TTL=64
Reply from 192.168.31.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.31.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 66ms, Average = 7ms PS C:\Windows\system32> PS C:\Windows\system32> Write-Host "`n=== 6. TRACEROUTE TO AZURE (compare with Round 1) ===" -ForegroundColor Yellow
=== 6. TRACEROUTE TO AZURE (compare with Round 1) ===
PS C:\Windows\system32> tracert -d -w 2000 -h 20 20.86.89.240

Tracing route to 20.86.89.240 over a maximum of 20 hops

1 3 ms 2 ms 1 ms 192.168.31.1
2 3 ms 2 ms 2 ms 192.0.0.1
3 * * * Request timed out.
4 10 ms 12 ms 9 ms 192.0.0.1
5 9 ms 8 ms 10 ms 192.0.0.1
6 8 ms 9 ms 9 ms 192.0.0.1
7 37 ms 9 ms 14 ms 172.26.110.162
8 8 ms 103 ms 93 ms 192.168.37.19
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 102 ms 35 ms 75 ms 104.44.196.187
13 * 54 ms 47 ms 51.10.34.214
14 * * * Request timed out.
15 199 ms 194 ms 202 ms 51.10.23.176
16 200 ms 203 ms 206 ms 51.10.23.183
17 193 ms 192 ms 196 ms 51.10.23.202
18 * * 195 ms 51.10.33.17
19 204 ms 197 ms 202 ms 104.44.55.65
20 * 313 ms 197 ms 51.10.34.242

Trace complete.
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 7. DNS SPEED (has it been changed?) ===" -ForegroundColor Yellow

=== 7. DNS SPEED (has it been changed?) ===
PS C:\Windows\system32> Write-Host "Default DNS:"
Default DNS:
PS C:\Windows\system32> Measure-Command { Resolve-DnsName google.com } | Select-Object TotalMilliseconds

TotalMilliseconds
-----------------
202.2444


PS C:\Windows\system32> Write-Host "Cloudflare:"
Cloudflare:
PS C:\Windows\system32> Measure-Command { Resolve-DnsName google.com -Server 1.1.1.1 } | Select-Object TotalMilliseconds

TotalMilliseconds
-----------------
214.3234


PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 8. EXTERNAL IP ===" -ForegroundColor Yellow

=== 8. EXTERNAL IP ===
PS C:\Windows\system32> (Invoke-WebRequest -Uri "https://api.ipify.org" -UseBasicParsing -TimeoutSec 10).Content
49.37.37.93
PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 9. WIFI DETAILS ===" -ForegroundColor Yellow

=== 9. WIFI DETAILS ===
PS C:\Windows\system32> netsh wlan show interfaces

There is 1 interface on the system:

Name : Wi-Fi
Description : Realtek RTL8852BE WiFi 6 802.11ax PCIe Adapter
GUID : 913cbfdd-0dc1-4da3-a159-e72b0dc34d18
Physical address : e8:65:38:22:2d:cd
Interface type : Primary
State : connected
SSID : Brahmos
AP BSSID : 3a:3b:ab:9f:b0:8a
Band : 5 GHz
Channel : 157
Connected Akm-cipher : [ akm = 00-0f-ac:02, cipher = 00-0f-ac:04 ]
Network type : Infrastructure
Radio type : 802.11ax
Authentication : WPA2-Personal
Cipher : CCMP
Connection mode : Auto Connect
Receive rate (Mbps) : 1201
Transmit rate (Mbps) : 1201
Signal : 100%
Rssi : -51
Profile : Brahmos
QoS MSCS Configured : 0
QoS Map Configured : 0
QoS Map Allowed by Policy : 0

PS C:\Windows\system32>
PS C:\Windows\system32> Write-Host "`n=== 10. CONNECTED DEVICES (ARP table) ===" -ForegroundColor Yellow

=== 10. CONNECTED DEVICES (ARP table) ===
PS C:\Windows\system32> arp -a

Interface: 192.168.31.27 --- 0xa
Internet Address Physical Address Type
192.168.31.1 b8-3b-ab-9f-b0-88 dynamic
192.168.31.173 0c-f0-7b-e8-da-bb dynamic
192.168.31.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
232.24.3.241 01-00-5e-18-03-f1 static
239.255.255.250 01-00-5e-7f-ff-fa static
239.255.255.251 01-00-5e-7f-ff-fb static
255.255.255.255 ff-ff-ff-ff-ff-ff static

 

[Protector]

@ipriyank If your ping to gateway is more than 3ms, you'll see that issue at every platform. Try to do these test with LAN rather than Wi-Fi because i think your Router is having some issue connecting with your device.

Usually, Ping to gateway usually stay at <1ms - 3ms but your goes above 60ms too. definitely something issue with your connectivity

 

[Skye]

@ipriyank I agree with @Protector. You should test it over Ethernet. JioFiber bufferbloat issue also occurs only when we are using full bandwidth (downloading at max speed), it doesn't happen randomly while doing nothing, especially not at all to the router itself.

It could be Wi-Fi scanning ping spikes. I face similar issue on my laptop too, but the impact is a lot worse in my case.

 

[ipriyank]

yes, with lan it is better. but i cannot connect to LAN and do my work. Note, it is JIO AIRFIBER. I want thinking of converting it fiber plan, go with airtel.

 

[frezzy321]

@ipriyank You will suffer from bufferbloat on AirFiber no matter what. It's not wired connection from source itself.