Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


[Christmas Sale] 5420 $34 | 5520 $48 | E3 $58 | @ Seattle
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

[Christmas Sale] 5420 $34 | 5520 $48 | E3 $58 | @ Seattle

oneilonlineoneilonline Member, Host Rep

WattaServer, a brand of ONeilOnline is pleased to offer these dedicated servers out of our Seattle datacenter. Please contact our sales department via email or live chat with any questions prior to ordering.


What's included with your dedicated server:
Full root/administrator access
24 x 7 x 365 Server Monitoring
24 x 7 x 365 Hardware Replacement
24 x 7 x 365 Customer Support
1Gbps Uplink on a Private VLAN
IPMI / KVM/IP On Demand
DDoS Protection up to 10GB/sec – Automated Null Route at 10GB+/sec spike
SLA 99.9% Uptime in a Tier3+ Certified Datacenter


What's available with your dedicated server:
Windows Server, CentOS, Fedora, Ubuntu, Debian, and many other OS available!
CPanel and Webmin Control Panels Available!
Managed Server Services Available!


Dual Xeon L5420
16 GB DDR2 1333
500 GB SATA III 7200
1 Gbps Uplink
10 TB Bandwidth
4 IPv4s
DDoS Protection @ 10GB/sec
On Demand KVM/IP
Seattle, WA
Free Setup
@ $34.00 /month
[ORDER NOW]


Dual Xeon L5520
48 GB DDR3 1066
2 TB SATA III 7200
1 Gbps Uplink
10 TB Bandwidth
4 IPv4s
DDoS Protection @ 10GB/sec
On Demand KVM/IP
Seattle, WA
Free Setup
@ $48.00 /month
[ORDER NOW]


Xeon E3-1230v1
16 GB DDR3 1333
1 TB SATA III 7200
1 Gbps Uplink
10 TB Bandwidth
4 IPv4s
DDoS Protection @ 10GB/sec
On Demand KVM/IP
Seattle, WA
Free Setup
@ $58.00 /month
[ORDER NOW]


Network Info:
Network Details and Realtime Status can be found here

Seattle, WA Datacenter
Our Seattle datacenter has the best peering for Asia networks.
Test IPv4:
ping 216.244.77.220
ping 207.244.149.244
ping 162.245.239.130
Test File: 100MB.test / 1000MB.test

  • WattaServer is a brand of ONeilOnline, founded in 1994.
  • Read what our customers have to say! Customer Testimonials!
  • Network providers include Internap, Level 3, Telia, NTT, Zayo, CenturyLink, Seattle Internet Exchange out of Seattle.
  • Test IPs, test file links and more info can be found on our datacenter page.
  • Sorry, no IPv6 available at our Seattle datacenter.
  • Warez-related, Bulk Mail, and Spam-related activities are strictly forbidden. Please review our TOS and AUP prior to ordering.
  • We accept PayPal, Stripe, VISA and MasterCard payments. No Bitcoin.
  • Promotional offers cannot be combined with other promotional offers.

Thanks for your interest!

Thanked by 1TimboJones

Comments

  • Finally, a dedicated offer for Seattle that might temp me. Unfortunately, you did this after BF, and I've already got some idlers.

    Plus, without raid, there's an eventual bad times, and it is older hardware...

  • You can never have enough idlers.

  • root@sv39 ~ # wget http://162.245.239.130/100MB.test
    --2018-12-21 23:11:33-- http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’

    100MB.test 100%[===================>] 96.00M 405KB/s in 4m 0s

    2018-12-21 23:15:34 (409 KB/s) - ‘100MB.test’ saved [100663296/100663296]

    root@sv39 ~ #

  • oneilonlineoneilonline Member, Host Rep

    @eol said:
    root@sv39 ~ # wget http://162.245.239.130/100MB.test
    --2018-12-21 23:11:33-- http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’

    100MB.test 100%[===================>] 96.00M 405KB/s in 4m 0s

    2018-12-21 23:15:34 (409 KB/s) - ‘100MB.test’ saved [100663296/100663296]

    root@sv39 ~ #

    Where are you located!?! 4m is definitely not good or the norm.

  • Dedicated Hetzner box, Falkenstein/Germany.

  • oneilonlineoneilonline Member, Host Rep

    Ahhh that would explain it. We could always try better peering for the server if you were interested.

  • Well no, it's alright.
    I figured the speed would be kind of low but not that low.

  • King of resellers, nothing new, serverstadium deals.

  • Download speed seems pretty slow for me, given I'm relatively close to Seattle (San Francisco Bay Area):

    $ wget http://162.245.239.130/100MB.test
    --2018-12-21 17:40:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: '100MB.test.2’
    
    100MB.test.2                   100%[===================================================>]  96.00M  2.19MB/s    in 43s
    
    2018-12-21 17:41:27 (2.22 MB/s) - '100MB.test.2’ saved [100663296/100663296]
    
    $ ping 162.245.239.130
    PING 162.245.239.130 (162.245.239.130) 56(84) bytes of data.
    64 bytes from 162.245.239.130: icmp_seq=1 ttl=47 time=26.4 ms
    64 bytes from 162.245.239.130: icmp_seq=2 ttl=47 time=27.5 ms
    64 bytes from 162.245.239.130: icmp_seq=3 ttl=47 time=26.2 ms
    64 bytes from 162.245.239.130: icmp_seq=4 ttl=47 time=26.3 ms
    64 bytes from 162.245.239.130: icmp_seq=5 ttl=47 time=26.6 ms
    
    Thanked by 1eol
  • ~5 times my speed.
    I am jealous.

  • oneilonlineoneilonline Member, Host Rep

    @dedimark said:
    King of resellers, nothing new, serverstadium deals.

    We are all resellers here, in some form or fashion. We offer a lot more features, services, and better support than what server stadium offers. Thanks

  • oneilonlineoneilonline Member, Host Rep

    @Daniel15 said:
    Download speed seems pretty slow for me, given I'm relatively close to Seattle (San Francisco Bay Area):

    $ wget http://162.245.239.130/100MB.test
    --2018-12-21 17:40:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: '100MB.test.2’
    
    100MB.test.2                   100%[===================================================>]  96.00M  2.19MB/s    in 43s
    
    2018-12-21 17:41:27 (2.22 MB/s) - '100MB.test.2’ saved [100663296/100663296]
    
    $ ping 162.245.239.130
    PING 162.245.239.130 (162.245.239.130) 56(84) bytes of data.
    64 bytes from 162.245.239.130: icmp_seq=1 ttl=47 time=26.4 ms
    64 bytes from 162.245.239.130: icmp_seq=2 ttl=47 time=27.5 ms
    64 bytes from 162.245.239.130: icmp_seq=3 ttl=47 time=26.2 ms
    64 bytes from 162.245.239.130: icmp_seq=4 ttl=47 time=26.3 ms
    64 bytes from 162.245.239.130: icmp_seq=5 ttl=47 time=26.6 ms
    

    We actually were based in SF area for a few years, but many complained of the poor latency for the game servers out of SF and SJ. One of the reasons we moved. Sorry to disappoint.

  • @oneilonline said:

    @Daniel15 said:
    Download speed seems pretty slow for me, given I'm relatively close to Seattle (San Francisco Bay Area):

    $ wget http://162.245.239.130/100MB.test
    --2018-12-21 17:40:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: '100MB.test.2’
    
    100MB.test.2                   100%[===================================================>]  96.00M  2.19MB/s    in 43s
    
    2018-12-21 17:41:27 (2.22 MB/s) - '100MB.test.2’ saved [100663296/100663296]
    
    $ ping 162.245.239.130
    PING 162.245.239.130 (162.245.239.130) 56(84) bytes of data.
    64 bytes from 162.245.239.130: icmp_seq=1 ttl=47 time=26.4 ms
    64 bytes from 162.245.239.130: icmp_seq=2 ttl=47 time=27.5 ms
    64 bytes from 162.245.239.130: icmp_seq=3 ttl=47 time=26.2 ms
    64 bytes from 162.245.239.130: icmp_seq=4 ttl=47 time=26.3 ms
    64 bytes from 162.245.239.130: icmp_seq=5 ttl=47 time=26.6 ms
    

    We actually were based in SF area for a few years, but many complained of the poor latency for the game servers out of SF and SJ. One of the reasons we moved. Sorry to disappoint.

    Sure, but I'd think that I'd get speeds better than 2 MB/s from a server where the ping time is only 26ms, particularly since you're saying that it has a 1 Gb/s uplink. For comparison I get ~7 MB/s from BuyVM in Las Vegas.

  • oneilonlineoneilonline Member, Host Rep

    @Daniel15 said:

    @oneilonline said:

    @Daniel15 said:
    Download speed seems pretty slow for me, given I'm relatively close to Seattle (San Francisco Bay Area):

    $ wget http://162.245.239.130/100MB.test
    --2018-12-21 17:40:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: '100MB.test.2’
    
    100MB.test.2                   100%[===================================================>]  96.00M  2.19MB/s    in 43s
    
    2018-12-21 17:41:27 (2.22 MB/s) - '100MB.test.2’ saved [100663296/100663296]
    
    $ ping 162.245.239.130
    PING 162.245.239.130 (162.245.239.130) 56(84) bytes of data.
    64 bytes from 162.245.239.130: icmp_seq=1 ttl=47 time=26.4 ms
    64 bytes from 162.245.239.130: icmp_seq=2 ttl=47 time=27.5 ms
    64 bytes from 162.245.239.130: icmp_seq=3 ttl=47 time=26.2 ms
    64 bytes from 162.245.239.130: icmp_seq=4 ttl=47 time=26.3 ms
    64 bytes from 162.245.239.130: icmp_seq=5 ttl=47 time=26.6 ms
    

    We actually were based in SF area for a few years, but many complained of the poor latency for the game servers out of SF and SJ. One of the reasons we moved. Sorry to disappoint.

    Sure, but I'd think that I'd get speeds better than 2 MB/s from a server where the ping time is only 26ms, particularly since you're saying that it has a 1 Gb/s uplink. For comparison I get ~7 MB/s from BuyVM in Las Vegas.

    Yes, it depends on the peering, location, and server load. Closer to your location the less hops, the better latency and speeds.

  • starblazrstarblazr Member
    edited December 2018

    nah, I think your stuff kinda sucks.
    This is from my dedicated at NewContinuum in Chicago.

    :~$ wget http://162.245.239.130/100MB.test
    --2018-12-22 07:33:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
    
    100MB.test          100%[===================>]  96.00M  1011KB/s    in 96s
    
    2018-12-22 07:35:21 (1019 KB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    This if from my Dedicated in Philly

    :~$ wget http://162.245.239.130/100MB.test
    --2018-12-22 07:35:20--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test.1’
    
    100MB.test.1        100%[=====================>]  96.00M   961KB/s   in 1m 43s
    
    2018-12-22 07:37:04 (953 KB/s) - ‘100MB.test.1’ saved [100663296/100663296]
    

    And just for giggles, here is my Google Cloud instance in Kansas City.

    :~$  wget http://162.245.239.130/100MB.test
    --2018-12-22 13:40:15--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
    
    100MB.test          100%[=====================>]  96.00M  1.15MB/s   in 67s
    
    2018-12-22 13:41:23 (1.44 MB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    So, unless "better peering" is codeword for "next rack over" I don't know how much better it could be with three different network paths, including Google's premium bandwidth tier, one right next to United IX in Chicago, and one East coast.

    Thanked by 2eol muffin
  • Thats that wrapped up.

  • Seems like u need to be located inside the rack

    Thanked by 1eol
  • That probably won't help either...

  • what's their refund policy? anyone charging back? no way 1gb uplink is that slow.

  • oneilonlineoneilonline Member, Host Rep

    @starblazr said:
    nah, I think your stuff kinda sucks.
    This is from my dedicated at NewContinuum in Chicago.

    :~$ wget http://162.245.239.130/100MB.test
    --2018-12-22 07:33:44--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
            
    100MB.test          100%[===================>]  96.00M  1011KB/s    in 96s
            
    2018-12-22 07:35:21 (1019 KB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    This if from my Dedicated in Philly

    :~$ wget http://162.245.239.130/100MB.test
    --2018-12-22 07:35:20--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test.1’
                    
    100MB.test.1        100%[=====================>]  96.00M   961KB/s   in 1m 43s
                    
    2018-12-22 07:37:04 (953 KB/s) - ‘100MB.test.1’ saved [100663296/100663296]
    

    And just for giggles, here is my Google Cloud instance in Kansas City.

    :~$  wget http://162.245.239.130/100MB.test
    --2018-12-22 13:40:15--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
      
    100MB.test          100%[=====================>]  96.00M  1.15MB/s   in 67s
        
    2018-12-22 13:41:23 (1.44 MB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    So, unless "better peering" is codeword for "next rack over" I don't know how much better it could be with three different network paths, including Google's premium bandwidth tier, one right next to United IX in Chicago, and one East coast.

    Yes, I agree, looks like something is going on with the server that is hosting the test download link. We would have to look into it. Thank you

  • Do I need 20 ips available? Do you offer the extras or limit to 5 only?

  • oneilonlineoneilonline Member, Host Rep

    Yes, you can request additional IPs. A signed IP justification form will be required for approval. We recommend this be completed prior to purchase, but you can also complete this after purchase.

  • Oh yea, this test file is kinda crappy.

    From Vancouver:

    B:\>wget http://162.245.239.130/100MB.test
    --2018-12-23 03:25:48--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: '100MB.test'
    
    100MB.test                               100%[============>]  96.00M  3.59MB/s    in 27s
    
    2018-12-23 03:26:15 (3.59 MB/s) - '100MB.test' saved [100663296/100663296]
    

    In comparison, here is test file result from ImpactVPS:

    wget http://sea.lg.subnetlabs.net/100mb.test
    --2018-12-23 03:45:50--  http://sea.lg.subnetlabs.net/100mb.test
    Resolving sea.lg.subnetlabs.net (sea.lg.subnetlabs.net)... 64.140.157.48
    Connecting to sea.lg.subnetlabs.net (sea.lg.subnetlabs.net)|64.140.157.48|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [text/plain]
    Saving to: '100mb.test.1'
    
    100mb.test.1                               100%[================>] 100.00M  9.07MB/s    in 11s
    
    2018-12-23 03:46:01 (8.93 MB/s) - '100mb.test.1' saved [104857600/104857600]
    

    Here is a test file result from Virmach Seattle from Vancouver:

    wget http://sea.lg.virmach.com/100MB.test
    --2018-12-23 03:51:35--  http://sea.lg.virmach.com/100MB.test
    Resolving sea.lg.virmach.com (sea.lg.virmach.com)... 104.140.22.36
    Connecting to sea.lg.virmach.com (sea.lg.virmach.com)|104.140.22.36|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100000000 (95M) [application/octet-stream]
    Saving to: '100MB.test.3'
    
    100MB.test.3                               100%[==============>]  95.37M  8.69MB/s    in 17s
    
    2018-12-23 03:51:52 (5.76 MB/s) - '100MB.test.3' saved [100000000/100000000]
    

    From Seattle impactvps:
    Initially, failed to download. Couldn't ping 162.245.239.130. I successfully ping the other two test IP's. I then am able to ping 162.245.239.130 and get the file:

    wget http://162.245.239.130/100MB.test
    --2018-12-23 03:27:58--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
    
    100MB.test                               100%[================>]  96.00M  51.0MB/s    in 1.9s
    
    2018-12-23 03:29:04 (51.0 MB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    From Seattle Virmach:

    wget http://162.245.239.130/100MB.test
    --2018-12-23 03:36:04--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
    
    100MB.test                               100%[=================>]  96.00M  50.8MB/s    in 1.9s
    
    2018-12-23 03:36:06 (50.8 MB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    So two other Seattle datacenters can't top half a gigabit. But at least we know they are not 100Mbps ports.

    From LA Virmach:

    wget http://162.245.239.130/100MB.test
    --2018-12-23 06:32:15--  http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test’
    
    100MB.test                               100%[=================>]  96.00M  1.95MB/s    in 46s
    
    2018-12-23 06:33:03 (2.07 MB/s) - ‘100MB.test’ saved [100663296/100663296]
    

    That LA Virmach number is garbage for 27ms ping time. I have over 42ms ping from Vancouver to LA and speedtests are above 80Mbps, so less than 20Mbps from Seattle to LA is garbage.

    Here are what ImpactVPS and Virmach from Seattle to Vancouver does for a speedtest in comparison:

    # ./speedtest-cli --server 4243
    Retrieving speedtest.net configuration...
    Testing from Subnet Labs LLC (172.110.YY.X)...
    Retrieving speedtest.net server list...
    Retrieving information for the selected server...
    Hosted by Shaw Communications (Vancouver, BC) [2389.94 km]: 6.323 ms
    Testing download speed.........................................
    Download: 2254.67 Mbit/s
    Testing upload speed................................................
    Upload: 1205.65 Mbit/s
    
    
    # ./speedtest-cli --server 4243
    Retrieving speedtest.net configuration...
    Testing from ColoCrossing (96.8.YY.x)...
    Retrieving speedtest.net server list...
    Retrieving information for the selected server...
    Hosted by Shaw Communications (Vancouver, BC) [3433.67 km]: 180.226 ms
    Testing download speed.........................................
    Download: 749.30 Mbit/s
    Testing upload speed.......................................................
    Upload: 532.09 Mbit/s
    
    Thanked by 1eol
  • oneilonlineoneilonline Member, Host Rep
    edited January 2019

    wget http://162.245.239.130/100MB.test
    --2019-01-14 08:37:54-- http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test.4’

    100MB.test.4 100%[==========================================================>] 96.00M 299MB/s in 0.3s

    2019-01-14 08:37:55 (299 MB/s) - ‘100MB.test.4’ saved [100663296/100663296]

    This thread can be closed.

  • eoleol Member
    edited January 2019

    root@sv39 ~ # wget -O /dev/null http://162.245.239.130/100MB.test
    --2019-01-14 17:45:09-- http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘/dev/null’

    /dev/null 100%[===================>] 96.00M 421KB/s in 3m 58s

    2019-01-14 17:49:08 (413 KB/s) - ‘/dev/null’ saved [100663296/100663296]

    root@sv39 ~ #

    EDIT2:
    Seems to be capped at 420.

  • @oneilonline said:
    wget http://162.245.239.130/100MB.test
    --2019-01-14 08:37:54-- http://162.245.239.130/100MB.test
    Connecting to 162.245.239.130:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100663296 (96M)
    Saving to: ‘100MB.test.4’

    100MB.test.4 100%[==========================================================>] 96.00M 299MB/s in 0.3s

    2019-01-14 08:37:55 (299 MB/s) - ‘100MB.test.4’ saved [100663296/100663296]

    This thread can be closed.

    Are you testing from the same server?

    Thanked by 1eol
  • oneilonlineoneilonline Member, Host Rep

    @TimboJones said: Are you testing from the same server?

    LOL no, from our office to the Seattle datacenter, same city.

  • @oneilonline said:

    @TimboJones said: Are you testing from the same server?

    LOL no, from our office to the Seattle datacenter, same city.

    Test from somewhere else. Everyone here is reporting really shitty numbers.

    Thanked by 1uptime
  • Just connect it to 127.0.0.1 mate

    Thanked by 2uptime eol
Sign In or Register to comment.