Question / Help Stream Quality 0 for the last 2 weeks. Use to be great. Speedtest looks good. ISP says everything is good. I'M LOST :(

L

LastBoss

New Member
My problem is...
My stream, which was great and stable for a long time at my current settings (6000bitrate/1080@30/faster/x264) is now awful and unable to remain stable even at 1000kbps (for the past 2+ weeks).
My Twitch Bandwidth Test V1.5 shows terribly low bandwidth and a quality of 0, for every ingest server.
https://i.imgur.com/qB707Yk.jpg

I have made no changes to my computers hardware or software (including OBS) leading up to when the issue began 2+ weeks ago.
Nothing has been done/changed inside my home regarding cables either.

I called my ISP today, and explained the issue...
The techsupport did not know what Twitch was and momentarily laughed when I explained it.
She said there were no problems in my area, and that my "signal strength looks fantastic".
She said my modem was provisioned correctly, but reprovisioned it anyways because she was out of ideas.
She then went on to suggest I upgrade to the internet package above my current one (300/15) to a whopping 600down/15up.
It was then clear to me that she didn't listen to/understand when I explained the problem being my upload to Twitch.
That was the end of that call.

My system is...
CPU: Intel i7-8700k@baseclock 3.7ghz
Motherboard: Asus Maximus X Hero (BIOS 1704)
Memory: 32gb G.Skill Ripjaws (4x8gb F4-3200C16-8GVKB)
GPU: MSI GeForce GTX970
OS: Windows 10 Pro (winver 1709)

OBS: 22.0.2 (64bit)

Modem/Router: HITRON CGNM-2250 (ISP provided)
I AM USING WIRED (I have tried 2 ethernet cables)

My ISP: Shaw Cable (Located in western Canada)
My advertised service plan: 300down/15up
My speedtest.net results: 330down/13up
https://www.speedtest.net/result/8001463778.png

My top 2 ingest servers have always been Seattle and Portland.
So I did Traceroutes for both ingest servers:
Code: 
C:\Windows\system32>tracert live-sea.twitch.tv

Tracing route to live-sea.twitch.tv [52.223.228.61]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2    24 ms    11 ms    12 ms  [My IP, I think]
  3    11 ms    25 ms    12 ms  rh63sp-rd-cmts.ek.shawcable.net [64.59.135.1]
  4    40 ms    40 ms    34 ms  rc1wt-be82.wa.shawcable.net [66.163.76.9]
  5     *     reserved.justin.tv [192.16.68.162]  reports: Destination net unreachable.

Trace complete.
Code: 
C:\Windows\system32>tracert live-pdx.twitch.tv

Tracing route to live-pdx.twitch.tv [52.223.225.184]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    11 ms    11 ms    17 ms  [My IP I think]
  3    19 ms    12 ms    19 ms  rh63sp-rd-cmts.ek.shawcable.net [64.59.135.1]
  4    49 ms    31 ms    31 ms  rc1wt-be82.wa.shawcable.net [66.163.76.9]
  5  reserved.justin.tv [192.16.68.162]  reports: Destination net unreachable.

Trace complete.

After some reading in the forums, I can see that "Packet Loss" seems to be what I am... Likely encountering...?
So I did a ping test of both ingest servers:
Code: 
C:\Windows\system32>ping live-sea.twitch.tv -t

Pinging live-sea.twitch.tv [52.223.227.225] with 32 bytes of data:
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
(...I let this go on for like 80 lines etc -SNIP-)

Ping statistics for 52.223.227.225:
    Packets: Sent = 82, Received = 78, Lost = 4 (4% loss),
Code: 
C:\Windows\system32>ping live-pdx.twitch.tv -t

Pinging live-pdx.twitch.tv [52.223.225.184] with 32 bytes of data:
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
(...I let this go on for like 80 lines etc -SNIP-)

Ping statistics for 52.223.225.184:
    Packets: Sent = 85, Received = 61, Lost = 24 (28% loss)

This is a screenshot of my Twitch Bandwidth Test:
https://i.imgur.com/qB707Yk.jpg

This is a screenshot of my OBS stats during the logfile I attached:
https://i.imgur.com/MIInXJO.jpg

This is a screenshot of Twitch Inspector, after the stream of the logfile I attached:
https://i.imgur.com/rUcJffM.jpg
 

Attachments

  • 2019-01-30 19-58-24.txt
    7.8 KB · Views: 86
Last edited:
koala

koala

Active Member
This is clearly a network issue. Somewhere on their way from your computer to the Twitch servers, most of your packets get lost.
There are several parts of the network where the issue might be located:
- on your machine
- on the connection between your machine and your router at home
- on your router at home
- on the connection between your router and your ISP
- somewhere within the ISP and its routing to Twitch
- somewhere on the Twitch server you chose

In addition:
- your ISP and your connection to the ISP looks decent, technically (regardless of the support that did not understand your issuel)

Most issues of this kind are located locally, i. e. within your network at home.
Try Twitch Bandwidth test on every Twitch server, not only North America. It should produce the same bad result for every server in the world, and if this is the case, we can rule out the Twitch servers as issue.

Do you have a second computer? Or some friend with a laptop? Connect that other computer to your network and perform the Twitch Bandwidth test with it. You don't need to install OBS on that computer, the Twitch Bandwidth test is enough. If the bandwidth of that test is ok, your issue lies within your PC. If the bandwidth test on that machine is as bad as on your machine, the issue probably doesn't lie on your machine.

You can also make that test the other way round. Connect your machine to a different network, for example at a neighbor, and retry the Twitch bandwidth test. If if works good, your machine is ok. If it is as bad as before, it's probably not your machine.

If it's not your machine, look at your router at home. Do you have some kind of parental controls activated on the router, or some QoS settings (prioritize some ports for network traffic)? You can rule out your router config if you factory-reset your router and don't do any post-configuration besides to restore basic internet access. If you have cable, the router should re-establish the internet connection on its own.

If it's your machine: did you made some firewall configuration? Additional security software? From the log can be seen you're using Windows Defender, this isn't causing any issues if not badly configured. Just letting it work works best.

It might be that you recently installed software (knowingly or unknowingly) that hook the network stack of your machine. Check what was installed around the time the issues started. You might got some PUA (potentially unwanted application) that scans your network traffic.
 
Narcogen

Narcogen

Active Member
If you have access to a VPN, even temporarily, I would run TwitchTest while connected to one. This looks like throttling.
 
C

christian_and22

New Member
LastBoss said:
My problem is...
My stream, which was great and stable for a long time at my current settings (6000bitrate/1080@30/faster/x264) is now awful and unable to remain stable even at 1000kbps (for the past 2+ weeks).
My Twitch Bandwidth Test V1.5 shows terribly low bandwidth and a quality of 0, for every ingest server.
https://i.imgur.com/qB707Yk.jpg

I have made no changes to my computers hardware or software (including OBS) leading up to when the issue began 2+ weeks ago.
Nothing has been done/changed inside my home regarding cables either.

I called my ISP today, and explained the issue...
The techsupport did not know what Twitch was and momentarily laughed when I explained it.
She said there were no problems in my area, and that my "signal strength looks fantastic".
She said my modem was provisioned correctly, but reprovisioned it anyways because she was out of ideas.
She then went on to suggest I upgrade to the internet package above my current one (300/15) to a whopping 600down/15up.
It was then clear to me that she didn't listen to/understand when I explained the problem being my upload to Twitch.
That was the end of that call.

My system is...
CPU: Intel i7-8700k@baseclock 3.7ghz
Motherboard: Asus Maximus X Hero (BIOS 1704)
Memory: 32gb G.Skill Ripjaws (4x8gb F4-3200C16-8GVKB)
GPU: MSI GeForce GTX970
OS: Windows 10 Pro (winver 1709)

OBS: 22.0.2 (64bit)

Modem/Router: HITRON CGNM-2250 (ISP provided)
I AM USING WIRED (I have tried 2 ethernet cables)

My ISP: Shaw Cable (Located in western Canada)
My advertised service plan: 300down/15up
My speedtest.net results: 330down/13up
https://www.speedtest.net/result/8001463778.png

My top 2 ingest servers have always been Seattle and Portland.
So I did Traceroutes for both ingest servers:
Code: 
C:\Windows\system32>tracert live-sea.twitch.tv

Tracing route to live-sea.twitch.tv [52.223.228.61]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2    24 ms    11 ms    12 ms  [My IP, I think]
  3    11 ms    25 ms    12 ms  rh63sp-rd-cmts.ek.shawcable.net [64.59.135.1]
  4    40 ms    40 ms    34 ms  rc1wt-be82.wa.shawcable.net [66.163.76.9]
  5     *     reserved.justin.tv [192.16.68.162]  reports: Destination net unreachable.

Trace complete.
Code: 
C:\Windows\system32>tracert live-pdx.twitch.tv

Tracing route to live-pdx.twitch.tv [52.223.225.184]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    11 ms    11 ms    17 ms  [My IP I think]
  3    19 ms    12 ms    19 ms  rh63sp-rd-cmts.ek.shawcable.net [64.59.135.1]
  4    49 ms    31 ms    31 ms  rc1wt-be82.wa.shawcable.net [66.163.76.9]
  5  reserved.justin.tv [192.16.68.162]  reports: Destination net unreachable.

Trace complete.

After some reading in the forums, I can see that "Packet Loss" seems to be what I am... Likely encountering...?
So I did a ping test of both ingest servers:
Code: 
C:\Windows\system32>ping live-sea.twitch.tv -t

Pinging live-sea.twitch.tv [52.223.227.225] with 32 bytes of data:
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
(...I let this go on for like 80 lines etc -SNIP-)

Ping statistics for 52.223.227.225:
    Packets: Sent = 82, Received = 78, Lost = 4 (4% loss),
Code: 
C:\Windows\system32>ping live-pdx.twitch.tv -t

Pinging live-pdx.twitch.tv [52.223.225.184] with 32 bytes of data:
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Reply from 192.16.68.162: Destination net unreachable.
Request timed out.
(...I let this go on for like 80 lines etc -SNIP-)

Ping statistics for 52.223.225.184:
    Packets: Sent = 85, Received = 61, Lost = 24 (28% loss)

This is a screenshot of my Twitch Bandwidth Test:
https://i.imgur.com/qB707Yk.jpg

This is a screenshot of my OBS stats during the logfile I attached:
https://i.imgur.com/MIInXJO.jpg

This is a screenshot of Twitch Inspector, after the stream of the logfile I attached:
https://i.imgur.com/rUcJffM.jpg
Click to expand...

Were you able to discover the issue? Im having the same problem. Thanks
 
You must log in or register to reply here.
Top