Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Anyone else having issues with incero or colocrossing routing? (solved)
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Anyone else having issues with incero or colocrossing routing? (solved)

MaouniqueMaounique Host Rep, Veteran
edited May 2014 in General

I have strange issues in the dallas location and they say it is not their issue. It also seems to be going on mostly with china but also colocrossing, can you post some MTRs between both locations if you can and/or china/incero dallas?

So far confirmed issues with miami and los angeles.

One of the examples from LA colocrossing:

3 10.9.4.177 (10.9.4.177) 2.870 ms 2.873 ms 69.31.114.169 (69.31.114.169) 0.239 ms
4 ae3-50g.cr1.lax1.us.nlayer.net (69.31.124.113) 0.570 ms 0.614 ms 69.31.114.169 (69.31.114.169) 0.247 ms
5 mpr1.lax2.us.above.net (206.223.123.71) 0.615 ms 0.578 ms ae3-50g.cr1.lax1.us.nlayer.net (69.31.124.113) 0.552 ms
6 mpr1.lax2.us.above.net (206.223.123.71) 0.581 ms 0.722 ms ae12.cr1.lax112.us.above.net (64.125.20.229) 0.735 ms
7 ae4.cr1.iah1.us.above.net (64.125.25.46) 67.858 ms 67.892 ms ae12.cr1.lax112.us.above.net (64.125.20.229) 0.666 ms
8 ae4.cr1.iah1.us.above.net (64.125.25.46) 67.858 ms 67.803 ms ae0.cr1.dfw2.us.above.net (64.125.20.197) 67.822 ms
9 ae0.cr1.dfw2.us.above.net (64.125.20.197) 40.754 ms 48.825 ms ae4.er1.dfw2.us.above.net (64.125.27.74) 48.621 ms
10 ae4.er1.dfw2.us.above.net (64.125.27.74) 48.657 ms 48.694 ms *
11 * * bc2-side-from-r1.inceronetwork.com (192.211.63.10) 48.544 ms
12 bc2-side-from-r1.inceronetwork.com (192.211.63.10) 48.502 ms * 48.487 ms

There are also multiple reports from china but it does seem to be working when I try it.

Our lg is http://lg-dallas.prometeus.net

Comments

  • RalliasRallias Member
    edited May 2014

    Forgive me for being dull, but that traceroute looks normal to me. What's the problem you're seeing?

  • MaouniqueMaounique Host Rep, Veteran

    Not really, they stop at incero door. That is the last hop. Similar, when I want to trace colocrossing, stops at incero door, however, not always. They say nlayer is dropping our packets, but that is not confirmed, I can access them, so we are still diggin'.

  • netomxnetomx Moderator, Veteran

    From my home:

      4     2 ms     4 ms     3 ms  bb-symm-201-158-223-46.gdljal.static.axtel.net [
    201.158.223.46]
      5     4 ms     7 ms     5 ms  ifwa-ln3-201-140-38-178.mtyxl.static.axtel.net [
    201.140.38.178]
      6     4 ms     *      150 ms  te4-1.ccr01.mty01.atlas.cogentco.com [38.104.248
    .29]
      7     8 ms    11 ms    10 ms  te0-4-0-1.rcr21.mfe01.atlas.cogentco.com [154.54
    .1.97]
      8    15 ms    16 ms    15 ms  be2420.ccr21.iah01.atlas.cogentco.com [154.54.42
    .65]
      9    21 ms    21 ms    20 ms  be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25
    .106]
     10    25 ms    24 ms    31 ms  be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.
    46]
     11    21 ms    47 ms    21 ms  64.125.12.169
     12    21 ms    22 ms    20 ms  208.185.52.198.IPYX-078076-900-ZYO.above.net [20
    8.185.52.198]
     13    26 ms    42 ms    25 ms  bc2-side-from-r1.inceronetwork.com [192.211.63.1
    0]
    
    Thanked by 1Maounique
  • MaouniqueMaounique Host Rep, Veteran

    @netomx said:
    From my home:

    >   4     2 ms     4 ms     3 ms  bb-symm-201-158-223-46.gdljal.static.axtel.net [
    > 201.158.223.46]
    >   5     4 ms     7 ms     5 ms  ifwa-ln3-201-140-38-178.mtyxl.static.axtel.net [
    > 201.140.38.178]
    >   6     4 ms     *      150 ms  te4-1.ccr01.mty01.atlas.cogentco.com [38.104.248
    > .29]
    >   7     8 ms    11 ms    10 ms  te0-4-0-1.rcr21.mfe01.atlas.cogentco.com [154.54
    > .1.97]
    >   8    15 ms    16 ms    15 ms  be2420.ccr21.iah01.atlas.cogentco.com [154.54.42
    > .65]
    >   9    21 ms    21 ms    20 ms  be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25
    > .106]
    >  10    25 ms    24 ms    31 ms  be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.
    > 46]
    >  11    21 ms    47 ms    21 ms  64.125.12.169
    >  12    21 ms    22 ms    20 ms  208.185.52.198.IPYX-078076-900-ZYO.above.net [20
    > 8.185.52.198]
    >  13    26 ms    42 ms    25 ms  bc2-side-from-r1.inceronetwork.com [192.211.63.1
    > 0]
    > 

    So you can access the site? Please use the lg and see if it works.

  • netomxnetomx Moderator, Veteran

    @Maounique said:
    So you can access the site? Please use the lg and see if it works.

    what site? I just took the last IP and tracert it. Do you mean http://colocrossing.com/ ?

  • MaouniqueMaounique Host Rep, Veteran

    no, lg-dallas.prometeus.net

  • netomxnetomx Moderator, Veteran

    @Maounique said:
    no, lg-dallas.prometeus.net

    I can access it.

    OST: lg-dallas                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
    1.|-- 192-211-58-130-customer-incero.com              0.0%    10    0.0   0.0   0.0   0.0   0.0
    2.|-- r1-side-from-bc2.inceronetwork.com              0.0%    10    0.2   0.2   0.2   0.2   0.0
    3.|-- ae0.er1.dfw2.us.above.net                       0.0%    10    0.4   0.4   0.3   0.4   0.0
    4.|-- 64.125.12.170                                   0.0%    10    1.0   1.0   0.8   2.0   0.4
    5.|-- be2031.ccr21.dfw01.atlas.cogentco.com           0.0%    10    1.6   1.6   1.6   1.8   0.1
    6.|-- be2145.mpd21.iah01.atlas.cogentco.com           0.0%    10    6.6   6.8   6.6   6.9   0.1
    7.|-- be2422.rcr21.mfe01.atlas.cogentco.com           0.0%    10   14.7  14.8  14.7  14.9   0.1
    8.|-- te8-1.ccr01.mty01.atlas.cogentco.com           40.0%    10   17.3  57.6  17.3 160.2  57.2
    9.|-- 38.104.245.50                                   0.0%    10   19.3  19.7  18.2  21.8   1.3
    10.|-- ifwa-ln3-201-140-38-225.mtyxl.static.axtel.net  0.0%    10   18.8  19.0  18.7  19.2   0.2
    11.|-- bb-symm-201-158-223-53.gdljal.static.axtel.net  0.0%    10   18.4  18.5  18.4  18.7   0.1
    12.|-- xxxxxxxxxx.static.axtel.net                   0.0%    10   19.9  20.1  19.5  21.7   0.6
    
    Thanked by 1Maounique
  • SpencerSpencer Member

    I have some servers that are single homed nlayer in Dallas, and like 18 hours ago they were having a TON of network issues. Woke up to 70+ text messages from nodeping about it.

    Thanked by 1Maounique
  • MaouniqueMaounique Host Rep, Veteran
    edited May 2014

    Spencer said: I have some servers that are single homed nlayer in Dallas, and like 18 hours ago they were having a TON of network issues. Woke up to 70+ text messages from nodeping about it.

    Incero says nlayer dropped our ranges out of the blue but they are restored now. This happened before in march and I will dig further to see why this happened and how can we prevent it. People say they had problems here as far as 10 hours ago but only opened tickets when it got worse.
    I have no nodeping or any other report about it, it did work for me from all locations i tried, only some customers saw it, I am really puzzled about this.

  • hiphiphip0hiphiphip0 Member
    edited May 2014

    Route goes to above.net, download speed is fine, around 300KB/s.
    Latency of Incero Dallas to china is not good as west coast location, so the download speed is good as it should be.
    I do speed test almost everyday, didn't notice a routing issue, maybe the reports are from other ISP users, chinaunicom etc.

    Off topic, sometimes high latency is a good thing, so you won't be packed by huge amount of customers. From the reviews and trends I saw, one provider in seattle would soon have a headache of too many customers.

    Thanked by 1Maounique
  • MaouniqueMaounique Host Rep, Veteran
    edited May 2014

    Seems fine now, still have no idea why this happened, thank you for help :)

    Update, there was an issue with manual updates that were not pushed through to Nlayer. We are in contact with Incero to see how to prevent this in the future.

Sign In or Register to comment.