dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
15

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca to dillyhammer

Premium Member

to dillyhammer

Re: Connection down, in lower Hamilton

Okay, will leave it in the hands of our capable folk.

FWIW, having proof there was truly loss between your computer and 10.199.4.1 directly (without the router) would give us more ammo with the Cogeco ticket since the router can't be pointed at, especially for an intermittent type issue.

Enjoy the fish and your weekend!

dillyhammer
START me up
Premium Member
join:2010-01-09
Scarborough, ON

dillyhammer

Premium Member

Ok , direct to modem.

C:\Users\Mike>tracert start.ca

Tracing route to start.ca[204.101.4.1]

1 7ms 7ms 7ms 10.199.4.1
2 9ms 9ms 8ms asr-link1-burlington1.net.start.ca [64.140.112.154]
3 10ms 9ms 9ms core1-toronto1-te3-3.net.start.ca [64.140.112.153]
4. 13ms 13ms 13ms core1-london1.ge1-1801.net.start.ca [64.140.112.85]
5. 16ms 11ms 13ms ws01-010.start.ca [204.101.248.50]

C:\Users\Mike>ping start.ca -t

Pinging start.ca [204.101.248.50] with 32 bytes of data:
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Request timed out.
Request timed out.
Reply from 204.101.248.50: bytes=32 time=15ms TTL=59
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Reply from 204.101.248.50: bytes=32 time=13ms TTL=59
Request timed out.
Reply from 204.101.248.50: bytes=32 time=13ms TTL=59
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Request timed out.
Reply from 204.101.248.50: bytes=32 time=14ms TTL=59
Reply from 204.101.248.50: bytes=32 time=13ms TTL=59

Ping statistics for 204.101.248.50:
Packets: Sent = 15, Received = 11, Lost = 4 (27% loss),

C:\Users\Mike>

Like I said, what we already know. Not ammo. Smoking gun.

Mike

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca

Premium Member

Can you do the ping to 10.199.4.1 please? Pinging www.start.ca doesn't show where the loss is. Thanks.

dillyhammer
START me up
Premium Member
join:2010-01-09
Scarborough, ON

dillyhammer

Premium Member

Someone reset my modem remotely at 3:31pm. At 3:33pm it came back up. No packet loss since then.

I'm leaving pingplotter running on 10 second cycles for the next 48 hours.

FWIW, this is the longest I've been down in almost 9 years - since Primus bought Magma and fscked it all up.

Mike

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca

Premium Member

Okay, the test we need to see is pinging the internal IP while directly connected to the modem - that's the smoking gun. Cogeco closed the ticket at 11:20am after you reported it was fine again so they wouldn't have rebooted your modem specifically. Either you have an intermittent RF issue (although signals are fine according to Cogeco) or there was a problem with the node and they are working on it.

dillyhammer
START me up
Premium Member
join:2010-01-09
Scarborough, ON

dillyhammer

Premium Member

Ok. If the packet loss happens again, I'll do the ping to 10.199.4.1 direct from the modem.

I called back in to tech support at 1:30pm, BTW. They mentioned the ticket was already closed by Cogeco, that they'd found no packet loss.

I'll keep an eye on it. Not much we can do. You're at their mercy as much as I.

Mike

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca

Premium Member

said by dillyhammer:

I'll keep an eye on it. Not much we can do. You're at their mercy as much as I.

Of all the partners we work with, Cogeco is by far the most helpful when it comes to tickets, generally things don't stay broke long. Have a good one!

dillyhammer
START me up
Premium Member
join:2010-01-09
Scarborough, ON

2 edits

dillyhammer

Premium Member

said by rocca:

Of all the partners we work with, Cogeco is by far the most helpful when it comes to tickets, generally things don't stay broke long. Have a good one!

That's really good to know. Especially for the prices they're charging you.

Edit: as of Saturday noon no packet loss since. I did get a call from Start letting me know that Cogeco could find no issues at their end, and suggested it may have been a virus or something on my network. The fact is, there was an issue on their end, first hop out, and whatever they did to correct it at 3:23pm seemed to work.

Cogeco continues to be full of shit, which is why I would never in a million years do business with them directly.

Mike