Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

flagtel issue

Options
  • 26-10-2011 1:12pm
    #1
    Registered Users Posts: 352 ✭✭


    Is there an issue at the moment with eircom/flagtel. See tracert below to a random Australian site (netlogistics.com.au)


    Tracing route to netlogistics.com.au [122.201.80.80]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 35 ms 33 ms 33 ms b-ras1.rtd.sligo.eircom.net [159.134.155.25]
    3 42 ms 33 ms 33 ms ge-3-1-6.pe1.rtd.rsl-rtd.eircom.net [86.43.247.13]
    4 42 ms 36 ms 35 ms tenge-6-1-1.core2.bdt.core.eircom.net [86.43.253.9]
    5 43 ms 35 ms 36 ms lag-1.core1.bdt.core.eircom.net [86.43.252.1]
    6 54 ms 49 ms 50 ms tenge-1-2-1.pe1.thn.the-thn.eircom.net [86.43.253.82]
    7 49 ms 49 ms 49 ms ge7-1-0.corea.thn.london.eircom.net [86.43.244.194]
    8 56 ms 49 ms 49 ms peer1.ldn1.flagtel.com [195.66.224.146]
    9 365 ms 356 ms 356 ms so-1-0-0.0.pjr02.ldn001.flagtel.com [85.95.25.9]
    10 355 ms 362 ms 357 ms so-1-0-0.0.pjr01.nyc007.flagtel.com [85.95.25.2]
    11 353 ms 353 ms 353 ms so-1-1-0.0.pjr01.nyc005.flagtel.com [85.95.25.149]
    12 359 ms 368 ms 355 ms so-0-1-0.0.pjr02.lax002.flagtel.com [85.95.26.14]
    13 355 ms 356 ms 354 ms ge-1-0-0.0.pjr01.lax001.flagtel.com [85.95.25.245]
    14 212 ms 190 ms 190 ms ge-5-0-0.0.cjr02.lax002.flagtel.com [85.95.25.254]
    15 451 ms 316 ms 356 ms so-6-0-0.0.cjr04.hkg003.flagtel.com [62.216.128.77]
    16 355 ms 355 ms 357 ms 62.216.128.66
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 429 ms * * c-22349-3161-VAIES-204-515.cust.nxg.net.au [121.200.226.77]
    26 * * * Request timed out.
    27 425 ms * * 122.201.82.246
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.


Comments

  • Registered Users Posts: 352 ✭✭fergalfrog


    Please ignore - this issue now seems to have been resolved.


  • Closed Accounts Posts: 1,138 ✭✭✭eircom: Ant


    fergalfrog wrote: »
    Is there an issue at the moment with eircom/flagtel. See tracert below to a random Australian site (netlogistics.com.au)


    Tracing route to netlogistics.com.au [122.201.80.80]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 35 ms 33 ms 33 ms b-ras1.rtd.sligo.eircom.net [159.134.155.25]
    3 42 ms 33 ms 33 ms ge-3-1-6.pe1.rtd.rsl-rtd.eircom.net [86.43.247.13]
    4 42 ms 36 ms 35 ms tenge-6-1-1.core2.bdt.core.eircom.net [86.43.253.9]
    5 43 ms 35 ms 36 ms lag-1.core1.bdt.core.eircom.net [86.43.252.1]
    6 54 ms 49 ms 50 ms tenge-1-2-1.pe1.thn.the-thn.eircom.net [86.43.253.82]
    7 49 ms 49 ms 49 ms ge7-1-0.corea.thn.london.eircom.net [86.43.244.194]
    8 56 ms 49 ms 49 ms peer1.ldn1.flagtel.com [195.66.224.146]
    9 365 ms 356 ms 356 ms so-1-0-0.0.pjr02.ldn001.flagtel.com [85.95.25.9]
    10 355 ms 362 ms 357 ms so-1-0-0.0.pjr01.nyc007.flagtel.com [85.95.25.2]
    11 353 ms 353 ms 353 ms so-1-1-0.0.pjr01.nyc005.flagtel.com [85.95.25.149]
    12 359 ms 368 ms 355 ms so-0-1-0.0.pjr02.lax002.flagtel.com [85.95.26.14]
    13 355 ms 356 ms 354 ms ge-1-0-0.0.pjr01.lax001.flagtel.com [85.95.25.245]
    14 212 ms 190 ms 190 ms ge-5-0-0.0.cjr02.lax002.flagtel.com [85.95.25.254]
    15 451 ms 316 ms 356 ms so-6-0-0.0.cjr04.hkg003.flagtel.com [62.216.128.77]
    16 355 ms 355 ms 357 ms 62.216.128.66
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 429 ms * * c-22349-3161-VAIES-204-515.cust.nxg.net.au [121.200.226.77]
    26 * * * Request timed out.
    27 425 ms * * 122.201.82.246
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Hi fergalfrog,

    Thanks for post.

    I do see that your connection is dropping after hits fragtel, yet I don't see any blocks in place on our server before it leaves the eircom's routers. When you're doing a traceroute to netlogistics.com.au it is dropping after a flagtel.com router as you can see below. However I have done a traceroute to this site, and this is now fully completing.
    Initially I thought that some other Irish ISPs may also be having problems resolving the site as well. This would possibly point to a dns issue. However it does appear to be ok now, though the hops were pretty slow.


    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 35 ms 33 ms 33 ms b-ras1.rtd.sligo.eircom.net [159.134.155.25]
    3 42 ms 33 ms 33 ms ge-3-1-6.pe1.rtd.rsl-rtd.eircom.net [86.43.247.13]
    4 42 ms 36 ms 35 ms tenge-6-1-1.core2.bdt.core.eircom.net [86.43.253.9]
    5 43 ms 35 ms 36 ms lag-1.core1.bdt.core.eircom.net [86.43.252.1]
    6 54 ms 49 ms 50 ms tenge-1-2-1.pe1.thn.the-thn.eircom.net [86.43.253.82]
    7 49 ms 49 ms 49 ms ge7-1-0.corea.thn.london.eircom.net [86.43.244.194]
    8 56 ms 49 ms 49 ms peer1.ldn1.flagtel.com [195.66.224.146]
    9 365 ms 356 ms 356 ms so-1-0-0.0.pjr02.ldn001.flagtel.com [85.95.25.9]
    10 355 ms 362 ms 357 ms so-1-0-0.0.pjr01.nyc007.flagtel.com [85.95.25.2]
    11 353 ms 353 ms 353 ms so-1-1-0.0.pjr01.nyc005.flagtel.com [85.95.25.149]
    12 359 ms 368 ms 355 ms so-0-1-0.0.pjr02.lax002.flagtel.com [85.95.26.14]
    13 355 ms 356 ms 354 ms ge-1-0-0.0.pjr01.lax001.flagtel.com [85.95.25.245]
    14 212 ms 190 ms 190 ms ge-5-0-0.0.cjr02.lax002.flagtel.com [85.95.25.254]
    15 451 ms 316 ms 356 ms so-6-0-0.0.cjr04.hkg003.flagtel.com [62.216.128.77]
    16 355 ms 355 ms 357 ms 62.216.128.66



    C:\Documents and Settings>tracert netlogistics.com.au

    Tracing route to netlogistics.com.au [122.201.80.80]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 10.252.240.1
    2 1 ms <1 ms <1 ms 10.252.254.1
    3 19 ms 40 ms 45 ms 194.125.204.13
    4 20 ms 3 ms 4 ms 159.134.125.194
    5 12 ms 3 ms 3 ms tenge-4-1-1.core2.prp.core.eircom.net [86.43.252
    .141]
    6 25 ms 16 ms 16 ms tenge-2-2-1.pe1.the.the-thn.eircom.net [86.43.25
    3.110]
    7 15 ms 14 ms 15 ms ge7-1-0.corea.the.london.eircom.net [86.43.244.1
    90]
    8 15 ms 14 ms 15 ms ldn-b1-link.telia.net [213.248.95.1]
    9 15 ms 15 ms 15 ms ldn-bb2-link.telia.net [80.91.248.94]
    10 67 ms 15 ms 15 ms ldn-b5-link.telia.net [80.91.252.202]
    11 17 ms * 28 ms tata-ic-114869-ldn-b5.c.telia.net [213.248.74.2]

    12 15 ms 15 ms 17 ms if-8-704.tcore1.l78-london.as6453.net [80.231.13
    0.9]
    13 301 ms 303 ms 316 ms if-2-2.tcore2.l78-london.as6453.net [80.231.131.
    1]
    14 303 ms 300 ms 300 ms if-8-23.tcore1.nyy-newyork.as6453.net [80.231.13
    1.46]
    15 306 ms 301 ms 302 ms if-1-2.tcore1.pdi-paloalto.as6453.net [66.198.12
    7.5]
    16 153 ms 152 ms 152 ms if-6-0-0.mcore4.pdi-paloalto.as6453.net [66.198.
    127.74]
    17 302 ms 319 ms 465 ms if-2-0-1.core2.m3h-sydney.as6453.net [207.45.196
    .94]
    18 301 ms 301 ms 301 ms if-6-1.core1.m3h-sydney.as6453.net [216.6.109.11
    7]
    19 307 ms 307 ms 308 ms ix-6-0-204.core1.m3h-sydney.as6453.net [216.6.43
    .14]
    20 308 ms 307 ms 307 ms s-br1-sydn-1.pr3.sydn.nxg.net.au [203.176.106.8]

    21 312 ms 318 ms 313 ms c-22349-3161-vaies-204-515.cust.nxg.net.au [121.
    200.226.77]
    22 312 ms 313 ms 312 ms border1.equinix.syd.netlogistics.com.au [122.201
    .64.227]
    23 310 ms 316 ms 310 ms 122.201.82.246
    24 307 ms 312 ms 312 ms netlogistics.com.au [122.201.80.80]

    Trace complete.

    I will investigate this further with Technical Support, though for the moment I don't see an issue with our network with this site.

    Regards,
    Ant


  • Registered Users Posts: 352 ✭✭fergalfrog


    yes it seems to be resolved now.

    Strangely downforeveryoneorjustme.com was reporting the url as up but binarycanary.com was reporting it as down.

    I tested via a network in London and another in Germany and both reported the url being unaccessible.
    However via O2 on my phone the url and others were accessible.

    Hence this is not an issue confined to Eircom.

    Thanks for your help and hopefully we won't see this problem again.


Advertisement