Results 1 to 25 of 27
-
03-28-2012, 01:29 PM #1Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
references and experience with HostDime
Someone can tell me please if you have bad or good things about HostDime?.
Currently I have a server, and for 3 months, but I always had bad experiences. have poor connectivity, network crashes. support data center real slow.
if it is normal or how to do to have an efficient support it?
Please please do a ping and tracert from your country. And see what the possible problem. the data center and I have six hours on hold and no clear answer.
ping 184.171.250.130 -t
tracert 184.171.250.130Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 01:42 PM #2Junior Guru Wannabe
- Join Date
- Jul 2009
- Location
- Orlando, FL
- Posts
- 70
Hello Netandino,
I am sorry if you have had any issues as of late. I am reviewing tickets you have had opened now and will provide an update to you about them as soon as possible.| Alex Font | HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2001
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Cloud Clusters
| Data Centers in USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands
-
03-28-2012, 01:42 PM #3Web Hosting Evangelist
- Join Date
- Feb 2012
- Location
- Europe
- Posts
- 453
Looks fine from here. Maybe some connectivity issue between your ISP and HostDime? Have you tried to contact them?
.
Steadfast Networks - Chicago, IL
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 60 byte packets 2 ip77.208-100-32.static.steadfastdns.net (208.100.32.77) 9.055 ms 9.060 ms 9.047 ms 3 ip41.208-100-32.static.steadfastdns.net (208.100.32.41) 0.252 ms 0.268 ms 0.262 ms 4 xe-0-3-0-6.r06.chcgil09.us.bb.gin.ntt.net (128.242.179.21) 0.678 ms 0.861 ms 0.967 ms 5 xe-1.level3.chcgil09.us.bb.gin.ntt.net (129.250.8.78) 0.454 ms xe-8-0-0.edge4.Chicago3.level3.net (4.68.63.197) 0.448 ms 0.479 ms 6 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) 0.550 ms 5.745 ms 2.397 ms 7 ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193) 0.469 ms 0.477 ms 0.462 ms 8 ae-3-3.ebr2.Atlanta2.Level3.net (4.69.132.74) 18.965 ms 27.032 ms 19.296 ms 9 ae-1-100.ebr1.Atlanta2.Level3.net (4.69.132.33) 21.632 ms 22.334 ms 21.631 ms 10 ae-1-8.bar1.Orlando1.Level3.net (4.69.137.149) 27.548 ms 27.545 ms 27.222 ms 11 HostDime.com-10G-ethernet.core1.level3.net (67.30.140.2) 28.227 ms 27.914 ms 28.166 ms 12 server10.gnservername.net (184.171.250.130) 27.678 ms 27.960 ms 27.997 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 60 byte packets 2 ec0-61.agg04.sctn01.hostnoc.net (96.9.184.62) 15.297 ms 15.327 ms 15.329 ms 3 xe2-04.gwy03.sctn01.hostnoc.net (64.120.243.37) 61.601 ms 61.614 ms 61.621 ms 4 209.197.17.133 (209.197.17.133) 132.733 ms 132.847 ms 132.899 ms 5 209.197.17.129 (209.197.17.129) 6.461 ms 6.458 ms 6.439 ms 6 209.220.16.205.ptr.us.xo.net (209.220.16.205) 6.381 ms 6.325 ms te0-5-0-2.ccr21.jfk07.atlas.cogentco.com (38.122.110.129) 7.222 ms 7 te0-6-0-7.mpd21.jfk02.atlas.cogentco.com (154.54.80.181) 7.284 ms 206.111.13.66.ptr.us.xo.net (206.111.13.66) 25.973 ms 25.938 ms 8 vlan80.csw3.NewYork1.Level3.net (4.69.155.190) 25.926 ms te0-2-0-1.ccr21.jfk05.atlas.cogentco.com (154.54.46.250) 7.572 ms vlan80.csw3.NewYork1.Level3.net (4.69.155.190) 25.870 ms 9 level3.jfk05.atlas.cogentco.com (154.54.11.218) 34.509 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 30.374 ms Te-8-1.car2.NewYork1.Level3.net (4.68.111.45) 28.011 ms 10 vlan90.csw4.NewYork1.Level3.net (4.69.155.254) 32.051 ms ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 119.138 ms 118.272 ms 11 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 115.958 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 29.913 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 34.256 ms 12 ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 47.215 ms ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 119.487 ms ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 47.078 ms 13 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 118.766 ms 119.178 ms ae-1-8.bar1.Orlando1.Level3.net (4.69.137.149) 60.685 ms 14 HostDime.com-10G-ethernet.core1.level3.net (67.30.140.2) 61.503 ms ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 51.056 ms HostDime.com-10G-ethernet.core1.level3.net (67.30.140.2) 61.402 ms 15 server10.gnservername.net (184.171.250.130) 61.905 ms ae-1-8.bar1.Orlando1.Level3.net (4.69.137.149) 60.863 ms server10.gnservername.net (184.171.250.130) 61.633 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 40 byte packets 2 (173.245.86.17) 10.047 ms 10.037 ms 10.015 ms 3 v995.core1.sjc1.he.net (64.71.150.21) 0.437 ms 0.554 ms 0.526 ms 4 10gigabitethernet2-3.core1.pao1.he.net (72.52.92.113) 1.043 ms 1.018 ms 4.995 ms 5 10gigabitethernet1-1.core1.lax1.he.net (72.52.92.22) 9.128 ms 11.600 ms 8.989 ms 6 10gigabitethernet1-1.core1.phx1.he.net (72.52.92.250) 19.380 ms 19.475 ms 19.648 ms 7 10gigabitethernet1-3.core1.dal1.he.net (72.52.92.254) 51.829 ms 51.812 ms 51.812 ms 8 10gigabitethernet1-3.core1.mia1.he.net (184.105.222.30) 78.676 ms 78.640 ms 78.718 ms 9 dimenoc.nota-miami.net (198.32.125.68) 89.630 ms 87.395 ms 87.358 ms 10 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 86.731 ms 86.940 ms 87.216 ms 11 server10.gnservername.net (184.171.250.130) 87.099 ms 86.879 ms 86.863 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 60 byte packets 2 xe-2-0-0.car03.dllstx2.networklayer.com (67.18.7.89) 0.212 ms 0.199 ms 0.208 ms 3 po101.dsr01.dllstx2.networklayer.com (70.87.254.73) 0.499 ms 0.752 ms 0.803 ms 4 te4-4.dsr01.dllstx3.networklayer.com (70.87.255.117) 0.685 ms te2-1.dsr01.dllstx3.networklayer.com (70.87.255.65) 0.745 ms te4-4.dsr01.dllstx3.networklayer.com (70.87.255.117) 0.776 ms 5 * * * 6 ethernet12-1.ar6.dal2.gblx.net (64.213.54.253) 0.518 ms 0.488 ms 0.489 ms 7 ae11.scr2.DAL1.gblx.net (67.16.166.50) 0.612 ms ae11.scr1.DAL1.gblx.net (67.16.166.42) 0.893 ms ae11.scr2.DAL1.gblx.net (67.16.166.50) 0.945 ms 8 xe0-1-0-10G.scr4.MIA1.gblx.net (67.16.165.206) 30.222 ms ae2.scr3.MIA1.gblx.net (67.16.147.150) 64.293 ms 30.349 ms 9 lag7.ar4.MIA2.gblx.net (67.16.147.142) 34.226 ms lag8.AR4.MIA2.gblx.net (67.16.147.130) 30.261 ms 30.387 ms 10 HostDime.com-10xe.mia01.gblx.net (64.214.70.10) 37.977 ms 38.635 ms 37.970 ms 11 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 36.858 ms 36.749 ms 36.656 ms 12 server10.gnservername.net (184.171.250.130) 36.612 ms 35.946 ms 36.314 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 40 byte packets 2 68.233.224.121 (68.233.224.121) 0.985 ms 1.200 ms 2.277 ms 3 xe-8-0-0.bar1.Tampa1.Level3.net (4.53.172.1) 0.961 ms 1.169 ms 2.248 ms 4 ae-5-5.ebr1.Miami1.Level3.net (4.69.148.213) 18.285 ms 18.272 ms 19.406 ms 5 ae-1-100.ebr2.Miami1.Level3.net (4.69.151.254) 7.656 ms 7.649 ms 7.640 ms 6 ae-3-5.bar2.Orlando1.Level3.net (4.69.148.210) 11.376 ms 10.499 ms 11.625 ms 7 ae-0-11.bar1.Orlando1.Level3.net (4.69.137.145) 10.205 ms 10.897 ms 10.600 ms 8 HostDime.com-10G-ethernet.core1.level3.net (67.30.140.2) 117.065 ms 117.058 ms 118.226 ms 9 server10.gnservername.net (184.171.250.130) 10.549 ms 11.168 ms 11.161 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 40 byte packets 2 205.134.242.113 (205.134.242.113) 0.571 ms 0.661 ms 0.719 ms 3 gige-g3-16.core1.lax1.he.net (65.19.129.5) 6.333 ms 6.419 ms 6.465 ms 4 10gigabitethernet1-1.core1.phx1.he.net (72.52.92.250) 10.848 ms 10.974 ms 10.963 ms 5 10gigabitethernet1-3.core1.dal1.he.net (72.52.92.254) 41.487 ms 41.595 ms 41.585 ms 6 10gigabitethernet1-3.core1.mia1.he.net (184.105.222.30) 68.376 ms 68.449 ms 68.547 ms 7 dimenoc.nota-miami.net (198.32.125.68) 76.513 ms 76.771 ms 76.788 ms 8 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 86.213 ms 77.039 ms 77.672 ms 9 server10.gnservername.net (184.171.250.130) 77.241 ms 77.185 ms 77.158 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 40 byte packets 2 gw-cdlan-2.umusic.cdlan.net (217.171.46.253) 0.404 ms 0.465 ms 0.530 ms 3 212.73.241.129 (212.73.241.129) 0.210 ms 0.188 ms 0.153 ms 4 ae-0-11.bar1.Milan1.Level3.net (4.69.142.189) 0.265 ms 0.237 ms 0.220 ms 5 ae-7-7.ebr2.Paris1.Level3.net (4.69.142.186) 17.952 ms 19.524 ms 17.953 ms 6 ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 97.459 ms ae-43-43.ebr2.Washington1.Level3.net (4.69.137.58) 97.312 ms ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 97.370 ms 7 ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 97.375 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 96.057 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 109.080 ms 8 ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129) 97.329 ms 95.951 ms ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141) 99.196 ms 9 ae-2-2.ebr3.Atlanta2.Level3.net (4.69.132.85) 110.694 ms 111.950 ms 110.740 ms 10 ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242) 111.880 ms 116.502 ms 114.154 ms 11 ae-1-8.bar1.Orlando1.Level3.net (4.69.137.149) 120.114 ms 119.995 ms 120.090 ms 12 HostDime.com-10G-ethernet.core1.level3.net (67.30.140.2) 172.830 ms 262.229 ms 262.038 ms 13 server10.gnservername.net (184.171.250.130) 118.996 ms 117.664 ms 117.762 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 40 byte packets 2 ge-5-0-0-210.fra44.ip4.tinet.net (77.67.73.253) 0.877 ms 0.870 ms 0.855 ms 3 xe-8-1-0.mia10.ip4.tinet.net (89.149.180.2) 131.760 ms 131.752 ms xe-9-0-0.mia10.ip4.tinet.net (89.149.180.10) 131.715 ms 4 HostDime-gw.1ge.tinet.net (213.200.73.30) 140.257 ms 140.143 ms 140.422 ms 5 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 140.111 ms 140.142 ms 140.086 ms 6 server10.gnservername.net (184.171.250.130) 139.320 ms 139.043 ms 138.438 ms
Code:traceroute to 184.171.250.130 (184.171.250.130), 30 hops max, 60 byte packets 2 rbx-g2-a9.fr.eu (213.251.130.78) 1.115 ms 1.123 ms 1.239 ms 3 ldn-5-6.uk.eu (91.121.131.182) 7.551 ms ldn-5-6.uk.eu (91.121.131.178) 7.654 ms ldn-5-6.uk.eu (91.121.128.192) 7.400 ms 4 * * nwk-2-6k.nj.us (178.32.135.230) 76.908 ms 5 ash-1-6k.il.us (178.32.135.233) 79.752 ms * * 6 atl-1-6k.ga.us (178.32.135.189) 92.261 ms 92.479 ms * 7 * * * 8 dimenoc.nota-miami.net (198.32.125.68) 121.696 ms 121.588 ms 121.600 ms 9 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 163.072 ms 163.080 ms 330.146 ms 10 server10.gnservername.net (184.171.250.130) 112.236 ms 112.201 ms 115.526 ms
██ miscis.com - Providing domains and premium hosting solutions at an affordable price
██ cPanel+Softaculous | 99.9% Uptime SLA | CloudLinux | Daily Backups
██ Accepting PayPal, Credit/Debit Cards, Liberty Reserve
██ Currently in Netherlands, EU & Arizona, USA
-
03-28-2012, 01:50 PM #4Junior Guru Wannabe
- Join Date
- Jul 2009
- Location
- Orlando, FL
- Posts
- 70
Thank you very much for your patience. As mentioned in your tickets, the issues unfortunately do not lie within our network but instead appear to be directly with the connection with telefonica.
Our Network Admins are working on a possible solution with our bandwidth providers to see if there may be something else that can be done to provide an alternative solution. We will keep you posted.| Alex Font | HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2001
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Cloud Clusters
| Data Centers in USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands
-
03-28-2012, 02:19 PM #5Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
when I contacted it and after six hours they gave me this answer
regards
We discuss the data center that some groups that are used to reach the data center are having problems. Unfortunately it is an external problem to us we can not handle directly, but which was reported.
Let's keep this ticket open to notify you when everything is correct.
We appreciate your understanding and patience in the case.
We are at the order.Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 02:23 PM #6Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
The case is very serious is the second time, the first time they made me wait over 15 hours. I regret that work well. We can not do anything about it. It shows their lack of professionalism in assists.
On a carrier can not be expected or more than one hour. I think it's time to take a decision and move to another data center decent.Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 02:29 PM #7Nothing is impossible!
- Join Date
- Jun 2002
- Location
- Orlando, FL
- Posts
- 1,070
netandino,
I hope you can understand if the issues are not within out network, we have no control to find a solution right away. Normally we would advise you to contact your ISP but we are making the effort to talk to them directly for you and solve the issue. Surely that shows we care.
Thanks for your patience while we talk to your ISP| Manny Vivar - manny.v@hostdime.com| HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2003
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Private Cloud
| Data Centers in Florida, USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands | Colombia |
-
03-28-2012, 02:35 PM #8Hello World
- Join Date
- Nov 2009
- Location
- /etc/my.cnf
- Posts
- 10,657
HostDime have a great team of people and believe me if the issue was within their network it would be delt with soon as...
I would love to know their recruitment process
I only have good things to say about HostDime and they certainly dont clown around like some providers these days.
Their billing team is fair and their support staff are VERY knowledgable...Last edited by Server Management; 03-28-2012 at 02:38 PM.
-
03-28-2012, 02:36 PM #9Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
Pues no es exactmanete el problema de mi IPS, y ya hay antecedentes. siempre falla su red. esa ves me hicieron esperar para decirme que su ingenieros detectaron un problema den los sumadores de network "problema de balanceo"
do not lie, you can review the ticket #363464
Good afternoon Theodore
Apparently one of the ISPs data center had a balancing problem in one of the switches, the supplier was contacted and solved the problem, we performed pings throughout the evening without losing packets, let us know to continue with problems.
Best regards / Best Regards,Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 02:47 PM #10Nothing is impossible!
- Join Date
- Jun 2002
- Location
- Orlando, FL
- Posts
- 1,070
The issues in that ticket were 2 months ago which are not related to the telefonica peering issues with level3 you are experiencing right now. These are 2 totally different issues at 2 totally different times
Telefonica peers with many different providers, their peering with level3 is the issue presently. So it is possible other servers you have don't use that exact route.
You can see by the post above from "Miscis" the issue is not happening to others.| Manny Vivar - manny.v@hostdime.com| HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2003
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Private Cloud
| Data Centers in Florida, USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands | Colombia |
-
03-28-2012, 02:57 PM #11Hello World
- Join Date
- Nov 2009
- Location
- /etc/my.cnf
- Posts
- 10,657
-
03-28-2012, 03:24 PM #12Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
Well, not exactly the same but are similar.
We have problems in access, connectivity, slow, packet loss, from Peru and Spain. in that you see with JAPAN. I've seen claims of many customers that their services provided are faulty. The support is slow.
I have personally spoken on the phone. and often the answer is the same. We are working on it. What happens is that technical support is remote. With engineers in the data center apparently takes communication. Must have effective people in the same datacenter
We need only support hardware and network connection. Personally I have many other servers in different data centers, for example, SoftLayer and things are different. The support is different.
We do not ask do wonders, we know that everything can have anomalies, faults, breakdowns. Just ask a real service and optimal. For this there are people specializing in everything to solve the problem immediately.Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 05:48 PM #13Nothing is impossible!
- Join Date
- Jun 2002
- Location
- Orlando, FL
- Posts
- 1,070
As mentioned above normally any other host would advise you to contact your ISP but we are making the effort to talk to them directly for you and solve the issue. Surely that shows our commitment to you for real service
| Manny Vivar - manny.v@hostdime.com| HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2003
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Private Cloud
| Data Centers in Florida, USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands | Colombia |
-
03-28-2012, 05:52 PM #14Web Hosting Master
- Join Date
- Nov 2009
- Location
- Colombia
- Posts
- 2,150
I've never had downtime in over a year of service, in their servers and servers/VPS from other providers.
If it's not their issue, how can they fix it? At least they are trying to contact Telefonica...
By the way, the connection from Colombia to HD is top notch█ Diego Rodríguez B. - https://diegorbaquero.com
█ Software Engineer @ Protocol Labs | Filecoin Saturn
-
03-28-2012, 06:12 PM #15Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
I had heard the bad reputation of HostDime, many others commented on it but still wanted to try to confirm what I had already a problem before, I had almost overlooked.
But you can not keep waiting their wills, not a charity service. You must be a good and efficient service or anything.
Perhaps customers will continue to expect when I say the ISP data center is wrong?
Fortunately not a direct server to my production use since we work directly with the planet "current SoftLayer" and for over eight years and have seen problems of this nature.
We know how bad it is to listen, not in our reach. If change is going badly for ISP and so give good service to their customers. At least the team is very upset with GN HostDime and from my experience and recommend no more nor speak for them.
Rather, they are a bad company, has constant problems with your network.
I do not think the ISPs always fail and worse in my case only two months and with many surprises.
NOTE: I am not against X staff, I am against the service.Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 06:20 PM #16Nothing is impossible!
- Join Date
- Jun 2002
- Location
- Orlando, FL
- Posts
- 1,070
It seems clear your not reading our posts, I understand your upset about the issues you are seeing but you are getting upset at the wrong company. If you do a search here on WHT you will see our reputation is the contrary of what your stating.
As mentioned above again, we are in contact with telefonica to try and isolate this issue for you.| Manny Vivar - manny.v@hostdime.com| HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2003
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Private Cloud
| Data Centers in Florida, USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands | Colombia |
-
03-28-2012, 06:29 PM #17Hello World
- Join Date
- Nov 2009
- Location
- /etc/my.cnf
- Posts
- 10,657
Your post doesnt make an ounce of sense...
How can you be upset with HostDime when the problem doesnt lay with them but rather your ISP?
Also as pointed out if you did a search on here you would find HostDime have an excellent reputation and their network is second to none.
Maybe you should part ways and move on instead of making up aload of false accusations.
After all the owner of HostDime himself is even going to the extra mile by responding here to your concerns...
-
03-28-2012, 06:37 PM #18Junior Guru Wannabe
- Join Date
- Apr 2010
- Location
- Perú
- Posts
- 37
Look. For a service is optimal, not only have the best engineer, even the best hardware in the data center. It is a system. This includes your ISP provider. Sales staff, accounting, level platform supported by others.
Apart from that I have several other servers in data centers and I can attest, and nobody says, our services are excellent but our ISP fails.
The answer is simple, because if something fails, everything fails. It's been a day and still no solution.
Whenever we have put clear examples.
To eat a good meal, you should have good quality raw material and good flavor, "made by specialists."
Here was my claim and you will rightly in my place would be saying the same thing. In two months we have seen several and have always talk to my ticket basis.Net Andino S.A.C.| Creating New Solutions in Information Systems. In Spanish
-
03-28-2012, 07:00 PM #19Web Hosting Master
- Join Date
- Nov 2009
- Location
- Colombia
- Posts
- 2,150
Are you actually reading your own comments?
You are damaging your reputation.
It's not a problem with HostDime's Data Center. It's a problem with the routing from your place to their datacenter. You ISP's connectivity is the issue.
Instead of bashing HostDime when they are doing more than you are to help fix a problem that's not even them, you should go to the root of the issue, not the DC where one or some of your servers are hosted.
If I was HostDime I would cancel the contract with you at the end of the month.█ Diego Rodríguez B. - https://diegorbaquero.com
█ Software Engineer @ Protocol Labs | Filecoin Saturn
-
03-28-2012, 08:16 PM #20Web Hosting Evangelist
- Join Date
- Jul 2010
- Location
- Orlando, FL
- Posts
- 521
Hello netandino,
I don't fully understand your analogy, but to cap off this thread, we will continue to actively work on the service issues with the ISP in question and we will get it resolved. If you choose to leave our service due to these issues, that is of course your choice but we will keep working on it until it is solved completely.
We thank you for your patronage and understanding.
Have a great day,| Dennis Henry | HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2001
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Cloud Clusters
| Data Centers in USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands
-
03-28-2012, 11:53 PM #21Solid State
- Join Date
- Aug 2010
- Posts
- 1,687
HostDime is only responsible for their own network, and it sounds like they manage it very well. They can't be held accountable for issues with your ISP. Maybe there is a language barrier here where you think that HostDime is your ISP? They're not saying, "our services are excellent but our ISP fails." They're saying, "our network is not the issue--YOUR ISP has bad routing to our network which we can't control." They are not the bad guys.
██ RamNode - High Performance Cloud VPS
██ SSD Cloud and Shared Hosting
██ NYC - LA - ATL - SEA - NL - DDoS Protection - AS3842
██ Deploy on our SSD cloud today! - www.ramnode.com
-
03-29-2012, 06:11 AM #22Web Hosting Master
- Join Date
- Sep 2009
- Posts
- 2,277
Hello,
As it has been stated many times it was not HostDimes issue it was an issue with your ISP and who they route through.
Depending on the ISPs you have an who they choose to route with will depend on the experience you get.
I have a significant number of services with HostDime and have not experienced any of the above with them.
HostDime do not in any way have a bad reputation. I personally believe they are one of the best hosts on this forum.
You need to listen to the advice that has been given to you on this forum as everyone is telling you the same thing.
In this case HostDime went above and beyond to try and resolve an issue with an external network, that does indeed show the commitment to providing a quality and reliable network.
-
03-29-2012, 08:31 AM #23Newbie
- Join Date
- May 2011
- Posts
- 8
The support overall was great however I switch to a dedicated server monday with them and with in 5 hours my site was hacked and all my file was deleted and they cant even explain to me how this happen
The only thing that saved is that I had my site info still on the older server.
-
03-29-2012, 08:38 AM #24Junior Guru Wannabe
- Join Date
- Jul 2009
- Location
- Orlando, FL
- Posts
- 70
Rexxy,
Are you able to either provide me with a ticket ID here or via DM and I will be more than willing to look into the situation for you. I apologize in advance for any extended issues and assure you that we will do everything we can to assist.| Alex Font | HostDime | Premier Global Data Centers
| www.hostdime.com/global | Global Infrastructure as a Service (IaaS) Provider Since 2001
| Managed Dedicated Servers | Global Colocation Facilities | Managed VPS | Managed Cloud Clusters
| Data Centers in USA | Mexico | Brazil | UK | Hong Kong | India | Netherlands
-
03-29-2012, 08:45 AM #25Newbie
- Join Date
- May 2011
- Posts
- 8
Ticket ID is HD12426
Thanks
Similar Threads
-
Years of Experience in Support/Sales/Joomla Sites/ Basic Designs + References
By TheSonic in forum Employment / Job RequestsReplies: 0Last Post: 04-30-2010, 06:45 PM -
[For Hire] Sys Admin/Tech Support / With References / 8+ years experience.
By UWebSmart in forum Employment / Job RequestsReplies: 0Last Post: 11-20-2009, 04:51 PM -
[For Hire] Experienced Admin - 8+ yrs Experience (SOLID References)
By rwxguru in forum Employment / Job RequestsReplies: 3Last Post: 10-23-2009, 05:03 AM -
[For Hire] Experienced Tech & Admin - 7yrs Experience + Good References
By hzDylan in forum Employment / Job RequestsReplies: 5Last Post: 09-09-2009, 01:18 PM -
Seeking a job (looking for experience, I have references/resume)
By douglashanna in forum Employment / Job OffersReplies: 2Last Post: 03-03-2005, 07:45 PM