Announcement

Collapse
No announcement yet.

vbulletin.org DOWN

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

  • #61
    Traceroute from another server:

    traceroute to vbulletin.org (205.214.66.221), 30 hops max, 38 byte packets
    1 216.46.192.1 (216.46.192.1) 0.905 ms 3.925 ms 6.373 ms
    2 fe0-0-1.rtr1.grr.pathwaynet.com (216.46.200.71) 5.194 ms 2.474 ms 0.715 ms
    3 s0-0-1.ar2.DET1.gblx.net (208.48.23.241) 12.493 ms 12.228 ms 11.576 ms
    4 pos2-2-155M.cr1.CLE1.gblx.net (64.212.107.218) 26.285 ms 26.303 ms 26.179 ms
    5 pos1-0-622M.cr1.WDC2.gblx.net (208.178.174.118) 40.275 ms 37.481 ms 49.292 ms
    6 so1-2-0-2488M.ar1.DCA3.gblx.net (64.214.65.141) 38.713 ms 38.574 ms 38.580 ms
    7 peer-01.ge-2-2-0-0.asbn.twtelecom.net (66.192.252.209) 38.643 ms 38.546 ms 38.328 ms
    8 core-01-so-2-2-0-0.nycl.twtelecom.net (66.192.240.17) 45.506 ms 46.212 ms 45.593 ms
    9 core-02-so-2-2-0-0.chcg.twtelecom.net (168.215.53.41) 67.228 ms 79.850 ms 67.190 ms
    10 core-02-so-1-0-0-0.dnvr.twtelecom.net (168.215.53.14) 98.784 ms 98.437 ms 98.561 ms
    11 sagg-01-rif-2.dnvr.twtelecom.net (66.192.245.94) 87.961 ms 87.615 ms 91.637 ms
    12 66-162-99-2.gen.twtelecom.net (66.162.99.2) 100.275 ms 100.455 ms 100.319 ms
    13 * * *
    14 * * *^C

    Comment


    • #62
      It looks like most people are having problems with TWTelecom... which is one of the three main providers to the datacenter vb.org is in

      I can't get to it either, even thouhg I'm seeming to go through AT&T, who are doing dandy.

      Being the only one left is Yipes. Anyone can't access vb.org and know their signal is sent via Yipes?

      Comment


      • #63
        those damn fisher price router's will screw ya every time
        MCSE, MVP, CCIE
        Microsoft Beta Team

        Comment


        • #64
          A day without vBulletin.org is...

          My ISP is RoadRunner (Time Warner)...

          Traceroute has started ...
          traceroute to www.vbulletin.org (205.214.66.221), 30 hops max, 40 byte packets
          4 srp1-0.milwwirtco-rtr1.wi.rr.com (24.160.225.1) 25.49 ms 20.936 ms 16.954 ms
          5 pop2-chi-p3-0.atdn.net (66.185.136.113) 22.166 ms 20.841 ms 34.755 ms
          6 twtc.atdn.net (66.185.132.102) 24.658 ms 21.706 ms 19.218 ms
          7 core-01-so-1-1-0-0.chcg.twtelecom.net (66.192.244.53) 19.392 ms 21.415 ms 24.141 ms
          8 core-02-so-1-0-0-0.dnvr.twtelecom.net (168.215.53.14) 93.259 ms 54.296 ms 51.318 ms
          9 sagg-01-rif-2.dnvr.twtelecom.net (66.192.245.94) 54.343 ms 52.569 ms 52.386 ms
          10 66-162-99-2.gen.twtelecom.net (66.162.99.2) 39.617 ms 102.276 ms 46.87 ms
          11 * * *

          you get the picture...

          30 * * *
          http://www.wdca.org/wdca.ico

          Comment


          • #65
            double

            almost 2 days and I still need to go on the site

            Comment


            • #66
              Just a quick question, could this be the reason why the site is not working for us. I thought both sites were on same servers. Should they have the same nameservers?

              vBulletin.com whois

              Registrant:
              Jelsoft Enterprises Limited (VBULLETIN2-DOM)
              Tagra
              Ascot, Berkshire SL5 8RF
              UK

              Domain Name: VBULLETIN.COM

              Administrative Contact, Technical Contact:
              Jelsoft Enterprises Limited (22425524O) [email protected]
              Jelsoft Enterprises Limited
              Tagra
              Ascot, Berkshire SL5 8RF
              UK

              Domain servers in listed order:

              NS1.JELSOFT.COM 205.214.66.216
              NS2.JELSOFT.COM 205.214.66.217

              vBulletin.org whois:

              Registrant:
              Chris Lambert
              43 Rosewood Lane
              Cumberland, RI 02864-3344
              US

              Registrar: DOTSTER
              Domain Name: VBULLETIN.ORG
              Last Updated on: 30-APR-03

              Administrative, Technical Contact:
              Lambert, Chris [email protected]
              43 Rosewood Lane
              Cumberland, RI 02864-334
              US
              401-743-2786


              Domain servers in listed order:
              NS2.DN.NET
              NS3.DN.NET
              NS1.DN.NET

              End of Whois Information

              Comment


              • #67
                They are on the same server but as you noted they use different nameservers. This is why I think the problem is DNS related.

                In the past it used to be strongly suggested that you use a secondary nameserver that is on a different network from your primary server. Unfortunately hardly anyone does this anymore.
                Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
                Change CKEditor Colors to Match Style (for 4.1.4 and above)

                Steve Machol Photography


                Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


                Comment


                • #68
                  Question is, why would the nameservers been changed?

                  Comment


                  • #69
                    here is mine

                    Code:
                    [[email protected] root]# traceroute vbulletin.org
                    traceroute to vbulletin.org (205.214.66.221), 30 hops max, 38 byte packets
                     1  64.46.100.110 (64.46.100.110)  0.733 ms  0.525 ms  0.495 ms
                     2  host.onoc.net (198.31.192.1)  2.425 ms  2.019 ms  0.983 ms
                     3  s5-0-115.tamqfl1-cr8.bbnplanet.net (4.24.136.189)  3.233 ms  4.439 ms  4.697 ms
                     4  p3-2.tamqfl1-br2.bbnplanet.net (4.24.10.229)  4.415 ms  4.038 ms  3.783 ms
                     5  p1-0.tamqfl1-br1.bbnplanet.net (4.24.7.157)  3.508 ms  4.468 ms  5.065 ms
                     6  so-4-1-0.atlnga1-br2.bbnplanet.net (4.24.6.73)  14.948 ms  17.871 ms  15.029 ms
                     7  p2-0.iplvin1-br1.bbnplanet.net (4.0.3.122)  25.389 ms  26.173 ms  25.111 ms
                     8  so-6-0-0.chcgil2-br1.bbnplanet.net (4.24.9.57)  28.919 ms  29.921 ms  31.568 ms
                     9  so-7-0-0.chcgil2-br2.bbnplanet.net (4.24.5.218)  28.935 ms  30.105 ms  28.570 ms
                    10  p4-0.dnvtco1-br2.bbnplanet.net (4.24.9.62)  56.619 ms  58.350 ms  60.542 ms
                    11  p15-0.dnvtco1-br1.bbnplanet.net (4.24.11.37)  57.372 ms  56.838 ms  57.039 ms
                    12  p1-0.dnvtco1-cr1.bbnplanet.net (4.24.11.22)  57.280 ms  56.706 ms  59.197 ms
                    13  gigabitethernet0.yipes9.bbnplanet.net (4.25.24.62)  61.151 ms  55.899 ms  57.070 ms
                    14  66.54.149.66 (66.54.149.66)  57.123 ms  56.433 ms  56.410 ms
                    15  * *
                    makde sure the ISp doesn't have vb.org's Ip goign to null
                    Carlos Rego
                    LinuxCult

                    Comment


                    • #70
                      It's up and fine for me, I guess I'm one of the lucky ones.

                      Comment


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

                        1 26 ms 29 ms 26 ms 61.3.249.3
                        2 22 ms 22 ms 22 ms 61.3.249.4
                        3 25 ms 38 ms 23 ms 61.1.192.30
                        4 23 ms 208 ms 23 ms 203.199.223.70
                        5 26 ms 26 ms 23 ms giga-core-gw1-6.91.chennai.vsnl.com [202.54.6
                        ]
                        6 36 ms 43 ms 35 ms ekm-chn-atm-pvc2.Bbone.vsnl.net.in [202.54.2.
                        ]
                        7 433 ms 429 ms 382 ms 12.124.58.133
                        8 389 ms 398 ms 382 ms gbr6-p80.attga.ip.att.net [12.123.21.78]
                        9 389 ms 403 ms 388 ms tbr2-p013601.attga.ip.att.net [12.122.12.45]
                        10 409 ms 408 ms 408 ms tbr1-p012402.dlstx.ip.att.net [12.122.10.73]
                        11 406 ms 406 ms 407 ms tbr2-p013601.dlstx.ip.att.net [12.122.9.162]
                        12 444 ms 436 ms 436 ms gbr4-p50.dvmco.ip.att.net [12.122.2.102]
                        13 437 ms 436 ms 437 ms gbr2-p100.dvmco.ip.att.net [12.122.5.30]
                        14 437 ms 436 ms 436 ms gar2-p370.dvmco.ip.att.net [12.123.36.141]
                        15 437 ms 440 ms 444 ms 12.124.158.110
                        16 * * * Request timed out.
                        17 * * * Request timed out.

                        Comment


                        • #72
                          Time Warner

                          Time Warner (I guess its "Bright House" now) strikes again.

                          My high-speed connection is through TW, and it has been really bad lately. Should clear up soon, I hope!

                          -Brett

                          Comment


                          • #73
                            Well I have found a some what good proxy server to use. For those of you that need to connect via proxy server try this address:

                            193.188.97.152:80
                            194.72.9.37:8080
                            66.119.34.38:80
                            62.81.33.25:80

                            Let me know if it works ok for all, I am going to find a few more so that you guys can get your work done or what ever. Since this is a DNS issue for the looks of it, I would suggest doing this as quick as you can before the something else happens until the issue is fixed.

                            Hope this helps

                            CodeBlu
                            Last edited by codeblu; Thu 8 May '03, 9:32pm.

                            Comment


                            • #74
                              Proxy servers a good band-aid

                              I plugged in 194.72.9.37 on 8080, and have vbulletin.org!!!!!

                              Thanks,
                              Brett

                              Originally posted by codeblu
                              Well I have found a some what good proxy server to use. For those of you that need to connect via proxy server try this address:

                              193.188.97.152:80
                              194.72.9.37:8080
                              66.119.34.38:80
                              62.81.33.25:80

                              Let me know if it works ok for all, I am going to find a few more so that you guys can get your work done or what ever. Since this is a DNS issue for the looks of it, I would suggest doing this as quick as you can before the something else happens until the issue is fixed.

                              Hope this helps

                              CodeBlu

                              Comment


                              • #75
                                I still get, "The page cannot be displayed"

                                Robert - Music is my caffeine!

                                Comment

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