2host networks issues?

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > 2host networks issues?

Posted by backtogeek, 11-13-2010, 06:35 PM
Anyone else with services hosted by 2host (2host.com)experiencing network issues?

I am getting abv 30% packet loss from multiple locations in the UK.

Tested from Home, office and servers in 2 different UK data centers.
Zen Office
Plusnet home
BT Business

Packets: Sent = 19, Received = 13, Lost = 6 (31% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 1197ms, Average = 399ms

35 packets transmitted, 24 received, 31% packet loss, time 34009ms
rtt min/avg/max/mdev = 101.885/450.448/2294.988/562.767 ms, pipe 3

1: 213.5.182.1 (213.5.182.1) 0.046ms
2: no-rdns-yet.ohtele.com (89.238.140.102) asymm 3 0.634ms
3: vlan2.bb1.lon2.uk.gbxs.net (193.27.64.113) asymm 4 7.950ms
4: 66.216.50.73 (66.216.50.73) asymm 7 69.853ms
5: ny60-vl14-lon-vl14.bboi.net (66.216.48.213) asymm 8 98.757ms
6: no reply
7: te8-3.bbr1.ash1.bandcon.com (216.151.179.225) 112.578ms
8: 209.107.197.210 (209.107.197.210) asymm 11 101.550ms
9: te-5-5.rtr2.avl1.netriplex.com (67.23.161.254) asymm 11 101.715ms
10: 178.18.17.108 (178.18.17.108) asymm 9 172.597ms reached

hopefully not the start of another DDOS

I have raised a ticket but based on past performance I dont expect a reply this weekend.
Posted by Scientist, 11-13-2010, 07:10 PM
Seems okay here from Virgin broadband, no packet loss. Although I do get intermittent connectivity to netriplex, almost every other day my putty session gets disconnected from both at home and work.

Edit: Ok spoke too soon, I'm seeing 20% packet loss now to your IP. Though my own VPS at 2host is fine.
Posted by backtogeek, 11-16-2010, 04:28 PM
update: still high packet loss and still no reply to support ticket 3 days later...
Posted by turbovps, 11-16-2010, 11:20 PM
Try http://www.just-ping.com
Posted by backtogeek, 11-17-2010, 05:49 AM
Thanks Turbo:

Quote:

Location Result min. rrt avg. rrt max. rrt IP
Singapore, Singapore: Okay 303.1 305.3 317.5 178.18.17.108
Amsterdam2, Netherlands: Okay 102.9 103.5 106.5 178.18.17.108
Florida, U.S.A.: Okay 21.0 22.6 31.4 178.18.17.108
Amsterdam3, Netherlands: Okay 102.7 103.1 104.1 178.18.17.108
Hong Kong, China: Okay 277.7 281.0 285.3 178.18.17.108
Sydney, Australia: Okay 239.7 241.5 247.0 178.18.17.108
MÃ¼nchen, Germany: Okay 120.9 121.7 124.5 178.18.17.108
Cologne, Germany: Okay 116.1 116.2 116.3 178.18.17.108
New York, U.S.A.: Okay 29.8 30.8 35.7 178.18.17.108
Stockholm, Sweden: Okay 132.3 132.9 135.5 178.18.17.108
Santa Clara, U.S.A.: Okay 76.7 76.8 77.0 178.18.17.108
Vancouver, Canada: Okay 295.1 295.5 297.0 178.18.17.108
Krakow, Poland: Okay 133.0 133.6 134.1 178.18.17.108
London, United Kingdom: Okay 101.9 102.9 105.0 178.18.17.108
Madrid, Spain: Okay 135.8 136.7 140.7 178.18.17.108
Padova, Italy: Okay 134.6 135.3 136.9 178.18.17.108
Austin, U.S.A.: Okay 144.1 144.7 148.3 178.18.17.108
Amsterdam, Netherlands: Okay 105.2 105.4 105.8 178.18.17.108
Paris, France: Okay 109.4 110.6 117.1 178.18.17.108
Melbourne, Australia: Packets lost (10%) 252.4 253.8 255.8 178.18.17.108
Shanghai, China: Packets lost (20%) 479.3 483.2 486.9 178.18.17.108
Copenhagen, Denmark: Okay 147.6 147.8 148.4 178.18.17.108
Lille, France: Packets lost (10%) 110.3 111.9 121.3 178.18.17.108
San Francisco, U.S.A.: Okay 71.8 72.3 72.9 178.18.17.108
Zurich, Switzerland: Okay 125.4 125.7 126.0 178.18.17.108
Mumbai, India: Okay 219.5 221.5 226.5 178.18.17.108
Chicago, U.S.A.: Okay 37.4 37.5 37.7 178.18.17.108
Nagano, Japan: Okay 184.4 184.6 184.9 178.18.17.108
Haifa, Israel: Okay 177.7 178.9 181.7 178.18.17.108
Auckland, New Zealand: Okay 198.8 199.5 201.7 178.18.17.108
Antwerp, Belgium: Okay 111.1 111.4 112.4 178.18.17.108
Groningen, Netherlands: Packets lost (10%) 108.4 108.9 109.5 178.18.17.108
Moscow, Russia: Okay 152.6 153.0 154.7 178.18.17.108
Dublin, Ireland: Okay 100.2 100.8 102.3 178.18.17.108
Oslo, Norway: Okay 129.6 129.8 130.0 178.18.17.108
Kharkov, Ukraine: Okay 158.8 159.1 159.8 178.18.17.108
Manchester, United Kingdom: Okay 108.3 109.2 113.9 178.18.17.108
Vilnius, Lithuania: Okay 141.7 143.4 149.8 178.18.17.108
Ashburn, U.S.A.: Okay 23.8 24.4 25.9 178.18.17.108
Bucharest, Romania: Packets lost (10%) 143.2 145.2 147.6 178.18.17.108
Bangkok, Thailand: Okay 284.7 285.6 286.6 178.18.17.108
Kuala Lumpur, Malaysia: Okay 250.6 251.7 253.0 178.18.17.108
Jakarta, Indonesia: Okay 306.3 307.1 308.4 178.18.17.108
Cape Town, South Africa: Packets lost (10%) 250.3 252.2 254.9 178.18.17.108
Glasgow, United Kingdom: Okay 109.1 109.6 112.3 178.18.17.108
Lisbon, Portugal: Okay 133.5 136.9 142.2 178.18.17.108
Chicago, U.S.A.: Okay 27.6 28.5 34.2 178.18.17.108
Dallas, U.S.A.: Okay 39.0 40.8 46.1 178.18.17.108

Posted by backtogeek, 11-17-2010, 09:57 AM
So got a responce to my ticket 4 days later after opening 4 more will different departments.

no appology or anything just asking for a traceroute... which I allready included in the first ticket.

superb service.

Customers now complaining of buffering problems.
Posted by backtogeek, 11-22-2010, 10:28 AM
9 days later I got a reply asking if the problem was still present saying that had taken action against some abusers.

problem is still present:

Ping statistics for 178.18.17.108:
Packets: Sent = 29, Received = 25, Lost = 4 (13% loss)
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 430ms, Average = 210ms

MAN Data center:

--- shout2.lmas-networks.com ping statistics ---
35 packets transmitted, 30 received, 14% packet loss, time 34011ms
rtt min/avg/max/mdev = 127.427/150.960/373.553/53.047 ms

Network-tools.com:

Ping 178.18.17.108
Round trip time to 178.18.17.108: 48 ms
Round trip time to 178.18.17.108: 58 ms
Round trip time to 178.18.17.108: 101 ms
Round trip time to 178.18.17.108: 349 ms
Timed out
Timed out
Round trip time to 178.18.17.108: 64 ms
Round trip time to 178.18.17.108: 64 ms
Round trip time to 178.18.17.108: 51 ms
Round trip time to 178.18.17.108: 50 ms

Average time over 10 pings: 78.5 ms

ping.eu:

--- PING 178.18.17.108 (178.18.17.108) 56(84) bytes of data. ---
64 bytes from 178.18.17.108: icmp_req=3 ttl=56 time=123 ms
64 bytes from 178.18.17.108: icmp_req=4 ttl=56 time=128 ms

--- 178.18.17.108 ping statistics ---
packets transmitted 4
received 2
packet loss 50 %
time 3008 ms

--- Round Trip Time (rtt) ---
min 123.336 ms
avg 125.759 ms
max 128.183 ms
mdev 2.449 ms

That reply was sent 3 hours ago, will update when I get a reply.....
Posted by craig joe, 11-23-2010, 02:26 PM
ya will never ever get an awesome support there,

you don't even dreaming about it, they are just as it, and that's it!

no matter what!

you got what you give

.
.
.
.
.
*
and i have more than 2 accounts there :p
Posted by backtogeek, 11-25-2010, 06:02 PM
so after 14 days they told me its resolved and it seem to be.

Reason: A client on the same node was under attack....14 days to figure that out... 1 word: wow