Results 1 to 3 of 3

Thread: vdi on cogent?

  1. #1

    vdi on cogent?

    For the past few days all my servers on vdi seems to experience great slow down. A trace shows that all connection was routed through cogent. Anyone know why? Multiple trace shows they are on cogent and they are VERY SLOW.

    1 31 0 0 66.46.176.3 -
    2 0 0 0 216.191.97.41 pos5-3.core1-mtl.bb.attcanada.ca
    3 0 0 16 216.191.65.173 pos8-1.core2-tor.bb.attcanada.ca
    4 15 16 16 216.191.65.70 pos5-0.gwy1-chi.bb.attcanada.ca
    5 16 15 16 216.191.65.38 po-9-2.pr1.ord2.us.mfnx.net
    6 15 16 31 208.185.0.189 so-2-2-0.cr1.ord2.us.mfnx.net
    7 31 47 31 208.184.233.149 pos5-0.mpr1.dfw2.us.mfnx.net
    8 31 47 31 216.200.127.213 so-3-0-0.cr1.dfw2.us.mfnx.net
    9 31 47 31 64.125.31.218 so-4-0-0.pr1.dfw3.us.mfnx.net
    10 47 31 47 64.124.51.171 64.124.51.171.cogentco.com
    11 47 31 47 66.28.4.169 g3-8.core02.dfw01.atlas.cogentco.com
    12 47 47 47 66.28.4.38 p15-0.core01.mci01.atlas.cogentco.com
    13 62 63 47 66.28.4.34 p5-0.core02.ord01.atlas.cogentco.com
    14 63 62 63 66.28.4.85 p6-0.core02.jfk02.atlas.cogentco.com
    15 63 62 63 66.28.4.122 p6-0.core01.jfk01.atlas.cogentco.com
    16 78 62 63 66.28.65.146 g50.ba01.b002894-1.jfk01.atlas.cogentco.com
    17 62 63 62 66.250.4.118 vdi.demarc.cogentco.com
    18 78 63 78 66.78.63.246 pos.core2.cft.vdi.net
    19 63 62 63 66.78.63.250 ge.edge1.cft.vdi.net
    20 62 63 62 216.10.16.24 vdi.net

  2. #2
    Join Date
    Nov 2001
    Posts
    852
    From webreseller
    [[email protected] admin]$ /usr/sbin/traceroute vdi.net
    traceroute to vdi.net (216.10.16.24), 30 hops max, 38 byte packets
    1 66.54.168.1 (66.54.168.1) 0.783 ms 0.314 ms 0.281 ms
    2 66.7.139.81 (66.7.139.81) 1.109 ms 0.794 ms 0.978 ms
    3 o1-10s11.phl053s101.yipes.com (66.54.144.189) 2.401 ms 1.949 ms 1.751 ms
    4 o1-53s11.phl004bd01.yipes.com (66.54.144.110) 2.792 ms 2.146 ms 2.372 ms
    5 66.54.175.193 (66.54.175.193) 2.467 ms 2.307 ms 1.985 ms
    6 gigabitethernet8-0-515.hsipaccess1.Philadelphia1.Level3.net (63.209.178.161) 2.180 ms 2.014 ms 2.138 ms
    7 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 2.204 ms 2.549 ms 2.718 ms
    8 so-3-0-0.mp2.NewYork1.Level3.net (64.159.1.42) 4.917 ms 5.587 ms 5.021 ms
    9 unknown.Level3.net (64.159.17.166) 5.557 ms 5.468 ms 5.659 ms
    10 ggr1-p370.n54ny.ip.att.net (63.211.54.66) 6.338 ms 7.176 ms 5.344 ms
    11 tbr2-p013802.n54ny.ip.att.net (12.122.12.53) 20.278 ms 7.214 ms 6.889 ms
    12 gar1-p340.nwrnj.ip.att.net (12.123.214.185) 6.509 ms 5.908 ms 5.744 ms
    13 12.119.140.50 (12.119.140.50) 6.506 ms 6.445 ms 6.536 ms
    14 pos.core2.cft.vdi.net (66.78.63.246) 76.775 ms 52.059 ms 96.456 ms
    15 ge.edge1.cft.vdi.net (66.78.63.250) 8.339 ms 8.037 ms 36.659 ms
    16 vdi.net (216.10.16.24) 8.850 ms 7.909 ms 7.781 ms


    From Dialtone
    [[email protected] root]# /usr/sbin/traceroute vdi.net
    traceroute to vdi.net (216.10.16.24), 30 hops max, 38 byte packets
    1 64.239.6.1 (64.239.6.1) 10.118 ms 11.631 ms 11.870 ms
    2 216.87.220.17 (216.87.220.17) 11.874 ms 9.914 ms 11.639 ms
    3 12.119.94.25 (12.119.94.25) 1.746 ms 11.674 ms 11.859 ms
    4 gbr4-p100.ormfl.ip.att.net (12.123.218.66) 16.115 ms 10.170 ms 11.461 ms
    5 gbr3-p20.attga.ip.att.net (12.122.2.181) 20.647 ms 24.004 ms 24.211 ms
    6 gbr2-p60.attga.ip.att.net (12.122.5.213) 23.389 ms 24.169 ms 23.827 ms
    7 tbr2-p013602.attga.ip.att.net (12.122.12.37) 24.922 ms 26.081 ms 22.132 ms
    8 * * *
    9 tbr1-p013301.wswdc.ip.att.net (12.122.11.169) 37.768 ms 41.637 ms 36.902 ms
    10 tbr1-p012201.n54ny.ip.att.net (12.122.10.17) 42.576 ms 40.758 ms 36.454 ms
    11 gar1-p3100.nwrnj.ip.att.net (12.123.214.181) 37.777 ms 42.952 ms 37.618 ms
    12 12.119.140.50 (12.119.140.50) 41.896 ms 42.184 ms 36.660 ms
    13 pos.core2.cft.vdi.net (66.78.63.246) 62.160 ms 80.546 ms 58.360 ms
    14 ge.edge1.cft.vdi.net (66.78.63.250) 42.957 ms 44.349 ms 39.984 ms
    15 vdi.net (216.10.16.24) 90.889 ms 43.355 ms 39.304 ms

  3. #3
    Join Date
    Sep 2000
    Location
    NY
    Posts
    489

    Re: vdi on cogent?

    [QUOTE]Originally posted by vegs
    [B]For the past few days all my servers on vdi seems to experience great slow down. A trace shows that all connection was routed through cogent. Anyone know why? Multiple trace shows they are on cogent and they are VERY SLOW.


    VDI can`t choose the incomming routes only your upstream can do that. try sending a tracert out from your server.

    If your provider is forcing cogent, then it lowers the cost for them. rogers in canada has 2 major uptreams, 1 is att canada, and they use telegloble which uses cogent.

    The important thing is the content being delivered, not the incomming request.

    The ping times on the trace are still prety low, 42 - 64
    -----My wife said it was ok----

Posting Permissions

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