Announcement

Collapse
No announcement yet.

vbulletin.org DOWN

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

  • #91
    Day 2...... no access from central ohio.....

    /me cries

    Comment


    • #92
      Originally posted by vB-Host.com
      I would be happy to give you a ns2 or even an ns3 for free for all the vB domains.. Hopefully it would stop things like this in the future happening.

      Can anyone reach either domain or is this global? I'm wondering if some lamer hacker got pissed at vb.org and got a bunch of buddies together and DoSed it forcing the ISP to null route the IP.. It's been over 24 hours now with no routing... thats insane...
      Here is my route from New York:

      1 <10 ms <10 ms <10 ms 10.0.0.4
      2 <10 ms <10 ms <10 ms ros75-145.optonline.net [167.206.75.145]
      3 <10 ms 10 ms <10 ms lyn92-21.optonline.net [167.206.92.21]
      4 <10 ms 10 ms 10 ms 167.206.15.9
      5 <10 ms 10 ms 10 ms r2-srp1-0.cr.hcvlny.cv.net [167.206.12.67]
      6 <10 ms 10 ms 10 ms r2-srp5-0.cr.hcvlny.cv.net [167.206.12.18]
      7 <10 ms 10 ms 10 ms r2-srp1-0.wan.hcvlny.cv.net [167.206.12.99]
      8 <10 ms 10 ms 10 ms r2-srp1-0.wan.prnynj.cv.net [167.206.12.115]
      9 10 ms 10 ms 10 ms r1-pos3-0.in.asbnva16.cv.net [167.206.8.254]
      10 10 ms 20 ms 10 ms peer-01-ge-2-2-1-0.asbn.twtelecom.net [66.192.25
      .193]
      11 20 ms 20 ms 30 ms core-01-so-2-2-0-0.nycl.twtelecom.net [66.192.24
      .17]
      12 40 ms 51 ms 40 ms core-02-so-2-2-0-0.chcg.twtelecom.net [168.215.5
      .41]
      13 70 ms 80 ms 80 ms core-02-so-1-0-0-0.dnvr.twtelecom.net [168.215.5
      .14]
      14 60 ms 60 ms 70 ms sagg-01-rif-2.dnvr.twtelecom.net [66.192.245.94]
      15 60 ms 61 ms 70 ms 66-162-99-2.gen.twtelecom.net [66.162.99.2]
      16 * * * Request timed out.
      17 * * * Request timed out.
      18 * * * Request timed out.

      Comment


      • #93
        Nothing from the host admin???
        My open eyes see everything, and you see nothing. . .
        That forum

        Comment


        • #94
          I'd guess that VB Team is trying to resolve this first before going to the host. VO's support prices for dedicated servers are not too nice ($35 for 30 mins, i think?).

          I would have however personally filled out a hlep desk ticket and perhaps even filled out the pager form.

          Comment


          • #95
            Originally posted by okrogius
            I'd guess that VB Team is trying to resolve this first before going to the host. VO's support prices for dedicated servers are not too nice ($35 for 30 mins, i think?).

            I would have however personally filled out a hlep desk ticket and perhaps even filled out the pager form.
            Well, since hte problem is network related, there isn't much they can do...
            My open eyes see everything, and you see nothing. . .
            That forum

            Comment


            • #96
              thank you for the proxies
              they are working well

              Comment


              • #97
                Never mind vBulletin.org going down... but what happened to vBulletinTemplates.com ?!?!?!
                Everytime i go on it, it says the server can't be found! Or is it just my laptop being annoying?!

                Comment


                • #98
                  Still down here for me, very much so:

                  1 * * * Request timed out.
                  2 8 ms 6 ms 8 ms bris-uBR-ca3-0-gw.chartertn.net [24.158.96.129]
                  3 8 ms 8 ms 6 ms TN-TRICTY-GS12-1.chartertn.net [24.158.96.228]
                  4 31 ms 22 ms 21 ms 12.124.59.113
                  5 23 ms 23 ms 21 ms gbr2-p70.attga.ip.att.net [12.123.21.6]
                  6 23 ms 23 ms 24 ms tbr2-p013602.attga.ip.att.net [12.122.12.37]
                  7 36 ms 37 ms 38 ms gbr3-p10.dlstx.ip.att.net [12.122.3.37]
                  8 36 ms 37 ms 41 ms tbr2-p013601.dlstx.ip.att.net [12.122.9.162]
                  9 58 ms 56 ms 58 ms gbr4-p50.dvmco.ip.att.net [12.122.2.102]
                  10 57 ms 56 ms 56 ms gbr2-p100.dvmco.ip.att.net [12.122.5.30]
                  11 58 ms 57 ms 56 ms gar2-p370.dvmco.ip.att.net [12.123.36.141]
                  12 84 ms 59 ms 58 ms 12.124.158.110
                  13 * * * Request timed out.
                  14 * * * Request timed out.
                  15 * * * Request timed out.
                  16 * * * Request timed out.
                  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 * * * 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.

                  Comment


                  • #99
                    Originally posted by Poggyuk
                    Never mind vBulletin.org going down... but what happened to vBulletinTemplates.com ?!?!?!
                    Everytime i go on it, it says the server can't be found! Or is it just my laptop being annoying?!
                    same problem as vb.org has.

                    try to use a proxy
                    The price of freedom is eternal vigilance!
                    - Thomas Jefferson

                    Comment


                    • Not likely a DNS issue

                      I highly doubt it is a dns issue. If the traceroute resolves the domain to an ip address, then the dns is working properly. It is not a web server issue. If the traceroute for everybody seems to dies int he same place, it is most lilely that place causing the problem.

                      I am getting the same problem as everybody else. Both from my office (using ISWEST) and from home (using Pacific Bell). Both the traceroutes die in the same place. All the proxy servers people have posted do not work. All I get is "page cannot be displayed". I hope this is resolved soon.

                      My traceroute (since everybody else is doing it too)

                      traceroute to www.vbulletin.org (205.214.66.221), 30 hops max, 40 byte packets
                      1 ib1.ftel.net (66.254.64.22) 1.568 ms 1.675 ms 1.483 ms
                      2 atm3-0-36.border.agoura.iswest.net (207.178.188.165) 8.942 ms 3.528 ms 3.23 ms
                      3 core1-fastether0-0.agoura.iswest.net (207.178.128.1) 3.686 ms 3.577 ms 3.634 ms
                      4 s10-1-0.ar1.LAX1.gblx.net (207.218.173.201) 5.122 ms 5.917 ms 5.027 ms
                      5 pos2-0-155M.cr2.LAX1.gblx.net (206.132.112.117) 5.699 ms 4.895 ms 5.067 ms
                      6 so2-0-0-2488M.cr1.PAO2.gblx.net (208.51.224.210) 14.026 ms 15.309 ms 15.415 ms
                      7 so-5-0-0-2488M.br2.PAO2.gblx.net (208.51.224.142) 17.546 ms 16.881 ms 16.353 ms
                      8 66.192.252.21 (66.192.252.21) 14.963 ms 17.192 ms 22.583 ms
                      9 dist-01-so-3-2-0-0.okld.twtelecom.net (66.192.250.37) 15.96 ms 16.975 ms 16.361 ms
                      10 dist-01-so-0-0-0-0.mdso.twtelecom.net (168.215.55.78) 17.449 ms 18.581 ms 22.868 ms
                      11 core-01-so-1-0-0-0.dnvr.twtelecom.net (168.215.55.213) 81.334 ms 82.14 ms 81.936 ms
                      12 sagg-01-rif-1.dnvr.twtelecom.net (66.192.245.90) 83.1 ms 84.19 ms 82.471 ms
                      13 66-162-99-2.gen.twtelecom.net (66.162.99.2) 48.509 ms 48.793 ms 51.12 ms
                      14 * * *
                      15 * * *
                      16 * * *
                      17 * * *
                      18 * * *
                      19 * * *
                      20 * * *
                      21 * * *
                      22 * * *
                      23 * * *
                      24 * * *
                      25 * * *
                      26 * * *
                      27 * * *
                      28 * * *
                      29 * * *
                      30 * * *

                      Comment


                      • It could still be a DNS issue at one or more of the root name servers. This would explain why some of us have no problem accessing vbulletin.org while others do.
                        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


                        • Yeah, I'm in NY and I can't get through to the site yesterday or today... Just timesout after twtelecom.net

                          -Jason
                          -Jason / WTF.com

                          "I think I've been quite clear that the new style will be in vB4." - Allen Lin / February 16, 2012

                          Comment


                          • Here is mine from GA (on comcast)
                            Microsoft Windows XP [Version 5.1.2600]
                            (C) Copyright 1985-2001 Microsoft Corp.
                            C:\Documents and Settings\Jimmy>tracert vbulletin.org
                            Tracing route to vbulletin.org [205.214.66.221]
                            over a maximum of 30 hops:
                            1 13 ms 11 ms 13 ms 10.171.144.1
                            2 12 ms 14 ms 35 ms 172.30.79.81
                            3 13 ms 12 ms 12 ms 172.30.79.122
                            4 21 ms 24 ms 21 ms 12.124.58.45
                            5 21 ms 19 ms 21 ms gbr6-p80.attga.ip.att.net [12.123.21.78]
                            6 22 ms 21 ms 21 ms tbr2-p013601.attga.ip.att.net [12.122.12.45]
                            7 35 ms 35 ms 35 ms gbr3-p10.dlstx.ip.att.net [12.122.3.37]
                            8 35 ms 35 ms 35 ms tbr2-p013601.dlstx.ip.att.net [12.122.9.162]
                            9 55 ms 55 ms 59 ms gbr4-p50.dvmco.ip.att.net [12.122.2.102]
                            10 58 ms * 54 ms gbr2-p100.dvmco.ip.att.net [12.122.5.30]
                            11 58 ms 56 ms 54 ms gar2-p370.dvmco.ip.att.net [12.123.36.141]
                            12 55 ms 59 ms 58 ms 12.124.158.110
                            13 * * * Request timed out.
                            14 * * * Request timed out.
                            15 * * * Request timed out.
                            16 * * * Request timed out.
                            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 * * * 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.

                            Comment


                            • Originally posted by Steve Machol
                              It could still be a DNS issue at one or more of the root name servers. This would explain why some of us have no problem accessing vbulletin.org while others do.
                              The site would still be accessible over IP in that case, which it isn't.
                              There's a network problem either right before the machine or in the machine itself (packets dropped when coming from a certain carrier?).

                              The real question is why hasn't it been fixed yet though?
                              This is a major outage at the ISP level (VO?) as far as I can see, and as such it should have a very high priority on their side.

                              The worst we had to wait was 6 - 8h when a UUNet router in Stockholm, .SE died.
                              It would seem this problem should be very trivial compared to replacing a smoking router...

                              tic toc.. tic toc..
                              My open eyes see everything, and you see nothing. . .
                              That forum

                              Comment


                              • I did a whois search and it said the domain name vbulletin.org is available which means they have to renew it.

                                Dark Shogun

                                Comment

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