cancel
Showing results for 
Search instead for 
Did you mean: 

Can no longer stream using discord

suezuki650
I'm here a lot

My son has been using discord to stream for quite some time, and now, although discord is running, he cannot stream.  It appears that it is being blocked by Rogers.  If he tried to use his phone to do the same thing (on wifi) it also doesn't work (so not his computer) but if he turns off wifi on his phone and just uses cell for internet, it works just fine.

 

We have not made any changes on our configurations.

 

Is anyone else having this problem?

 

*Added Labels*

21 REPLIES 21

Re: Can no longer stream using discord

-G-
Resident Expert
Resident Expert

@suezuki650  Welcome to the Community!

 

Are you an Ignite Internet customer?  If so, do you have Parental Controls and/or Protected Browsing enabled on your service?

Re: Can no longer stream using discord

We do not have ignite and have not changed anything.  Our Rogers box is in bridge mode and I have not reconfigured our router recently.

Re: Can no longer stream using discord

-G-
Resident Expert
Resident Expert

@suezuki650  Have you also tried either rebooting your router or resetting its WAN interface?  I have had to do this from time to time to fix semi-broken IPv6 network connectivity when Rogers does maintenance work in my corner of the network.

Re: Can no longer stream using discord

I have rebooted the router and it did not fix the problem.

 

 

Re: Can no longer stream using discord

Bloib
I've been here awhile

Hello,

 

It seems that Rogers internet is causing an issue with Discord East US servers. You get a constant connecting tone and will end with No Route. Can we have this looked into?

 

https://twitter.com/grimsbeard/status/1352648193897594889

 

 1  rt-ax88u-2a08 (192.168.50.1)  3.561 ms  2.140 ms  1.708 ms

 2  174.112.210.1 (174.112.210.1)  28.790 ms  16.457 ms  13.729 ms

 3  69.63.255.229 (69.63.255.229)  16.368 ms  16.370 ms  15.976 ms

 4  209.148.236.178 (209.148.236.178)  17.392 ms  13.315 ms  12.660 ms

 5  209.148.236.177 (209.148.236.177)  13.524 ms  16.249 ms  15.070 ms

 6  209.148.236.178 (209.148.236.178)  21.318 ms  10.508 ms  16.979 ms

 7  209.148.236.177 (209.148.236.177)  14.614 ms  16.139 ms  15.148 ms

 8  209.148.236.178 (209.148.236.178)  13.150 ms  14.290 ms  18.021 ms

 9  209.148.236.177 (209.148.236.177)  15.364 ms  10.519 ms  23.049 ms

10  209.148.236.178 (209.148.236.178)  15.511 ms  14.972 ms  19.079 ms

11  209.148.236.177 (209.148.236.177)  12.810 ms  10.977 ms  10.308 ms

12  209.148.236.178 (209.148.236.178)  14.516 ms  14.488 ms  17.752 ms

13  209.148.236.177 (209.148.236.177)  16.827 ms  13.076 ms  14.527 ms

14  209.148.236.178 (209.148.236.178)  15.002 ms  29.510 ms  15.968 ms

15  209.148.236.177 (209.148.236.177)  12.656 ms  20.181 ms  20.162 ms

16  209.148.236.178 (209.148.236.178)  12.940 ms  16.334 ms  23.590 ms

17  209.148.236.177 (209.148.236.177)  17.171 ms  15.421 ms  17.150 ms

18  209.148.236.178 (209.148.236.178)  14.271 ms  14.738 ms  15.499 ms

19  209.148.236.177 (209.148.236.177)  16.300 ms  10.663 ms  13.472 ms

20  209.148.236.178 (209.148.236.178)  19.900 ms  16.065 ms  15.397 ms

21  209.148.236.177 (209.148.236.177)  15.429 ms  15.268 ms  15.381 ms

22  209.148.236.178 (209.148.236.178)  16.470 ms  18.073 ms  16.979 ms

23  209.148.236.177 (209.148.236.177)  13.139 ms  17.107 ms  15.047 ms

24  209.148.236.178 (209.148.236.178)  14.287 ms  14.791 ms  13.984 ms

25  209.148.236.177 (209.148.236.177)  18.262 ms  17.549 ms  15.542 ms

26  209.148.236.178 (209.148.236.178)  17.117 ms  24.132 ms  13.722 ms

27  209.148.236.177 (209.148.236.177)  15.832 ms  24.501 ms  16.448 ms

28  209.148.236.178 (209.148.236.178)  16.479 ms  14.904 ms  13.492 ms

29  209.148.236.177 (209.148.236.177)  16.860 ms  17.153 ms  13.777 ms

30  209.148.236.178 (209.148.236.178)  11.845 ms  14.206 ms  25.021 ms

31  209.148.236.177 (209.148.236.177)  17.895 ms  13.860 ms  20.818 ms

32  209.148.236.178 (209.148.236.178)  13.093 ms  14.905 ms  14.502 ms

33  209.148.236.177 (209.148.236.177)  15.742 ms  14.571 ms  18.167 ms

34  209.148.236.178 (209.148.236.178)  27.552 ms  16.413 ms  18.598 ms

35  209.148.236.177 (209.148.236.177)  17.468 ms  20.463 ms  16.531 ms

36  209.148.236.178 (209.148.236.178)  12.189 ms  18.989 ms  16.203 ms

37  209.148.236.177 (209.148.236.177)  14.478 ms  13.063 ms  12.921 ms

38  209.148.236.178 (209.148.236.178)  21.105 ms  16.550 ms  13.567 ms

39  209.148.236.177 (209.148.236.177)  17.037 ms  31.104 ms  26.052 ms

40  209.148.236.178 (209.148.236.178)  20.863 ms  17.441 ms  21.144 ms

41  209.148.236.177 (209.148.236.177)  15.031 ms  11.608 ms  16.560 ms

42  209.148.236.178 (209.148.236.178)  14.663 ms  13.649 ms  15.749 ms

43  209.148.236.177 (209.148.236.177)  17.401 ms  17.505 ms  14.517 ms

44  209.148.236.178 (209.148.236.178)  32.021 ms  17.948 ms  16.665 ms

45  209.148.236.177 (209.148.236.177)  17.937 ms  15.534 ms  24.168 ms

46  209.148.236.178 (209.148.236.178)  22.863 ms  19.206 ms  14.307 ms

47  209.148.236.177 (209.148.236.177)  18.842 ms  14.860 ms  18.321 ms

48  209.148.236.178 (209.148.236.178)  23.475 ms  12.897 ms  17.486 ms

49  209.148.236.177 (209.148.236.177)  17.348 ms  13.080 ms  16.799 ms

50  209.148.236.178 (209.148.236.178)  21.387 ms  20.427 ms  18.227 ms

51  209.148.236.177 (209.148.236.177)  15.141 ms  22.617 ms  16.465 ms

52  209.148.236.178 (209.148.236.178)  11.151 ms  31.645 ms  11.131 ms

53  209.148.236.177 (209.148.236.177)  17.145 ms  14.664 ms  16.213 ms

54  209.148.236.178 (209.148.236.178)  15.001 ms  13.765 ms  16.174 ms

55  209.148.236.177 (209.148.236.177)  25.425 ms  15.234 ms  15.330 ms

56  209.148.236.178 (209.148.236.178)  13.380 ms  20.131 ms  15.784 ms

57  209.148.236.177 (209.148.236.177)  15.646 ms  15.256 ms  17.864 ms

58  209.148.236.178 (209.148.236.178)  23.984 ms  13.676 ms  18.013 ms

59  209.148.236.177 (209.148.236.177)  16.878 ms  18.232 ms  16.019 ms

60  209.148.236.178 (209.148.236.178)  14.084 ms  14.784 ms  15.008 ms

61  209.148.236.177 (209.148.236.177)  18.416 ms  16.269 ms  18.673 ms

62  209.148.236.178 (209.148.236.178)  15.347 ms  15.612 ms  17.022 ms

63  209.148.236.177 (209.148.236.177)  15.667 ms  21.222 ms  15.007 ms

64  209.148.236.178 (209.148.236.178)  14.813 ms  15.275 ms  16.395 ms

Re: Can no longer stream using discord

I also can’t at all

Re: Can no longer stream using discord

Bloib
I've been here awhile

Even switching regions doesn't let me watch or stream to others... something is very wrong on Rogers end. 

Re: Can no longer stream using discord

Shen1
I've been around

Same here, although my issue is I can't join most voice servers. Something is wrong with rogers Wifi.

Re: Can no longer stream using discord

Canada613
I've been around
Hi, I am also having this issue as of yesterday. The only interim solution i've found is to turn on a VPN. Hoping rogers can fix this ASAP.

Re: Can no longer stream using discord

I discovered a routing loop inside Rogers when trying to access Discord server. (us-east3716.discord.gg)

 

When I trace the address (us-east3716.discord.gg) I get to a Rogers address at 209.148.236.177 which sends me to 209.148.236.178. It gets sent back to the first and the loop continues forever or until timeout.

 

Can this be passed on the Rogers network admins?

 

 

Re: Can no longer stream using discord

I see my post got transferred here. Fix the routing loop and that should fix it for most people.

Re: Can no longer stream using discord

We tried the VPN workaround and it worked for us too.  Not an ideal fix but it's better than what we had.  Thanks.

Re: Can no longer stream using discord

That works because your network traffic is going around the routing loop. I assume you are getting a "No Route" message on your discord. If it's your Discord server, you can also change the server location to US Central or something else.

Re: Can no longer stream using discord

Just to add more data to this thread, here's the trace to the discord east coast server that @testestets mentioned:

 

C:\Users\Test>tracert us-east3716.discord.gg

 

Tracing route to us-east3716.discord.gg [162.244.55.113]

over a maximum of 30 hops:

 

  1           <1 ms    <1 ms    <1 ms  86U [xxx.xxx.xxx.xxx]

  2           12 ms    17 ms    16 ms  174.112.xxx.xxx

  3             9 ms    18 ms    10 ms     67.231.221.77

  4           11 ms    10 ms    11 ms  209.148.236.178

  5           11 ms    17 ms    32 ms  209.148.236.177

  6           11 ms    12 ms    11 ms  209.148.236.178                looped back to 178

  7           10 ms    11 ms    19 ms  209.148.236.177

  8           12 ms      8 ms     11 ms  209.148.236.178                looped back to 178

  9           12 ms    30 ms    10 ms  209.148.236.177

 10          12 ms    15 ms    12 ms  209.148.236.178                looped back to 178

 11          14 ms    10 ms    12 ms  209.148.236.177

 12            9 ms      9 ms     16 ms  209.148.236.178                looped back to 178

 13          10 ms    18 ms    10 ms  209.148.236.177

 14          14 ms    17 ms    15 ms  209.148.236.178                looped back to 178

 15          18 ms    11 ms    10 ms  209.148.236.177

 16            6 ms    17 ms    10 ms  209.148.236.178                looped back to 178

 17          14 ms    11 ms    18 ms  209.148.236.177

 18          20 ms    10 ms    10 ms  209.148.236.178                looped back to 178

 19          11 ms      9 ms    17 ms  209.148.236.177

 20          11 ms    19 ms    13 ms  209.148.236.178                looped back to 178

 21          11 ms    13 ms    11 ms  209.148.236.177

 22          12 ms    15 ms    10 ms  209.148.236.178                looped back to 178

 23          10 ms    15 ms    10 ms  209.148.236.177

 24          17 ms      9 ms     10 ms  209.148.236.178                looped back to 178

 25          11 ms    12 ms    16 ms  209.148.236.177

 26          12 ms    15 ms    13 ms  209.148.236.178                looped back to 178

 27          12 ms    12 ms    17 ms  209.148.236.177

 28          12 ms    11 ms    11 ms  209.148.236.178                looped back to 178

 29          18 ms    11 ms      9 ms  209.148.236.177

 30          13 ms    19 ms    11 ms  209.148.236.178                looped back to 178 & timeout

 

 

Another example of an East Coast Discord server showing the Rogers server loopback:

 

 

Trace complete.C:\Users\Test>tracert us-east8579.discord.gg

 

Tracing route to us-east8579.discord.gg [213.179.197.199]

over a maximum of 30 hops:

 

  1           <1 ms    <1 ms    <1 ms  86U [xxx.xxx.xxx.xxx]

  2           17 ms    13 ms    16 ms  174.112.xxx.xxx

  3           13 ms    12 ms      9 ms     67.231.221.77

  4           17 ms    10 ms    18 ms  209.148.236.178

  5           14 ms    12 ms    13 ms  209.148.236.177

  6           12 ms    17 ms      8 ms  209.148.236.178                looped back to 178

  7           11 ms    11 ms    16 ms  209.148.236.177

  8           14 ms    13 ms    12 ms  209.148.236.178                looped back to 178

  9           16 ms    12 ms    12 ms  209.148.236.177

 10          11 ms    14 ms    11 ms  209.148.236.178                looped back to 178

 11            9 ms     16 ms    17 ms  209.148.236.177

 12          14 ms    17 ms    15 ms  209.148.236.178                looped back to 178

 13          16 ms    13 ms      7 ms  209.148.236.177

 14          14 ms    11 ms    13 ms  209.148.236.178                looped back to 178

 15          10 ms    19 ms      9 ms  209.148.236.177

 16          20 ms    14 ms    14 ms  209.148.236.178                looped back to 178

 17          14 ms    13 ms      9 ms  209.148.236.177

 18          27 ms    16 ms    10 ms  209.148.236.178                looped back to 178

 19          15 ms    13 ms    17 ms  209.148.236.177

 20          17 ms    22 ms    16 ms  209.148.236.178                looped back to 178

 21          10 ms    21 ms    11 ms  209.148.236.177

 22          18 ms      9 ms     17 ms  209.148.236.178                looped back to 178

 23          17 ms    18 ms    10 ms  209.148.236.177

 24          13 ms      8 ms     12 ms  209.148.236.178                looped back to 178

 25          17 ms    12 ms    13 ms  209.148.236.177

 26          16 ms    18 ms    11 ms  209.148.236.178                looped back to 178

 27          10 ms    14 ms    17 ms  209.148.236.177

 28          16 ms      9 ms      9 ms  209.148.236.178                looped back to 178

 29          16 ms    18 ms    14 ms  209.148.236.177

 30          18 ms    17 ms      9 ms  209.148.236.178                looped back to 178 & timeout

 

Trace complete.

 

 

Examples of traces to Discord servers that work, sort of ......

C:\Users\Test>tracert us-central350.discord.gg

 

Tracing route to us-central350.discord.gg [138.128.141.62]

over a maximum of 30 hops:

 

  1           <1 ms    <1 ms    <1 ms  86U [xxx.xxx.xxx.xxx]

  2           14 ms    11 ms    16 ms  174.112.xxx.xxx

  3             8 ms    11 ms      5 ms     67.231.221.73

  4             9 ms    10 ms    11 ms  209.148.236.177

  5           14 ms      9 ms    18 ms  209.148.231.77

  6           13 ms    12 ms    17 ms  209.148.233.130

  7           *                            *                             *             Request timed out.

  8           *                            *                             *             Request timed out.

  9           *                            *                             *             Request timed out.

 10          *                            *                             *             Request timed out.

 11          *                            *                             *             Request timed out.

 12          35 ms    35 ms    30 ms  hosted-by.i3d.net [138.128.141.62]

 

Trace complete.

 

C:\Users\Test>tracert us-west6185.discord.gg

 

Tracing route to us-west6185.discord.gg [213.179.204.211]

over a maximum of 30 hops:

 

  1           <1 ms    <1 ms    <1 ms  86U [xxx.xxx.xxx.xxx]

  2           12 ms    15 ms      9 ms  174.112.xxx.xxx

  3           12 ms    13 ms    12 ms    67.231.221.73

  4           17 ms    12 ms    20 ms  209.148.236.177

  5           13 ms    11 ms    19 ms  209.148.236.169

  6           12 ms    21 ms    21 ms  209.148.233.130

  7           *                            *                             *             Request timed out.

  8           *                            *                             *             Request timed out.

  9           *                            *                             *             Request timed out.

 10          *                            *                             *             Request timed out.

 11          *                            *                             *             Request timed out.

 12          *                            *                             *             Request timed out.

 13          *                            *                             *             Request timed out.

 14          78 ms    97 ms    73 ms  hosted-by.i3d.net [213.179.204.211]

 

Trace complete.

 

Ping tests to the same Discord servers

 

This test to an East Coast server fails due to the server loopback:

 

C:\Users\Test>ping us-east3716.discord.gg

 

Pinging us-east3716.discord.gg [162.244.55.113] with 32 bytes of data:

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

 

Ping statistics for 162.244.55.113:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

 

 

 

This test to an East Coast server also fails due to the server loopback:

 

C:\Users\Test>ping us-east8579.discord.gg

 

Pinging us-east8579.discord.gg [213.179.197.199] with 32 bytes of data:

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

Reply from 209.148.236.178: TTL expired in transit.

 

Ping statistics for 213.179.197.199:

                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

 

 

This test works

 

C:\Users\Test>ping us-central350.discord.gg

 

Pinging us-central350.discord.gg [138.128.141.62] with 32 bytes of data:

Reply from 138.128.141.62: bytes=32 time=33ms TTL=56

Reply from 138.128.141.62: bytes=32 time=27ms TTL=56

Reply from 138.128.141.62: bytes=32 time=26ms TTL=56

Reply from 138.128.141.62: bytes=32 time=26ms TTL=56

 

Ping statistics for 138.128.141.62:

                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

                Minimum = 26ms, Maximum = 33ms, Average = 28ms

 

 

This test works as well:

 

C:\Users\Test>ping us-west6185.discord.gg

 

Pinging us-west6185.discord.gg [213.179.204.211] with 32 bytes of data:

Reply from 213.179.204.211: bytes=32 time=78ms TTL=54

Reply from 213.179.204.211: bytes=32 time=73ms TTL=54

Reply from 213.179.204.211: bytes=32 time=73ms TTL=54

Reply from 213.179.204.211: bytes=32 time=76ms TTL=54

 

Ping statistics for 213.179.204.211:

                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

                Minimum = 73ms, Maximum = 78ms, Average = 75ms

 

 

So, as @testestets indicates, fix the server loopback, which will hopefully fix the path to all of the Discord East Coast servers.  

Re: Can no longer stream using discord

Nice job posting all the traces that I'm too lazy to do. I'm not working today so not feeling it lol. Could we get some sort of confirmation that a network tech is looking into the issue?

Re: Can no longer stream using discord

🙂  I'll send a message to the mods to have the Network Operations Center look at the problem.

 

Edit:   Message sent.....

Re: Can no longer stream using discord

MohMoh11
I've been around

Having the exact same issue trying to connect to discord east as well. Did a Traceroute and got the same results as you. Seems to be bouncing between 209.148.236.178 and 209.148.236.177.

Rogers please do something to fix this.

Re: Can no longer stream using discord

I am no longer getting the routing loop, looks like it got fixed. Well done.

 

😀

 

Re: Can no longer stream using discord

Looks like this is fixed.  Here's yesterdays and todays results:

 

Yesterdays trace (Saturday 23 Jan 2021):

 

C:\Users\Test>tracert us-east3716.discord.gg

 

Tracing route to us-east3716.discord.gg [162.244.55.113]

over a maximum of 30 hops:

 

  1           <1 ms    <1 ms    <1 ms  86U [xxx.xxx.xxx.xxx]

  2           12 ms    17 ms    16 ms  174.112.xxx.xxx

  3             9 ms    18 ms    10 ms     67.231.221.77

  4           11 ms    10 ms    11 ms  209.148.236.178

  5           11 ms    17 ms    32 ms  209.148.236.177

  6           11 ms    12 ms    11 ms  209.148.236.178                looped back to 178

  7           10 ms    11 ms    19 ms  209.148.236.177

  8           12 ms      8 ms     11 ms  209.148.236.178                looped back to 178

  9           12 ms    30 ms    10 ms  209.148.236.177

 10          12 ms    15 ms    12 ms  209.148.236.178                looped back to 178

 11          14 ms    10 ms    12 ms  209.148.236.177

 12            9 ms      9 ms     16 ms  209.148.236.178                looped back to 178

 13          10 ms    18 ms    10 ms  209.148.236.177

 14          14 ms    17 ms    15 ms  209.148.236.178                looped back to 178

 15          18 ms    11 ms    10 ms  209.148.236.177

 16            6 ms    17 ms    10 ms  209.148.236.178                looped back to 178

 17          14 ms    11 ms    18 ms  209.148.236.177

 18          20 ms    10 ms    10 ms  209.148.236.178                looped back to 178

 19          11 ms      9 ms    17 ms  209.148.236.177

 20          11 ms    19 ms    13 ms  209.148.236.178                looped back to 178

 21          11 ms    13 ms    11 ms  209.148.236.177

 22          12 ms    15 ms    10 ms  209.148.236.178                looped back to 178

 23          10 ms    15 ms    10 ms  209.148.236.177

 24          17 ms      9 ms     10 ms  209.148.236.178                looped back to 178

 25          11 ms    12 ms    16 ms  209.148.236.177

 26          12 ms    15 ms    13 ms  209.148.236.178                looped back to 178

 27          12 ms    12 ms    17 ms  209.148.236.177

 28          12 ms    11 ms    11 ms  209.148.236.178                looped back to 178

 29          18 ms    11 ms      9 ms  209.148.236.177

 30          13 ms    19 ms    11 ms  209.148.236.178                looped back to 178 & timeout

 

 

Todays trace (Sunday 24 Jan 2021):

 

C:\Users\Test>tracert us-east3716.discord.gg

 

Tracing route to us-east3716.discord.gg [162.244.55.113]

over a maximum of 30 hops:

 

  1          <1 ms    <1 ms    <1 ms     86U [xxx.xxx.xxx.xxx]

  2           13 ms    10 ms    13 ms     174.112.xxx.xxx

  3           13 ms    10 ms    11 ms        67.231.221.77

  4           11 ms    10 ms    10 ms     209.148.236.178

  5           13 ms    11 ms    12 ms     209.148.231.73

  6           19 ms    18 ms    20 ms        69.63.248.58

  7           24 ms    19 ms    19 ms     209.148.235.234

  8           33 ms    40 ms    53 ms     209.148.233.102

  9           37 ms    39 ms    58 ms     100ge.eqx-ashburn.misi3d.com [206.126.237.210]

 10          34 ms    36 ms    31 ms     hosted-by.i3d.net [162.244.55.113]

 

Trace complete.

 

The other previously failed trace also ran to completion this morning. 

 

I'm assuming that the path down to all of the Discord East Coast servers will also work.  If you find anything that still fails, please post the server ID.

Re: Can no longer stream using discord

mirzaishfaq
I've been around

when i turn on parental control on ignite modem it also blocked Discord. How can i unblock discord website?

Topic Stats
  • 21 replies
  • 5962 views
  • 13 Likes
  • 10 in conversation