Here is a trace from my end

Tracing route to 198.92.98.77 over a maximum of 30 hops

1 2561 ms 28 ms 24 ms 24.81.4.1
2 50 ms 30 ms 29 ms rd1bb-ge3-1-1.vc.shawcable.net [64.59.152.2]
3 25 ms 29 ms 30 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
4 28 ms 30 ms 28 ms rc1wt-pos2-2.wa.shawcable.net [66.163.76.54]
5 34 ms 29 ms 29 ms ge-7-2-102.hsa2.Seattle1.Level3.net [63.211.200.
29]
6 54 ms 29 ms 30 ms ge-6-1-1.mp2.Seattle1.Level3.net [209.247.9.85]

7 91 ms 95 ms 95 ms as0.mp2.Tampa1.Level3.net [64.159.3.218]
8 91 ms 96 ms 95 ms unknown.Level3.net [64.159.1.150]
9 * * * Request timed out.

I still can't get on.
Deb can you email me some screen shots? :biggrin:

It's timing out inside level3's network. Possibly RC's hosting company has a dropped connection or bad peering with level3 or something. Shaw says it isn't their network and not their problem....

Me too, works ok here all day.

Walter

Typically they should contact the admin for the segment and notify them. Not just use the old "it's not our network" line.

Agreed Brad.

What I was told though is "we aren't a direct client of level3 so we can't initiate a trouble ticket".

Lazy...

how can we fix the problem?

Fo those that have access, can you grab RC e-mail address so we can e-mail RC and let them know. Maybe they can fix it from their end.

its down here in saskatchewan too. Im with access communications.

Anyone who has reefcentral working? Can I come over? I'm going through withdrawls. I think I'm going crazy :mad: