dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1245
share rss forum feed

HKPolice

join:2002-08-09
Scarborough, ON

[rCable] CBC FIFA football stream keeps choking

No, it's not the CBC server's fault because it works perfectly fine on Teksavvy DSL using the same desktop.

Diablo3 Americas server also chokes to 350ms at times, with a constant latency of 140-190ms which is barely playable. What is going on with Start's routing these days??


damir

join:2013-12-12
CANADA
start is going to ask you for some tracerts, can u provide them?

i am gaming atm, and i dont see any high latency myself

HKPolice

join:2002-08-09
Scarborough, ON
reply to HKPolice
CBC stream just died, I was getting packet loss to google & every other site. My friend on start cable 2 blocks away also experiencing the same thing.


DavePC

join:2013-08-18
Scarborough, ON
Can Verify The CBC server choking, all other connections are fine however, tracert provides nominal pings.

Kennedy and Steeles Area.

thephenom

join:2011-06-01
Scarborough, ON
reply to HKPolice
Yeah, my CBC stream died at the start of extra time as well. Tried reloading a few times, nothing.


Start Sam

join:2014-01-21
London, ON
kudos:3
reply to HKPolice
We're having an issue with part of our network, rocca's already on the case working to resolve it.

Sorry for the inconvience for all, we will get this resovled as soon as possible.


DavePC

join:2013-08-18
Scarborough, ON
Reviews:
·Rogers Hi-Speed
·Start Communicat..
Getting some immense packet loss, nevermind..

Pinging google.com [173.194.43.64] with 32 bytes of data:
Request timed out.

Ping statistics for 173.194.43.64:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

Tracing route to google.com [173.194.43.64]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 7 ms 8 ms 10.105.155.1
3 12 ms 10 ms 11 ms 209.148.244.165
4 11 ms 12 ms 10 ms 69.63.248.205
5 * 102 ms * 72.14.198.214
6 * 106 ms * 216.239.47.114
7 * 55 ms * 72.14.239.19
8 19 ms 18 ms 15 ms yyz08s09-in-f0.1e100.net [173.194.43.64]

Trace complete.


Yoorie

join:2011-11-22
Toronto, ON
reply to thephenom
Just started getting connection issues as well. Pinging google.com:
Ping statistics for 2607:f8b0:400b:806::100e:
Packets: Sent = 48, Received = 39, Lost = 9 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 131ms, Average = 49ms

18% loss and average latency of 49ms, when it's usually slightly below 10ms. Not an IPv6 issue either, as I tried to ping DSLReports and got similar statistics.

EDIT: Glad to see that you guys are already working on getting this resolved!


Doberman

@108.168.82.x
reply to DavePC
Same here in Mississauga. Major packet drop and high latency. Anyone else?


hagbard72

join:2000-10-02
Kingsville
reply to HKPolice
Problem is here in Kingsville as well. Can't even run speedtest. Lots of time outs to the start server.


TOPDAWG
Premium
join:2005-04-27
Calgary, AB
kudos:3
reply to HKPolice
same here I'm in midland sites won't load sometimes. oh well just wait it out.


rocca
Start.ca
Premium
join:2008-11-16
London, ON
kudos:23
reply to hagbard72
As Sam mentioned, having an issue in the core - working on it.

marka

join:2010-03-10
Fergus, ON
reply to HKPolice
I'm getting the same in Fergus on C cable, both streaming and in games.
--
semper ubi sub ubi


rocca
Start.ca
Premium
join:2008-11-16
London, ON
kudos:23
reply to rocca
Working on bypass, trying to determine if it was a network fault or a massive attack. Details when available.


dallas2

@108.168.22.x
reply to rocca
i thought i got ddos by someone thank god i came here and look


DavePC

join:2013-08-18
Scarborough, ON
Reviews:
·Rogers Hi-Speed
·Start Communicat..

1 edit
reply to rocca
yeah I see it it now within my tracert.

Pinging google.com [2607:f8b0:400b:806::1004] with 32 bytes of data:
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=9ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=18ms
Reply from 2607:f8b0:400b:806::1004: time=14ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=9ms
Reply from 2607:f8b0:400b:806::1004: time=9ms
Request timed out.
Reply from 2607:f8b0:400b:806::1004: time=9ms
Reply from 2607:f8b0:400b:806::1004: time=9ms 
Request timed out.
Request timed out.
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=18ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
Reply from 2607:f8b0:400b:806::1004: time=9ms
Reply from 2607:f8b0:400b:806::1004: time=8ms
 
Ping statistics for 2607:f8b0:400b:806::1004:
    Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 18ms, Average = 9ms
 
C:\Users\owner>ping google.com -4 -n 20
 
Pinging google.com [173.194.43.67] with 32 bytes of data:
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=17ms TTL=57
Reply from 173.194.43.67: bytes=32 time=11ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=17ms TTL=57
Reply from 173.194.43.67: bytes=32 time=16ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=9ms TTL=57
Request timed out.
Request timed out.
Reply from 173.194.43.67: bytes=32 time=9ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
Reply from 173.194.43.67: bytes=32 time=7ms TTL=57
Reply from 173.194.43.67: bytes=32 time=8ms TTL=57
 
Ping statistics for 173.194.43.67:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 17ms, Average = 9ms
 
Tracing route to google.com [2607:f8b0:400b:807::1004]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2600:16f6:ca84:ecb0::1
  2     9 ms     8 ms     *     ipv6-gw1-toronto1.net.start.ca [2600:1621:1::10]
 
  3   445 ms     *     1786 ms  core1-toronto1.net.start.ca [2600:1621:1::1] < I think this is the issue
  4     8 ms     9 ms     9 ms  2001:4860:1:1:0:9f54::
  5     9 ms     9 ms     7 ms  2001:4860::1:0:e38
  6     8 ms     8 ms     9 ms  2001:4860:0:1::4ab
  7     8 ms    10 ms     8 ms  yyz08s10-in-x04.1e100.net [2607:f8b0:400b:807::1
004]
 
 

Trace complete.

madchikun

join:2004-07-18
Canada
reply to Start Sam
Thanks Sam. Hopefully we can get this resolved during half of extra time so we can see the end of the game

HKPolice

join:2002-08-09
Scarborough, ON
reply to HKPolice
Apparently no internet at all according to my friend. I'm watching the game on my backup Teksavvy DSL line no problems at all.

What the hell is going on with start these days? Too much focus on customer service and not enough on infrastructure?

oldsam

join:2011-05-30
reply to HKPolice
Juuust in time for my Netflix break. Thanks Obama.


Yoorie

join:2011-11-22
Toronto, ON
reply to madchikun
I'd use my phone's data if I were watching the game right now! Fixing it may take a while; it's best to have a backup.


Nik6906

@207.219.69.x
reply to oldsam
Looks like an outage here in Toronto East on cable. It's extra time in the semi finals. Fiiiiiiix it


Yoorie

join:2011-11-22
Toronto, ON
reply to HKPolice
You're suggesting there is a downward trend in the performance or reliability of Start's infrastructure? I'm not aware of evidence to show this, besides this one incident, which isn't a trend.

In fact, Start significantly upgraded their core boxes just around 2 weeks ago.


billco

join:2011-02-11
Ottawa, ON
Reviews:
·Start Communicat..

1 edit
reply to HKPolice
Looks like I'm back to normal, as of a minute ago.

If it's any consolation, I've had all sorts of weird things fail today, out of the blue. Maybe today is like that Mayan end of the world, but for switching equipment... :P

Edit: almost normal... still getting a bit of packet loss, but it's surfable.


Anzio

join:2008-11-22
Innisfil, ON
reply to HKPolice
said by HKPolice:

Apparently no internet at all according to my friend. I'm watching the game on my backup Teksavvy DSL line no problems at all.

What the hell is going on with start these days? Too much focus on customer service and not enough on infrastructure?

To be entirely fair, I haven't seen any issues with Start other than this outage. Anything else was announced and anticipated maintenance.


Peekaboo

@24.114.76.x
reply to Yoorie
In actual fact I have had quite a few dropped packets in the last few days from that portion of starts network. I didn't want to think there was an issue but clearly there was something going on.


DavePC

join:2013-08-18
Scarborough, ON
Back up, just in time


smogers

@108.170.167.x
reply to HKPolice
Um to the OP it is FIFA Soccer not football.


Yoorie

join:2011-11-22
Toronto, ON
said by smogers :

Um to the OP it is FIFA Soccer not football.

Americans are the only ones calling Football "soccer" and Americans don't matter in football.

Also, the issue seems to have been fixed!


billco

join:2011-02-11
Ottawa, ON
reply to smogers
said by smogers :

Um to the OP it is FIFA Soccer not football.

Don't make me break out the duck tape.

mlord

join:2006-11-05
Nepean, ON
kudos:13
reply to Yoorie
Not fixed yet. Everything is crawling.. like back to the good old "Nortel 1meg modem" days.