- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Calling/live chat with tech support hasnt been helping me. They been telling me the congestion will be fixed and some would say they cant fix it. My trace route test show the issue is with a verizon node.
Tracing route to google.com [74.125.239.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
2 24 ms 24 ms 23 ms
3 25 ms 27 ms 29 ms P0-1-2-1.LSANCA-LCR-22.verizon-gni.net
4 125 ms 66 ms 25 ms so-4-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.248]
5 124 ms 30 ms 27 ms 0.xe-6-0-3.XL3.LAX15.ALTER.NET [152.63.113.169]
6 31 ms 33 ms 29 ms TenGigE0-4-4-0.GW4.LAX15.ALTER.NET [152.63.115.242]
7 28 ms 27 ms 26 ms google-gw.customer.alter.net [63.125.112.154]
8 28 ms 28 ms 27 ms 216.239.46.40
9 27 ms 27 ms 27 ms 216.239.43.148
10 27 ms 27 ms 29 ms lax04s09-in-f8.1e100.net [74.125.239.8]
Tracing route to 0.xe-6-0-3.XL3.LAX15.ALTER.NET [152.63.113.169]
1 <1 ms <1 ms <1 ms
2 147 ms 157 ms 165 ms
3 191 ms 189 ms 198 ms P0-1-2-1.LSANCA-LCR-21.verizon-gni.net [130.81.44.26]
4 210 ms 216 ms 221 ms so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 258 ms 250 ms 249 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
6 284 ms 279 ms 288 ms 0.xe-6-0-3.XL3.LAX15.ALTER.NET [152.63.113.169]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WEB100 Kernel Variables: Client: localhost/127.0.0.1
CurMSS: 1460
X_Rcvbuf: 87380
X_Sndbuf: 172592
AckPktsIn: 516
AckPktsOut: 0
BytesRetrans: 2920
CongAvoid: 288
CongestionOverCount: 0
CongestionSignals: 2
CountRTT: 440
CurCwnd: 24820
CurRTO: 405
CurRwinRcvd: 65536
CurRwinSent: 5888
CurSsthresh: 23360
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 1440724
DataPktsIn: 0
DataPktsOut: 975
DupAcksIn: 74
ECNEnabled: 0
FastRetran: 2
MaxCwnd: 67160
MaxMSS: 1460
MaxRTO: 687
MaxRTT: 466
MaxRwinRcvd: 65536
MaxRwinSent: 5888
MaxSsthresh: 32120
MinMSS: 1460
MinRTO: 244
MinRTT: 44
MinRwinRcvd: 65536
MinRwinSent: 5840
NagleEnabled: 1
OtherReductions: 1
PktsIn: 516
PktsOut: 975
PktsRetrans: 2
RcvWinScale: 7
SACKEnabled: 3
SACKsRcvd: 76
SendStall: 0
SlowStart: 70
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SlowStart: 70
hedRTT: 202
SndWinScale: 8
SndLimTimeRwin: 2170891
SndLimTimeCwnd: 7819615
SndLimTimeSender: 164756
SndLimTransRwin: 3
SndLimTransCwnd: 11
SndLimTransSender: 8
SndLimBytesRwin: 239760
SndLimBytesCwnd: 1164760
SndLimBytesSender: 36204
SubsequentTimeouts: 0
SumRTT: 128835
Timeouts: 0
TimestampsEnabled: 0
WinScaleRcvd: 8
WinScaleSent: 7
DupAcksOut: 0
StartTimeUsec: 532729
Duration: 10158366
c2sData: 2
c2sAck: 2
s2cData: 8
s2cAck: 2
half_duplex: 0
link: 0
congestion: 0
bad_cable: 0
mismatch: 0
spd: 1.13
bw: 0.84
loss: 0.002051282
avgrtt: 292.81
waitsec: 0.00
timesec: 10.00
order: 0.1434
rwintime: 0.2138
sendtime: 0.0162
cwndtime: 0.7700
rwin: 0.5000
swin: 1.3168
cwin: 0.5124
rttsec: 0.292807
Sndbuf: 172592
aspd: 0.00000
CWND-Limited: 225.88
minCWNDpeak: 2920
maxCWNDpeak: 67160
CWNDpeaks: 2
The theoretical network limit is 0.84 Mbps
The NDT server has a 84.0 KByte buffer which limits the throughput to 4.49 Mbps
Your PC/Workstation has a 64.0 KByte buffer which limits the throughput to 1.70 Mbps
The network based flow control limits the throughput to 1.74 Mbps
Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is 'OC-48', Server Acks report link is 'T1'