Take2hosting.com - DOWN!!! - Knowledgebase

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Take2hosting.com - DOWN!!!

Take2hosting.com - DOWN!!!

Posted by QuickWeb-Roel, 12-15-2009, 06:29 AM
Seems like a bad welcome! first day of my our server and the entire network is down including their own site

I was initially impressed with their fast provisioning and responsive support! I wonder what's going on?

IP address: 38.99.70.2
Host name: take2hosting.com
Alias:
take2hosting.com
38.99.70.2 is from United States(US) in region North America

TraceRoute to 38.99.70.2 [take2hosting.com]
Hop (ms) (ms) (ms) IP Address Host name
1 16 12 6 72.249.128.109 -
2 26 14 9 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 11 13 9 4.69.145.133 ae-33-80.car3.dallas1.level3.net
4 9 15 15 4.68.110.110 cogent-comm.car3.dallas1.level3.net
5 8 10 7 154.54.6.65 te2-4.mpd01.dfw01.atlas.cogentco.com
6 27 24 29 154.54.25.206 te9-1.mpd01.mci01.atlas.cogentco.com
7 32 20 24 154.54.29.230 te0-1-0-0.ccr21.mci01.atlas.cogentco.com
8 61 55 56 154.54.30.53 te0-0-0-2.ccr21.sfo01.atlas.cogentco.com
9 62 69 63 154.54.30.50 te4-3.mpd01.sfo01.atlas.cogentco.com
10 62 56 57 154.54.1.26 te3-4.mpd01.sjc01.atlas.cogentco.com
11 68 65 83 154.54.26.146 te4-3.ccr01.sjc07.atlas.cogentco.com
12 Timed out 71 Timed out 38.99.68.130 take-two-hosting-inc-10-gbit-ethernet.demarc.cogentco.com
13 Timed out Timed out Timed out -
14 Timed out Timed out Timed out -
15 Timed out Timed out Timed out -
16 Timed out Timed out Timed out -
Trace aborted.

Update: Ok now up again! maybe around 10 minutes outage!!!
Posted by CNSERVERS, 12-15-2009, 06:33 AM
they seem to have pretty good uptime from what i heard.
Posted by QuickWeb-Roel, 12-15-2009, 06:39 AM

Quote:

Originally Posted by meyu

they seem to have pretty good uptime from what i heard.

yep hopefully all good as i haven't seen any bad reviews about them there were total 2 downtime almost 5 minutes each and 5 minutes apart. Server remains up so could be router hiccup.

just-ping:

Singapore, Singapore: Packets lost (60%) 368.8 370.8 374.3 38.99.70.2
Amsterdam2, Netherlands: Packets lost (70%) 163.9 165.0 165.9 38.99.70.2
Florida, U.S.A.: Packets lost (90%) 109.0 109.0 109.0 38.99.70.2
Amsterdam3, Netherlands: Packets lost (80%) 166.0 166.7 167.3 38.99.70.2
Hong Kong, China: Packets lost (100%) 38.99.70.2
Rio de Janeiro, Brazil: Packets lost (90%) 199.1 199.1 199.1 38.99.70.2
Sydney, Australia: Packets lost (90%) 158.4 158.4 158.4 38.99.70.2
Munchen, Germany: Packets lost (70%) 177.1 178.3 179.9 38.99.70.2
Cologne, Germany: Packets lost (70%) 171.7 172.6 173.6 38.99.70.2
New York, U.S.A.: Packets lost (70%) 82.7 83.9 85.6 38.99.70.2
Stockholm, Sweden: Packets lost (80%) 197.0 197.2 197.4 38.99.70.2
Santa Clara, U.S.A.: Packets lost (90%) 9.3 9.3 9.3 38.99.70.2
Vancouver, Canada: Packets lost (80%) 75.5 75.7 76.0 38.99.70.2
Krakow, Poland: Packets lost (90%) 205.1 205.1 205.1 38.99.70.2
London, United Kingdom: Packets lost (80%) 158.7 158.8 158.9 38.99.70.2
Madrid, Spain: Packets lost (70%) 291.3 291.6 291.8 38.99.70.2
Padova, Italy: Packets lost (100%) 38.99.70.2
Austin, U.S.A.: Packets lost (90%) 58.6 58.6 58.6 38.99.70.2
Amsterdam, Netherlands: Packets lost (80%) 160.0 160.7 161.5 38.99.70.2
Paris, France: Packets lost (80%) 164.5 165.8 167.2 38.99.70.2
Melbourne, Australia: Packets lost (70%) 169.5 170.8 171.6 38.99.70.2
Shanghai, China: Packets lost (80%) 235.0 236.6 238.1 38.99.70.2
Copenhagen, Denmark: Packets lost (90%) 182.3 182.3 182.3 38.99.70.2
Lille, France: Packets lost (50%) 174.3 174.7 175.2 38.99.70.2
San Francisco, U.S.A.: Packets lost (90%) 7.3 7.3 7.3 38.99.70.2
Zurich, Switzerland: Packets lost (90%) 187.6 187.6 187.6 38.99.70.2
Mumbai, India: Packets lost (90%) 260.7 260.7 260.7 38.99.70.2
Chicago, U.S.A.: Packets lost (70%) 57.8 58.3 58.5 38.99.70.2
Johannesburg, South Africa: Packets lost (80%) 344.8 349.1 353.5 38.99.70.2
Nagano, Japan: Packets lost (80%) 112.6 114.4 116.2 38.99.70.2
Haifa, Israel: Packets lost (100%) 38.99.70.2
Auckland, New Zealand: Packets lost (80%) 132.8 133.1 133.4 38.99.70.2
Antwerp, Belgium: Packets lost (90%) 169.8 169.8 169.8 38.99.70.2
Groningen, Netherlands: Packets lost (90%) 166.8 166.8 166.8 38.99.70.2
Moscow, Russia: Packets lost (50%) 207.0 208.5 210.7 38.99.70.2
Dublin, Ireland: Packets lost (60%) 176.1 189.5 228.9 38.99.70.2
Oslo, Norway: Packets lost (100%) 38.99.70.2
Odessa, Ukraine: Packets lost (100%) 38.99.70.2
Manchester, United Kingdom: Packets lost (90%) 169.0 169.0 169.0 38.99.70.2
Vilnius, Lithuania: Packets lost (80%) 222.6 231.5 240.5 38.99.70.2
Posted by msherman, 12-15-2009, 07:11 AM
I can confirm that there was a customer under DDoS attack which impacted ingress connectivity for about 15 minutes this morning.

The attack has been mitigated and network services have returned to normal.
Posted by markb1439, 12-19-2009, 02:47 AM
Definitely don't judge Take 2 from this situation. Their uptime is fantastic (as is everything else about them). Highly recommended, based on a year and a half of experience.

And, in this case, it seems as if they did the best possible job mitigating the situation.
Posted by jimmy1128, 12-21-2009, 05:29 AM
I've been with Take2Hosting for more than one year, and never had trouble with their network before.
I think they have solved the problem within a reasonable time. Everything's working fine now from my end.
Posted by QuickWeb-Roel, 12-21-2009, 05:39 AM
yes after those first two days consecutive downtime of 10-15 minutes due to DDoS attack everything seems normal now... and I must say their support is A grade!