amuck-landowner

How is vpsBoard performance in your location?

NodeBytes

Dedi Addict
@Damian - Could be because VPSBoard was down from the BuyVM network upgrade for a while so it doesn't have as much traffic right now.
 

karl

New Member
Traceroute from Sydney Australia, performance is much better now :)  

Code:
traceroute to vpsboard.com (108.162.194.157), 64 hops max
 1   192.168.0.1 (192.168.0.1) 0.865ms 0.726ms 0.625ms
 2   172.18.112.83 (172.18.112.83) 20.312ms 19.468ms 20.213ms
 3   172.18.65.42 (172.18.65.42) 19.468ms 19.374ms  172.18.93.202 (172.18.93.202) 19.718ms
 4   139.130.207.77 (139.130.207.77) 20.079ms 19.651ms 21.167ms
 5   203.50.11.94 (203.50.11.94) 20.977ms 19.828ms 19.599ms
 6   203.50.20.64 (203.50.20.64) 18.685ms 20.007ms 20.199ms
 7   139.130.94.34 (139.130.94.34) 19.434ms 19.433ms 19.192ms
 8   203.192.174.181 (203.192.174.181) 23.838ms 23.527ms 23.004ms
 9   202.147.55.82 (202.147.55.82) 21.057ms 55.886ms 20.041ms
 10   203.192.167.86 (203.192.167.86) 19.825ms 19.726ms 19.958ms
 11   108.162.194.157 (108.162.194.157) 21.785ms 19.851ms 19.639ms
 

D. Strout

Resident IPv6 Proponent
In terms of regular, user-noticeable performance, page loads are mostly OK, though adding posts is a PITA (see this post). Overall can't complain. But where it really gets weird is routing. I'm in New England and my ISP routes everything down the coast to NYC, then onward from there. Above.net is their main peer, which takes over in Boston, then in to New York, where it hands off to nLayer. nLayer takes it from New York to Newark (I think, see geolocation for 198.32.118.91 and 69.31.34.127, but the hostnames indicate NYC and Newark), where it hands off to Cloudflare at IP 108.162.195.157. That IP geolocates to San Francisco, which makes no sense considering the handoff and ping times (~30ms for me). I assume it's anycasted, and actually ends up at a server in the NYC metro area.

IPv6 routing is even more weird. I tunnel through a server in Montreal, which uses Tata. Tata takes the traffic to NYC, then to London, then hands off to Telia, which dumps it on Cloudflare's doorstep in Paris. Weirdness all around. Maybe I should see about forcing IPv4 for vpsBoard. Routing to another continent may be part of my problem, as I'm undoubtedly accessing VPSB over IPv6 with the above routing  <_<
 

drmike

100% Tier-1 Gogent
You and that IPV6 love @D. Strout :)

Strange though on the IPV4 routing also. 

I suspect the IPV4 is fine/correct.  Geolocation info just wrong (i.e. geolocated to Cloudflare HQ's?)

IPV6 handoff in Europe = FACEPALM.

Frankly, unsure who/what is totally to blame though. I suspect there is lots of this big error with Cloudflare's setup.  End users never pay any attention and just blame sites on being slow, but it is the outsourced mess meant to improve things.
 

Master Bo

Member
Not lightning fast, but not terribly slow, either. Acceptable.

Location: Novosibirsk, Russia, ISP: SibirTelecom.
 

bizzard

Active Member
Loads fine for me and is pretty usable. Here goes my traceroute from the southern tip of India, using service of Asianet right now.

Code:
traceroute to vpsboard.com (108.162.195.157), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  3.175 ms  3.354 ms  4.153 ms
 2  10.2.71.1 (10.2.71.1)  47.874 ms  52.351 ms  52.377 ms
 3  4.231.88.202.asianet.co.in (202.88.231.4)  53.950 ms  54.255 ms  53.556 ms
 4  illekm-static-203.200.136.33.vsnl.net.in (203.200.136.33)  55.261 ms illekm-static-203.200.136.46.vsnl.net.in (203.200.136.46)  55.182 ms  55.307 ms
 5  59.165.191.45.man-static.vsnl.net.in (59.165.191.45)  56.128 ms Vlan1331.icore1.HK2-HongKong.as6453.net (116.0.67.121)  166.067 ms 59.165.191.45.man-static.vsnl.net.in (59.165.191.45)  56.236 ms
 6  * * cloudflare3-10G.hkix.net (202.40.160.246)  122.256 ms
 7  108.162.195.157 (108.162.195.157)  120.819 ms  123.307 ms *
 

MannDude

Just a dude
vpsBoard Founder
Moderator
I've got to admit, I'm surprised by some of these results. Maybe it's just me then, but I get pretty slow/horrible speeds often. Lot of slow loading pages. Very slow posting.

Code:
traceroute to vpsboard.com (108.162.194.157), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  0.536 ms  0.753 ms  1.364 ms
 2  10.194.144.2 (10.194.144.2)  21.098 ms  21.563 ms  21.296 ms
 3  69.174.129.30 (69.174.129.30)  8.186 ms  7.754 ms  7.957 ms
 4  130.xe-8-0-1.er1.ord7.us.above.net (208.184.78.61)  12.781 ms  12.880 ms  12.969 ms
 5  equinix.xe-1-3-0.cr2.ord1.us.nlayer.net (206.223.119.61)  16.109 ms  15.887 ms  16.877 ms
 6  ae2-30g.ar1.ord1.us.nlayer.net (69.31.111.138)  20.559 ms  19.059 ms ae2-30g.ar2.ord1.us.nlayer.net (69.31.111.150)  16.403 ms
 7  as13335.xe-7-0-5.ar2.ord1.us.nlayer.net (69.31.105.34)  42.656 ms as13335.xe-8-0-3.ar1.ord1.us.nlayer.net (69.31.110.90)  43.433 ms  43.525 ms
 8  108.162.194.157 (108.162.194.157)  15.791 ms  15.449 ms  15.665 ms
 

Ivan

Active Member
Verified Provider
It hasn't been that great lately, below average performance, and yes, posting is a bit slow for the past week. 
 

MannDude

Just a dude
vpsBoard Founder
Moderator
Hmm... Thanks everyone for the updates. I'll see what I can to do to ensure performance remains fast and consistently stable.
 

mikho

Not to be taken seriously, ever!
The loading speed is very unreliable. Some times it's fast as lightning, other times it's slow as a elderly person in a wheelchair doing their weekly shopping.
 

clarity

Active Member
The board id crawling right now. I am guessing something is attacking it. It is pretty slow posting, and the pages aren't zipping by like they normally do.

Edit: It took 7 seconds from the time that I pressed Post for it to actually do it!
 
Last edited by a moderator:

ihatetonyy

New Member
Not fast, but fairly okay.


Code:
C:\Users\Me>tracert vpsboard.com


Tracing route to vpsboard.com [108.162.195.157]
over a maximum of 30 hops:


  1    <1 ms    <1 ms    <1 ms  ONE [192.168.0.1]
  2    37 ms    27 ms    30 ms  98.242.10.1
  3    11 ms    15 ms    12 ms  te-7-3-ur01.visalia.ca.ccal.comcast.net [68.87.201.41]
  4    15 ms    19 ms    19 ms  te-0-2-0-0-ar03.sacramento.ca.sacra.comcast.net [68.87.221.69]
  5    23 ms    25 ms    25 ms  pos-1-5-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.94.113]
  6    28 ms    23 ms    23 ms  pos-0-1-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.62]
  7    19 ms    28 ms    35 ms  173.167.57.138
  8    25 ms    29 ms    28 ms  as13335.xe-11-0-6.ar1.lax1.us.nlayer.net [69.31.125.106]
  9    20 ms    21 ms    22 ms  108.162.195.157
 
Top
amuck-landowner