The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#41
|
|||
|
|||
5 seconds...
Browser, Connection Speed? I have no other ideas.. |
#42
|
||||
|
||||
vb.org is really slow for me as well right now. vb.com is fine however. Trace route sucks...
Quote:
|
#43
|
|||
|
|||
Just to make you all feel better about how quick it is, heres my trace route and ping to here.
Quote:
Quote:
|
#44
|
|||
|
|||
Code:
W:\>ping vbulletin.org Pinging vbulletin.org [69.93.104.202] with 32 bytes of data: Reply from 69.93.104.202: bytes=32 time=42ms TTL=51 Reply from 69.93.104.202: bytes=32 time=44ms TTL=51 Reply from 69.93.104.202: bytes=32 time=41ms TTL=51 Reply from 69.93.104.202: bytes=32 time=40ms TTL=51 Ping statistics for 69.93.104.202: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 44ms, Average = 41ms Either that or they just really like people from Vegas and keep a fast lane open for us Just to compare - yahoo.com Reply from 66.94.234.13: bytes=32 time=34ms TTL=54 google.com Reply from 72.14.207.99: bytes=32 time=104ms TTL=238 sportsforum.ws Reply from 66.36.253.99: bytes=32 time=96ms TTL=52 www.whitehouse.gov Reply from 70.183.191.120: bytes=32 time=43ms TTL=55 apple.com Reply from 17.254.3.183: bytes=32 time=36ms TTL=236 vbulletin.de Reply from 80.237.154.40: bytes=32 time=207ms TTL=39 godaddy.com Reply from 64.202.188.201: bytes=32 time=43ms TTL=109 vbulletin.com Reply from 69.93.104.200: bytes=32 time=42ms TTL=51 mozilla.com Reply from 63.245.209.10: bytes=32 time=33ms TTL=244 ... looks pretty much the same to me. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|