vbulletin.org DOWN

[boro_boy]

why is vbulletin.org down?

[YCrowley]

fine for me

[nuno]

Yeah, looks like vBulletin.org is 'down', I can't access either, I'll try later on.

[Steve Machol]

It works for me too. It's not a server issue because it's on the same server as this forum.

[Steve Machol]

It appears to be a routing issue that only affects certain users. Do a traceroute to vbulletin.org and post the results.

[codeblu]

Down for me here too.

CodeBlu

[filburt1]

It appears to be a routing issue that only affects certain users. Do a traceroute to vbulletin.org and post the results.

It was dead for me at school, too. Home traceroute:

  3    15 ms    13 ms    14 ms  172.30.13.17
  4    14 ms    16 ms    20 ms  172.30.13.59
  5    15 ms    20 ms    14 ms  68.54.81.2
  6    34 ms    21 ms    11 ms  sl-gw28-rly-8-0.sprintlink.net [144.223.48.45]
  7    13 ms    52 ms    20 ms  sl-bb24-rly-8-0.sprintlink.net [144.232.7.133]
  8    12 ms    27 ms    48 ms  sl-bb25-rly-10-0.sprintlink.net [144.232.14.150]
  9    15 ms    15 ms    14 ms  sl-bb26-rly-11-0.sprintlink.net [144.232.14.170]
 10    24 ms    52 ms    36 ms  sl-bb21-atl-10-0.sprintlink.net [144.232.8.126]
 11    55 ms    71 ms    50 ms  sl-bb20-fw-10-1.sprintlink.net [144.232.18.214]
 12    42 ms    53 ms    39 ms  sl-gw34-fw-8-0.sprintlink.net [144.232.11.10]
 13    57 ms    49 ms    46 ms  sl-inetconn-7-0.sprintlink.net [160.81.76.26]
 14    57 ms    41 ms    83 ms  core-01-ge-0-3-0-0.dlfw.twtelecom.net [168.215.54.81]
 15    61 ms    56 ms    80 ms  core-01-so-2-0-0-0.dnvr.twtelecom.net [168.215.53.70]
 16    61 ms    71 ms    61 ms  sagg-01-rif-1.dnvr.twtelecom.net [66.192.245.90]
 17    85 ms    81 ms    78 ms  66-162-99-2.gen.twtelecom.net [66.162.99.2]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20  ^C

[codeblu]

This is what I get:

1 15 ms <10 ms 62 ms 10.168.192.1
2 15 ms <10 ms <10 ms 12.244.107.17
3 16 ms 16 ms 15 ms 12.244.68.38
4 16 ms 63 ms 15 ms 12.244.72.234
5 47 ms 15 ms 16 ms gbr1-p50.cgcil.ip.at
6 16 ms 47 ms 15 ms tbr1-p013502.cgcil.i
7 31 ms 31 ms 31 ms 12.122.10.122
8 31 ms 31 ms 31 ms gbr1-p20.dvmco.ip.at
9 47 ms 31 ms 32 ms gar2-p360.dvmco.ip.a
10 31 ms 62 ms 63 ms 12.124.158.110
11 * * * Request timed out.
12 * * * Request timed out.
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.

[noppid]

Dies here for me too...

12 66-162-99-2.gen.twtelecom.net (66.162.99.2) 110.628 ms 108.647 ms 112.657 ms

[drumsy]

Also dead for me.

[Steve Machol]

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

[mafo0]

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 .

[N9ne]

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

[Steve Machol]

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

[mafo0]

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