Page 2 of 2 FirstFirst 12
Results 26 to 35 of 35
  1. #26
    Join Date
    Jan 2005
    Posts
    2,203
    My pings are in the 60ms range for the past few days. It has always been in the 40ms. I hope it goes back to normal soon.

  2. #27
    sagonet's network is even fast from my side of the world ... and they have super deals ... wonder if they need a reseller ... j/k

  3. #28
    Join Date
    Jul 2004
    Location
    BC, Canada
    Posts
    13
    I haven't had any problems personally, but my clients have. This all started on the 20th, and still continues up to this day. Nothing has been done on behalf of Sagonet, even after dozens of tickets and phone calls. Seems we're just playing a game of tag or something here.
    All 9 of my servers were completely useless to me for a total of 48 hours due to major latency problems as well as certain clients who were unable to connect to my services. after that 48 hour period, a few of the servers seemed to calm down, but now there are still 5 that have been offline for 11 days now because of this. I have been getting VERY frustrated with their support because it seems they are not taking any of my suggestions into consideration. I have just now sent them the link to this thread to prove to them that something IS infact wrong, since all I've been hearing so far is "We have no reports of any problems". Really ticks me off how they are misinformed as to what's going on with their own network. Or if it's not their network, they should atleast know something is up with Level3.
    The IP Engineering team looked into things and said they would contact level 3 staff and get back to me, however, that was 5 days ago, and still no reply. They got another ticket from me which they claim to have resolved, saying it was a problem with IRC, when IRC had absolutely nothing to do with it.
    If these problems continue to go unresolved, I will surely be packing up and moving elsewhere.

  4. #29
    I doubt you have 5 servers offline for 11 days. We have servers in multiple sub-nets and we haven't seen the issue you seen.

    Well you may have been attacked if you have IRC. So it may just have everything to do with it.

  5. #30
    Join Date
    Jul 2004
    Location
    BC, Canada
    Posts
    13
    IRC is not in use and hasn't been. All of these problems started the same day the routing problem came up, and it is still a routing problem as I've already proved in my trace routes. You're just like everybody else, including their staff. Trying to say it has nothing to do with what it really is. -_-

  6. #31
    Why don't you show a traceroute then?

    I say the same thing because we have a lot of servers there (a few times of what you do), and we have not a single issue on any of them.

  7. #32
    Join Date
    Jul 2004
    Location
    BC, Canada
    Posts
    13
    Yes I realize this, but as you can obviously see by this topic, there ARE people who have problems. I don't feel I need to prove anything to you, but here it is.

    1 13 ms 23 ms 17 ms 70.69.252.1
    2 16 ms 14 ms 14 ms rd1bb-ge4-0-2.vc.shawcable.net [64.59.159.66]
    3 17 ms 14 ms 17 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
    4 22 ms 23 ms 26 ms rc1wt-pos2-3.wa.shawcable.net [66.163.77.26]
    5 35 ms 20 ms 21 ms 4.79.110.1
    6 248 ms 189 ms 337 ms so-7-0-0.mp2.Seattle1.Level3.net [64.159.1.165]

    7 78 ms 598 ms 260 ms as-2-0.mp2.Tampa1.Level3.net [64.159.3.218]
    8 402 ms 74 ms 75 ms ge-1-1-51.car3.Tampa1.Level3.net [4.68.104.6]
    9 75 ms 74 ms 75 ms 4.79.144.2
    10 75 ms 75 ms 674 ms gi0-1.ds01.tpa.sagonet.net [65.110.32.8]
    11 560 ms 77 ms 75 ms unknown.sagonet.net [207.150.169.170]

    =======

    1 6 ms 5 ms 6 ms 70.69.252.1
    2 7 ms 8 ms 195 ms rd1bb-ge4-0-2.vc.shawcable.net [64.59.159.66]
    3 7 ms 7 ms 11 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
    4 12 ms 12 ms 50 ms rc1wt-pos2-3.wa.shawcable.net [66.163.77.26]
    5 12 ms 12 ms 34 ms 4.79.110.1
    6 208 ms 15 ms 12 ms so-7-0-0.mp2.Seattle1.Level3.net [64.159.1.165]

    7 458 ms 74 ms 501 ms as-2-0.mp2.Tampa1.Level3.net [64.159.3.218]
    8 488 ms 75 ms 74 ms ge-1-1-51.car3.Tampa1.Level3.net [4.68.104.6]
    9 75 ms 74 ms 75 ms 4.79.144.2
    10 75 ms 75 ms 75 ms gi0-1.ds01.tpa.sagonet.net [65.110.32.8]
    11 75 ms 551 ms 75 ms unknown.sagonet.net [207.150.169.170]

    ======

    1 27 ms 52 ms 53 ms 70.69.252.1
    2 16 ms 14 ms 18 ms rd1bb-ge4-0-2.vc.shawcable.net [64.59.159.66]
    3 84 ms 26 ms 17 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
    4 19 ms 23 ms 21 ms rc1wt-pos2-3.wa.shawcable.net [66.163.77.26]
    5 22 ms 35 ms 20 ms 4.79.110.1
    6 28 ms 20 ms 20 ms so-7-0-0.mp2.Seattle1.Level3.net [64.159.1.165]

    7 90 ms 84 ms 88 ms as-2-0.mp2.Tampa1.Level3.net [64.159.3.218]
    8 157 ms 220 ms 233 ms ge-1-1-53.car3.Tampa1.Level3.net [4.68.104.70]
    9 100 ms 95 ms 83 ms 4.79.144.2
    10 326 ms 227 ms 96 ms gi0-1.ds01.tpa.sagonet.net [65.110.32.8]
    11 84 ms 83 ms 83 ms unknown.sagonet.net [207.150.169.170]

  8. #33
    Join Date
    Jan 2005
    Posts
    2,203
    I didn't experience any of those issues you mentioned. None of my visitors complained either, they are from all over the world. Maybe it's your connection to Sago that's causing the problem.

  9. #34
    Well, there was an issue. That's last week. That's the original reason for this thread.

    You don't have to prove anything to me. But you need to backup your claims.

  10. #35
    Join Date
    Jul 2004
    Location
    BC, Canada
    Posts
    13
    Well I also have users from around the world, and about 500+ trace routes from all of my users which I have sent to Sagonet. I am simply mentioning that I am having problems, as I can see others are or were too. So I don't understand why I would need to back up my claim in a forum such as this, since not much help can be provided either way. Just my point of view.

    On a lighter note, I finally got through to them and they have one specific technician assigned to my issue. So hopefully that means things will start progressing a little faster from here on out.

    I still think the changes they made on that same day of the routing issue could be the cause of this, but of course, they won't take that into consideration.
    Last edited by Project; 06-30-2005 at 06:13 AM.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •