been with slingshot for the past 6 months or so have been getting constant 250 - 280 kbs download speeds
the past 2 to 3 weeks speeds have looked like this
currently have dynalink modem plugged directly into phone jack through extension cable (which is how i had it when i got the higher speeds) plus other phone jacks filterd , tried shorter cable ,tried isolation tests ,pings ,tracerts, tried using filter between modem and phone jack.
tried two diff modems plus different computer, tried clean install to elimate possibility of virus or spyware etc.tried diff ethernet cables. but nothing seems to help. i was told by slingshot after countless calls that after discussing with telecom my line was only capable of a 1.5meg connection and that the speed i was getting was the fastest i could get, and if i had got any speeds higher then that it was due to luck. i explained to the operator that for the past 6 months i have had constant 250 - 280 kbps download speeds during busy hours and off peek hours and the speed issue had only been happening for the past 2 weeks .i was asked to follow more test yada yada yada.
just wana know if anyone has any useful info for me thanks
heres info out of my modem
Line Mode G.DMT Line State Show Time
Latency Type Interleave Line Up Time 04:07:41:14
Line Coding Trellis On Line Up Count 1
Statistics Downstream Upstream
Line Rate 1408 Kbps 160 Kbps
Attainable Line Rate 1568 Kbps 936 Kbps
Noise Margin 12.3 dB 31.0 dB
Line Attenuation 63.5 dB 31.5 dB
Output Power 7.0 dBm 4.8 dBm
K (number of bytes in DMT frame) 45 6
R (number of check bytes in RS code word) 16 16
S (RS code word size in DMT frame) 4 8
D (interleave depth) 16 8
Super Frames 331049 331047
Super Frame Errors 32 2
RS Words 5627832 2813899
RS Correctable Errors 17643 18
RS Uncorrectable Errors 417 0
HEC Errors 31 2
OCD Errors 0 0
LCD Errors 0 0
Total Cells 1239535085 0
Data Cells 17479152 0
Bit Errors 0 0
Total ES 290 0
Total SES 11 0
Total UAS 45 0
sorry i dont have any info of modem stats befor i had speed props
but i never used any of this info until the problem started happening