All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Delimiter network questions?
I'm looking for a smallish dedi in the USA for personal CDN use, and Delimiter's 16gb ram deal looks perfect. As it's a CDN I would need good networking to the UK and USA, Asia and Eastern Europe are already covered! Is the ping time to the UK for Delimiter decent? Do they have many dropouts on the network? Has anyone had any big issues with slow speed or high ping times? My script drops servers out that do not respond to ping for more than a minute, or if the response time gets too high.
Also I know this is a question I should probably ask Sales, but what's their policy on DDoS attacks? If there is an attack on one of the IP's, will the other IP's and IPv6 still be up or do they basicly unplug your server?
- Are you happy with DelimiterVPS's network?41 votes
- Yes! :)53.66%
- No! :(46.34%
Comments
As I somehow can't edit my post, support/hardware quality is not an issue here. I can always move provider if there are any issues.
A better way to do this would be to ask for traceroutes from Delimiter (Yomura) to some locations you will want to deliver content to.
DDOS its simple - the network port gets shutdown and the IPs blackholed. There is no DDOS mitigation included in any of Delimiter's budget products.
Sounds like fun!
Delimiter Atlanta -> BT DSL (London) - 98.7ms
Its pretty decent, can always get someone with a box to do some traceroutes for you.
I like it!
It's pretty good for the price. Congestion is definitely noticeable during peak hours though.
@FizzyJoe908 - Congestion?? Can you give me some more information on that. We see no congestion anywhere on the network in Atlanta (I am assuming you are referring to Atlanta)
Is their IPv6 still routed through HE's POP in Miami? That was the only reason I canceled my server with them since I mainly use IPv6 and going from Colorado to Florida to Atlanta made it hard to use on a daily basis.
@Kujoe - we've always had native IPv6, but to get to HE we had to use a tunnel as they had a spat with Zayo, Cogent and Level 3 which depeered them for IPv6. We are peering directly with HE in NY, LA, Chicago and Dallas; and also the dispute between HE and the others seems to have partially abated:
Level 3 and XO now carry HE's IPv6 routes.
Whereas in New York we see the routes directly:
@MarkTurner I'd be happy to next time it is brought to my attention.
@fizzyjoe908 - thanks just PM or email me (my email is on my wall)
Make sure that they will not mark your order as fraud,
Otherwise forget your first pay & server.
So basically unplugged server? Why not just nullroute/blackhole that single IP that's affected?
@nexmark - unplugging is fast, effective, and cheap.
Also can corrupt data....
unplugging the network can corrupt data?
Probably if said data is half-way trough a transfer over the network
Unless you're running something that handles your data which requires a network connection to function.. Can't think of anything tho
@Corey - Not their problem, protecting the network is their top priority.
Besides if you get corrupted data every time the network blips, there is something wrong with your setup.
@Nexmark - not physically pulling a cable out the back because these are blade servers in the majority of cases. But shutting down the blade's port on the aggregate switch in the back of the blade chassis.
@Corey - It would only corrupt data if the customer had a ISCSI or DRDB root; and then given the level of traffic caused by the DDOS, it would have more than likely dropped that connection long before the switch port was shutdown.
Ping SoftLayer Singapore:
--- speedtest.sng01.softlayer.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5769ms
rtt min/avg/max/mdev = 224.298/224.323/224.386/0.547 ms
Trace to SoftLayer Singapore:
traceroute to speedtest.sng01.softlayer.com (119.81.28.170), 30 hops max, 60 byte packets
1 107.189.32.62 (107.189.32.62) 0.373 ms 0.435 ms 0.474 ms
2 te1-1-0d0.cir1.atlanta6-ga.us.xo.net (216.156.108.17) 0.312 ms 0.316 ms 0.316 ms
3 vb2000d1.rar3.atlanta-ga.us.xo.net (207.88.13.154) 57.910 ms 54.384 ms 54.380 ms
4 te-3-0-0.rar3.dallas-tx.us.xo.net (207.88.12.2) 55.177 ms 55.176 ms 55.174 ms
5 vb12.rar3.la-ca.us.xo.net (207.88.12.46) 56.989 ms 56.971 ms 56.972 ms
6 207.88.14.218.ptr.us.xo.net (207.88.14.218) 54.037 ms * *
7 216.156.64.86.ptr.us.xo.net (216.156.64.86) 54.104 ms 54.091 ms 54.027 ms
8 gi8-0-0.cr1.nrt1.asianetcom.net (202.147.0.121) 158.657 ms 158.662 ms 158.656 ms
9 ge3-1-0-0.gw3.nrt4.asianetcom.net (202.147.0.55) 158.975 ms 159.139 ms 159.122 ms
10 gi6-0-0.gw1.nrt4.asianetcom.net (202.147.0.229) 158.933 ms 158.942 ms 158.943 ms
11 xe-1-0-3-0.gw2.nrt4.asianetcom.net (202.147.0.237) 160.305 ms 160.338 ms 160.312 ms
12 SFL-0027.asianetcom.net (203.192.131.250) 154.486 ms 154.527 ms 154.478 ms
13 ae7.bbr01.eq01.tok01.networklayer.com (50.97.18.162) 149.174 ms 149.285 ms 149.255 ms
14 ae1.bbr01.eq01.sng02.networklayer.com (50.97.18.165) 229.767 ms 229.794 ms 223.558 ms
15 ae5.dar01.sr03.sng01.networklayer.com (50.97.18.197) 234.287 ms 234.272 ms ae5.dar02.sr03.sng01.networklayer.com (50.97.18.199) 240.499 ms
16 po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) 241.659 ms po1.fcr01.sr03.sng01.networklayer.com (174.133.118.131) 229.317 ms po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) 248.132 ms
17 speedtest.sng01.softlayer.com (119.81.28.170) 224.470 ms 231.466 ms 224.910 ms
Ping SoftLayer Amsterdam:
--- speedtest.ams01.softlayer.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5537ms
rtt min/avg/max/mdev = 106.389/107.146/109.320/1.084 ms
Trace to SoftLayer Amsterdam:
traceroute to speedtest.ams01.softlayer.com (159.253.132.18), 30 hops max, 60 byte packets
1 107.189.32.62 (107.189.32.62) 0.430 ms 0.469 ms 0.488 ms
2 te1-1-0d0.cir1.atlanta6-ga.us.xo.net (216.156.108.17) 0.302 ms 0.303 ms 0.313 ms
3 67.111.23.95.ptr.us.xo.net (67.111.23.95) 1.437 ms 1.489 ms 1.554 ms
4 ae-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.5.189) 100.996 ms 99.813 ms 100.058 ms
5 ae-8.r20.asbnva02.us.bb.gin.ntt.net (129.250.5.214) 19.825 ms * 24.035 ms
6 ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5) 44.614 ms * *
7 ae-2.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.145) 108.621 ms 108.311 ms *
8 ae-2.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.159) 97.459 ms ae-1.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.147) 101.270 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.159) 104.916 ms
9 81.20.69.178 (81.20.69.178) 107.002 ms ae11.bbr01.eq01.ams02.networklayer.com.64.20.81.in-addr.arpa (81.20.64.50) 97.626 ms 81.20.69.178 (81.20.69.178) 96.586 ms
10 ae6.dar02.sr01.ams01.networklayer.com (50.97.18.251) 97.652 ms 107.827 ms ae5.dar02.sr01.ams01.networklayer.com (50.97.18.239) 100.931 ms
11 * po1.fcr01.sr01.ams01.networklayer.com (159.253.158.131) 101.082 ms po2.fcr01.sr01.ams01.networklayer.com (159.253.158.133) 110.612 ms
12 speedtest.ams01.softlayer.com (159.253.132.18) 101.510 ms 95.822 ms 98.515 ms
Delimiter's connectivity to the UK gives the best throughput out of all US I've used.
I can normally get 40+mbps down at my home, whereas all the other providers I've used rarely break 25mbps.
Support is generally good, though I have had to bump the odd low priority after a day or two to get it acted on.
The only real issue I've encountered (that's been brought up in other threads) is that they don't email advanced notice of maintenance by default, which was a problem for me when they were moving the blades to a new enclosure requiring them to be powered down.
@DigitalDuke - this lack of directed notice (ie email into mailbox) was brought up on here about 6 weeks ago, I did feed that back to Delimiter's management. The result was the second maintenance window was emailed to customers twice once 10 days before and a second time about 48 hours before saying "don't forget"; in addition to the notice being placed in the Network Issues page also onto Twitter. I think they have found a balance on that now.
Delimiter's UK connectivity should be great, this is also critical for me as I am based in the UK and often have to deal with network issues at that site. I am currently on BT DSL at home so once we get the connectivity onto LINX later this month then it should help increase peering and connectivity in Europe.
Depending on which ISP you are with, will depend on how much this will impact you. BT at the moment is using Cogent for their US transit which is a mess, hopefully we can get them to offload in London at Linx and we'll backhaul to Atlanta.
Weird, on my BT routes to QP They go over level3 (I don't have a traceroute atm, as i'm in the states) and not cogent.
@AlexanderM - it depends which BT you are with. You/Quickpacket end up all over the place, right now its going to DECIX in Frankfurt onto WVFibre/BroadbandOne then they are carrying it Amsterdam->New York->Atlanta.
BT Wholesale have it going via Cogent down to Atlanta, there is no Level3 in there. The AS path is 174 46261 25926
BroadbandOne/WVFibre barely do anything with Level3, its just their route of last resort. I've studied their routes in many locations.
The traffic to BT (AS2856) being handed off at LINX (which is what you just said was your goal for your network).
1 ash-ten3-1-atl-ten3-1.bboi.net (66.216.1.158) [MPLS: Label 46 Exp 0] 16 msec
2 nj-ten2-2-ash-ten1-5.bboi.net (66.216.1.162) [MPLS: Label 72 Exp 0] 20 msec
3 ny60-ten1-4-nj-ten2-1.bboi.net (66.216.1.105) [MPLS: Label 162 Exp 0] 20 msec
4 lon-vl14-ny60-vl14.bboi.net (66.216.48.214) 96 msec
5 linx1.ukcore.bt.net (195.66.224.10) 96 msec
6 core1-te0-3-0-12.ealing.ukcore.bt.net (109.159.254.101) [AS 2856] 96 msec
7 acc1-10GigE-7-0-0.mr.21cn-ipp.bt.net (109.159.250.16) [AS 2856] 104 msec
8 109.159.250.69 [AS 2856] 104 msec
9 31.55.165.106 [AS 2856] 100 msec
10 31.55.165.184 [AS 2856] 112 msec
Seems good enough for me, I'll go for it. Here is my ping and traceroute from BT Infinity UK to the test ip above:
wtf vanilla
@qps - BT is not one network - BT wholesale goes via Cogent, BT DSL goes via Frankfurt (WVFibre), BT Infinity goes via Linx (WVFibre).
My comment was the route out of the UK, not into the UK. Into the UK you go via WVFibre or Cogent depending on the BT network.