Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Datashack Problem ?
Datashack Problem ?
| Posted by rajapatr1, 02-04-2012, 02:59 AM |
Hello
now datashack network problem ?
Round trip time to 173.208.196.xx: 34 ms
Timed out
Round trip time to 173.208.196.xx: 23 ms
Timed out
Timed out
Timed out
Round trip time to 173.208.196.xx: 26 ms
Round trip time to 173.208.196.xx: 23 ms
Timed out
Timed out |
| Posted by Kevin Hillstrand, 02-04-2012, 04:39 AM |
There website is loading perfectly alright on my end...
Have you tried contacting there support?
Best,
Kevin |
| Posted by JD0192, 02-04-2012, 04:58 AM |
No complaints on my end, Just send them a email to have a look at the server.
Quote:
[root@localhost ~]# wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-02-04 02:57:20-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'
100%[======================================>] 104,857,600 11.2M/s in 9.0s
2012-02-04 02:57:29 (11.1 MB/s) - `/dev/null' saved [104857600/104857600]
|
|
| Posted by BassHost, 02-04-2012, 09:37 AM |
It is also working fine on my end.
Quote:
[root@ka3 ~]# wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-02-04 16:40:26-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: â/dev/nullâ
100%[======================================>] 104,857,600 34.0M/s in 2.9s
2012-02-04 16:40:29 (34.0 MB/s) - â/dev/nullâ
|
|
| Posted by rajapatr1, 02-04-2012, 10:58 AM |
|
Now it comeback to normal network have attack |
| Posted by ryguy222, 02-04-2012, 11:55 AM |
|
Hrmm not even a blip on any of my servers. |
| Posted by JD0192, 02-04-2012, 12:51 PM |
Guessing your server is on a 1Gbit port?
Quote:
|
Originally Posted by BassHost
It is also working fine on my end.
|
|
| Posted by BassHost, 02-04-2012, 01:36 PM |
Quote:
|
Originally Posted by JD0192
Guessing your server is on a 1Gbit port?
|
Yep ... this server is colocated them. |
| Posted by pubcrawler, 02-04-2012, 04:04 PM |
|
I was around working on server within Datashack's colo facility overnight. Never noticed any loss of connectivity. |
| Posted by BassHost, 02-04-2012, 06:50 PM |
Quote:
|
Originally Posted by pubcrawler
I was around working on server within Datashack's colo facility overnight. Never noticed any loss of connectivity.
|
Off topic ...
How is their colo facility? Never visited them in person. |
| Posted by Keiro, 02-04-2012, 08:01 PM |
[root@serv ~]# wget -O /dev/null http://cachefly.cachefly.net/100mb.test --2012-02-04 12:00:23-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'
100%[====================================================================================================================================================== =============================================>] 104,857,600 28.9M/s in 3.7s
2012-02-04 12:00:26 (27.4 MB/s) - `/dev/null' saved [104857600/104857600]
Pretty quick.
I've got other issues with Datashack though. |
| Posted by pubcrawler, 02-04-2012, 08:09 PM |
I was working remotely on the server.
Mentioned the part of this being within Datashack's colo facility, because that's a different location than their dedicated servers.
As such, if the original poster didn't have colo server, quite possible something might have been going on over at Wholesale Internet (that's my understanding where other Datashack stuff is housed).
Haven't been to their colo facility in person. I try not to visit colo facilities in person since we have elected to man our airports with TSA stupidness and driving around the country gets tiring. Cheaper just to pay for hands-on or hire a contractor local to the facility. |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
