Announcement

Collapse
No announcement yet.

vbulletin.org DOWN

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • crowfield99
    replied
    Not working for me either, really need to get on it so I can get the code for a hack I am about to pay for!

    Leave a comment:


  • Steve Machol
    replied
    Originally posted by okidoki
    So.. has anyone contacted the carrier for vb.org ?..
    Since vbulletin.com and vbulletin.org are on the same server I don't see this would make any difference. Nor do I see why the routing to one works but the other doesn't. 'Tis a mystery.

    Leave a comment:


  • rylin
    replied
    and on that note, i just compared a trace to vb.com and .org.
    it's the hop right before the end destination that fails for me.. so.. uh.. unless there's a bad nic, a dead port on a switch or a unplugged cable, it doesn't make sense to me :P

    Leave a comment:


  • rylin
    replied
    So.. has anyone contacted the carrier for vb.org ?..

    Leave a comment:


  • rylin
    replied
    Tracing route to vbulletin.org [205.214.66.221]
    over a maximum of 30 hops:
    1 <1 ms 1 ms <1 ms 192.168.1.1
    2 7 ms 8 ms 7 ms gw-n1fls31o887.telia.com [213.66.164.1]
    3 8 ms 8 ms 7 ms 10.0.111.1
    4 8 ms 8 ms 8 ms far-a12-feth3-1.se.telia.net [213.66.164.253]
    5 8 ms 8 ms 8 ms hy-d6-pos7-2.se.telia.net [212.181.203.149]
    6 8 ms 8 ms 8 ms hy-c2-pos3-1.se.telia.net [212.181.192.89]
    7 8 ms 8 ms 8 ms hy-c1-pos-14-1.se.telia.net [217.208.251.53]
    8 8 ms 8 ms 8 ms s-b4-pos10-0.telia.net [213.248.67.65]
    9 9 ms 8 ms 9 ms s-bb2-pos0-3-0.telia.net [213.248.66.13]
    10 16 ms 16 ms 16 ms kbn-bb2-pos0-0-0.telia.net [213.248.65.29]
    11 107 ms 108 ms 107 ms nyk-bb2-pos0-2.telia.net [213.248.64.46]
    12 127 ms 128 ms 127 ms chi-bb1-pos2-1-0.telia.net [213.248.80.122]
    13 172 ms 173 ms 172 ms sca-bb1-pos0-1-0.telia.net [213.248.80.34]
    14 173 ms 174 ms 174 ms att-sca-bb1.telia.net [213.248.86.62]
    15 174 ms 173 ms 173 ms tbr2-p013802.sffca.ip.att.net [12.122.11.229]
    16 197 ms 197 ms 197 ms gbr2-p50.ormfl.ip.att.net [12.122.12.130]
    17 195 ms 196 ms 195 ms gbr2-p20.dvmco.ip.att.net [12.122.5.26]
    18 196 ms 195 ms 195 ms gar2-p370.dvmco.ip.att.net [12.123.36.141]
    19 * 198 ms 199 ms 12.124.158.110
    20 * * * Request timed out.
    Stockholm, Sweden (TeliaNet).. no go..

    Leave a comment:


  • Floris
    replied
    http://www.vbulletin.com/forum/showt...threadid=71070


    maybe merge the threads ?

    Leave a comment:


  • Boofo
    replied
    Originally posted by amykhar
    Been down for me all day too. Tracert dies where everyone else's does. Did anyone in charge of the server contact their web host to let them know there is a problem?

    Amy
    To vbulletin.org with a max of 128 hops:

    1 0ms 0ms 0ms [192.168.0.1]
    2 13ms 11ms 12ms [10.16.48.1]
    3 24ms 12ms 12ms [12.215.13.225]
    4 24ms 28ms 22ms [12.215.6.22]
    5 22ms 23ms 24ms gbr5-p90.cgcil.ip.att.net [12.123.6.2]
    6 26ms 24ms 24ms tbr1-p013501.cgcil.ip.att.net [12.122.11.41]
    7 40ms 41ms 41ms [12.122.10.122]
    8 56ms 42ms 42ms gbr1-p20.dvmco.ip.att.net [12.122.5.22]
    9 40ms 48ms 44ms gar2-p360.dvmco.ip.att.net [12.123.36.137]
    10 Request Timed Out
    --------------------------------------------------------------------------------------

    Leave a comment:


  • amykhar
    replied
    Been down for me all day too. Tracert dies where everyone else's does. Did anyone in charge of the server contact their web host to let them know there is a problem?

    Amy

    Leave a comment:


  • boro_boy
    replied
    Originally posted by mafo0
    so then its really an isp's problem, not vb.org's, right?
    here is mine. And its still dead:

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\M C Yates>tracert vbulletin.org

    Tracing route to vbulletin.org [205.214.66.221]
    over a maximum of 30 hops:

    1 36 ms 17 ms 28 ms 10.142.63.254
    2 10 ms 24 ms 60 ms midd-t2cam1-b-v119.inet.ntl.com [213.106.238.221
    ]
    3 25 ms 10 ms 68 ms mid-t2core-b-ge-wan61.inet.ntl.com [213.106.237.
    161]
    4 18 ms 33 ms 21 ms ren-bb-b-so-220-0.inet.ntl.com [62.253.187.93]
    5 77 ms 27 ms 150 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

    6 34 ms 23 ms 20 ms man-bb-b-ge-221-0.inet.ntl.com [62.253.187.178]

    7 58 ms 23 ms 74 ms 213.206.159.245
    8 28 ms 40 ms 29 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]

    9 27 ms 23 ms * sl-bb22-lon-15-0.sprintlink.net [213.206.128.54]

    10 97 ms 114 ms 90 ms sl-bb20-nyc-2-0.sprintlink.net [144.232.9.163]
    11 97 ms 97 ms 96 ms sl-bb22-nyc-8-0.sprintlink.net [144.232.7.106]
    12 145 ms 128 ms 137 ms sl-bb21-chi-9-0.sprintlink.net [144.232.9.149]
    13 114 ms 114 ms 120 ms sl-gw32-chi-10-0.sprintlink.net [144.232.26.34]

    14 114 ms 149 ms 139 ms sl-timewarner-5-0.sprintlink.net [144.223.73.202
    ]
    15 112 ms 124 ms 112 ms core-01-ge-0-3-0-0.chcg.twtelecom.net [168.215.5
    4.29]
    16 192 ms 175 ms 150 ms core-02-so-1-0-0-0.dnvr.twtelecom.net [168.215.5
    3.14]
    17 141 ms 214 ms 176 ms sagg-01-rif-2.dnvr.twtelecom.net [66.192.245.94]

    18 147 ms 149 ms 149 ms 66-162-99-2.gen.twtelecom.net [66.162.99.2]
    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 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\Documents and Settings\M C Yates>

    Leave a comment:


  • mafo0
    replied
    so then its really an isp's problem, not vb.org's, right?

    Leave a comment:


  • Steve Machol
    replied
    I can connect from my home machine, but a traceroute from my server to vbulletin.org times out.

    Leave a comment:


  • N9ne
    replied
    Dead for me too. I get sprint and twtelecom in a tracert.

    Leave a comment:


  • mafo0
    replied
    1 <1 ms <1 ms <1 ms COMPAQP4.mshome.net [192.168.0.1]
    2 10 ms 10 ms 7 ms 10.72.144.1
    3 9 ms 9 ms 9 ms 172.30.100.209
    4 10 ms 7 ms 8 ms 172.30.100.250
    5 13 ms 31 ms 10 ms 68.48.0.162
    6 9 ms 9 ms 9 ms 12.126.168.9
    7 10 ms 9 ms 11 ms tbr1-p012201.wswdc.ip.att.net [12.123.9.74]
    8 50 ms 26 ms 13 ms tbr1-p012201.n54ny.ip.att.net [12.122.10.17]
    9 35 ms 33 ms 37 ms tbr1-p012101.cgcil.ip.att.net [12.122.10.2]
    10 51 ms 49 ms 49 ms 12.122.10.118
    11 87 ms 52 ms 52 ms gbr1-p20.dvmco.ip.att.net [12.122.5.22]
    12 51 ms 53 ms 79 ms gar2-p360.dvmco.ip.att.net [12.123.36.137]
    13 52 ms 54 ms 50 ms 12.124.158.110
    14 * * * Request timed out.

    It goes on in a list of time-outs after 14..... That first one in the list is me connecting through my lan .

    Leave a comment:


  • Steve Machol
    replied
    So far I've seen 4 out of 5 people reporting routing issues after twtelecom.net.

    Leave a comment:


  • drumsy
    replied
    Also dead for me.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X