Trouble connecting to Dallas twitch servers

[Vashiiq]

Tech Support Guy System Info Utility version 1.0.0.9
OS Version: Microsoft Windows 10 Pro, 64 bit, Build 18363, Installed 20200713130528.000000-300
Processor: AMD Ryzen 7 3800X 8-Core Processor, AMD64 Family 23 Model 113 Stepping 0, CPU Count: 16
Total Physical RAM: 24 GB
Graphics Card: NVIDIA Geforce RTX 2080
Hard Drives: C: 930 GB (175 GB Free); D: 931 GB (317 GB Free); E: 0 GB (0 GB Free); F: 453 GB (220 GB Free); G: 11 GB (11 GB Free); H: 111 GB (111 GB Free);
Motherboard: Gigabyte Technology Co., Ltd. AB350M-Gaming 3-CF, ver x.x, s/n Default string
System: American Megatrends Inc., ver ALASKA - 1072009, s/n Default string
Antivirus: Windows Defender, Enabled and Updated

https://testmy.net/uCY-NHOyB.png

http://imgur.com/a/1F23Pqh

^ Upload examples. Imgur link is to Twitch servers.

I stream daily on twitch.tv. For the past 2 years i've been dealing with this internet problem, that I have terrible upload to servers that arent COX related, and cannot connect to Dallas Texas servers for the life of me.

my ISP is Cox,(yeah I know..) and I've had over 12+ techs out over the span of a year now. They've changed many cables, many different things, nothing is wrong with my house.

I use a NETGEAR AC1900 C6300BD, I also have a NETGEAR Nighthawk AC1900 Model R7000, that I am not using, because I was told router/modem combos do NOT go well when connected to another router. I was also using the router/modem that COX gave me, but I decided to not use it, as it gave worse performance overall.

I cannot change ISPs, even though ATT's services are very close to my house, they refuse to put service on my street.

I do NOT have Fiber internet, which is kind of a drag.

I live in Louisiana, fairly close to Texas. I get DAILY packet loss.

I've shown COX support everything I can, they just do not listen, and ask for a tech to come out, which I don't want anymore, because they tell me, that it's NOT my residence.

I am extremely desperate these days. Moving is not an option, I wish it was.

If you need any more information about anything, so that you can help, please ask.

Please help me.

 

[lunarlander]

You are probably using wi-fi. Try connecting an ethernet cable and see. Ethernet usually gets better speeds because it takes away the variablility of wi-fi: distance from router, line of sight, concrete walls etc.

 

[Vashiiq]

You are probably using wi-fi. Try connecting an ethernet cable and see. Ethernet usually gets better speeds because it takes away the variablility of wi-fi: distance from router, line of sight, concrete walls etc.

my PC is in fact connected to the modem via Ethernet.

 

[lunarlander]

Is the receiving end on the PC a Gigabit Ethernet card ?

Is this a laptop or brand name desktop? If so, please give Brand and Model .

 

[Vashiiq]

Is the receiving end on the PC a Gigabit Ethernet card ?

Is this a laptop or brand name desktop? If so, please give Brand and Model .

This is on a PC with a Gigabit ethernet card, yes.

 

[Vashiiq]

Is the receiving end on the PC a Gigabit Ethernet card ?

Is this a laptop or brand name desktop? If so, please give Brand and Model .

Regarding the model of the PC, i've custom built it.

 

[Couriant]

Let’s start from the top.

You are connected Ethernet to the router.

The router is connected to the modem.

The modem is NOT the wireless combo.

What speed are you paying for?

what speeds are you getting at when connected directly to the modem?

when connected to the modem, do the command at Command Prompt:

ping google.com -n 100

copy and paste the end result here (the statistics portion)

 

[Vashiiq]

Let’s start from the top.

You are connected Ethernet to the router.

The router is connected to the modem.

The modem is NOT the wireless combo.

What speed are you paying for?

what speeds are you getting at when connected directly to the modem?

when connected to the modem, do the command at Command Prompt:

ping google.com -n 100

copy and paste the end result here (the statistics portion)

I am connected via Ethernet to a modem/router combo.

I HAVE a router that i can use, but I am not currently.

I'm paying for 150down 10up, because it is all I need. I used to have gigablast, but I downgraded because I never got the upload anyway.

The speeds i have shown you are the speeds when i'm directly connected to the modem

Pinging google.com [172.217.1.142] with 32 bytes of data:
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=22ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=23ms TTL=118
Request timed out.
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=23ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=35ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=21ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=23ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=21ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=25ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Request timed out.
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=22ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118
Reply from 172.217.1.142: bytes=32 time=19ms TTL=118
Reply from 172.217.1.142: bytes=32 time=17ms TTL=118
Reply from 172.217.1.142: bytes=32 time=20ms TTL=118
Reply from 172.217.1.142: bytes=32 time=18ms TTL=118

Ping statistics for 172.217.1.142:
Packets: Sent = 100, Received = 98, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 35ms, Average = 18ms

 

[TerryNet]

What download/upload do you get with Speedtest.net? Please run it a few times, as it can vary a little.

 

[Vashiiq]

What download/upload do you get with Speedtest.net? Please run it a few times, as it can vary a little.

http://imgur.com/a/9uzgkfB

It is good. But the reason it is good, is because it's connected to the closest possible servers, which as you can see there. I'm having trouble connecting to Dallas twitch servers, as seen in the imgur, in the original post.

 

[Vashiiq]

By the way, this does not ALWAYS happen. It is very random, sometimes it's good, sometimes it's not.

 

[TerryNet]

The Speedtest.net results support the COX techs saying that it's "NOT [your] residence." That is, between your computer and the COX gateway server all is good.

I don't know what you can do about it, and COX may also have no control and/or not willing to investigate. If you discuss with COX again be sure to ask for a "tier 2" or supervisor. Any first level tech support who can understand what might be happening has already been promoted to tier 2 or supervisor (or whatever terminology they use).

Maybe much of the time there is just too much network congestion between you and the desired servers.

Or maybe the COX routing is non optimal. This is something they could investigate, but good luck convincing them to do so. Sometimes an ISP's routing (on one or more or all their gateway servers) can get messed up to the point of making certain web sites unreachable.

 

[Couriant]

I agree. The ping test and the speed test shows you are good. If you have an up address of the servers, perhaps a trace route may find where the bottleneck is but if is past Coxs network and on Level 3 and beyond, CoZ may not do anything... maybe report it if there is other people worth the same issue

 

[Couriant]

Also if the twitch is good now. Try the ping when it’s not and see if you get a different result. If it’s different then do Tracert google.com in command prompt.

 

[TerryNet]

Do a tracert to the desired server (and save the results in a file) and check the IP configuration of the device (router or computer) connected to the modem when you have a good upload and another when the upload is poor or fails. If the routes are different you may have evidence to motivate COX to investigate.