Shared Hosting
Shared HostingKnowledgebase
Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Virpus Alert
Virpus Alert
 |
 |
 |
Posted by scyllar, 08-22-2010, 02:30 AM Hi Weekend again and my VPS has went down gain after they transfered me to another node after last weekend's nightmair. I tried to access their control panel to boot it myself, but it's also down. I don't know if it shoould raise a red flag for you if you are also with them, it's definitely a signal for me to run.
Posted by webhosting_123, 08-22-2010, 02:40 AM you are right, my server again down now..
Posted by Ventrix, 08-22-2010, 02:45 AM Could you please prove it by reporting your VPS IP to the mods?
http://www.webhostingtalk.com/report.php?p=6969639
Posted by webhosting_123, 08-22-2010, 02:50 AM yes, check.
but why you required ?
Posted by Ventrix, 08-22-2010, 02:56 AM
but why you required ?
I have a VPS hosted by Virpus and currently online.
Posted by scyllar, 08-22-2010, 02:59 AM
I have a VPS hosted by Virpus and currently online.
Posted by webhosting_123, 08-22-2010, 02:59 AM ok, but i am not fake, you check it.
Posted by scyllar, 08-22-2010, 03:02 AM
Posted by webhosting_123, 08-22-2010, 03:02 AM i think ovzglacier
Posted by scyllar, 08-22-2010, 03:05 AM
Posted by Ventrix, 08-22-2010, 03:07 AM I'm currently on ovzadrian node, did you contact their support department?
Posted by scyllar, 08-22-2010, 03:10 AM
that means much for others than for me now as I have made up my mind to run.
Posted by Ventrix, 08-22-2010, 03:12 AM
that means much for others than for me now as I have made up my mind to run.
Posted by webhosting_123, 08-22-2010, 03:13 AM ya but not receive any reply..
Posted by webhosting_123, 08-22-2010, 03:17 AM approx. 1 hour before
Posted by scyllar, 08-22-2010, 03:19 AM not very long, actually their tickets have been replied fairly fast before.
BTW, I have submited my vps ip's here, but who will monitor it? Please guide us newbies
Posted by webhosting_123, 08-22-2010, 03:39 AM you have any other option in compair price to virpus
Posted by seikan, 08-22-2010, 04:12 AM Huh.. another victim here... my VPS is down for 2 hours now..
Posted by scyllar, 08-22-2010, 04:17 AM
Posted by Ventrix, 08-22-2010, 04:28 AM
BTW, I have submited my vps ip's here, but who will monitor it? Please guide us newbies
Posted by mahadri, 08-22-2010, 05:54 AM Virpus's SolusVM says my VPS is running, but the VPS and the SolusVM ssh console have been unreachable since 2:30 AM EDT, going on 3.5 hours now. All other address in that /20 block appear unreachable too, so I submitted a ticket an hour ago and received the quick reply "Sorry for the inconvenience. We are now performing a maintenance to fix this issues. Please try after some time."
Posted by MikHo, 08-22-2010, 06:07 AM I can not reach my vps from home (goes over cogent network) but I can tracert the same ip (and get a response) from http://network-tools.com
It looks like they are facing a routing problem somewhere.
I can not react virpus.com either... but myvirpus.com is ok .. from home that is
Posted by seikan, 08-22-2010, 06:07 AM
Posted by royalduke, 08-22-2010, 06:19 AM I think I'm going to renew my virpus VPS term for another 6 months because I'm on a good node I was planning to let it go and re-signup later but I seriously don't wanna be in a bad node.
Posted by scyllar, 08-22-2010, 07:34 AM
Posted by royalduke, 08-22-2010, 07:49 AM I am on ovz-cancer (such a depressing name) and it works for me, my sites are up.
I don't think I'll ever host client sites on virpus, I just use it for.. nothing. I did sone research when I signed up, they looked good, I think I got what I needed from them as they are a budget provider.
I would love to know if anyone hosts clients with them though or uses their VPS as a hosting server, anyone?
Anyways, hopefully this issue will be solved and Ken will update us about it here at WHT.
Posted by mahadri, 08-22-2010, 08:04 AM Affected nodes appear to be ovz-crusher, ovz-disher, ovz-griffen, ovz-dubos, and ovz-barksdale. ovz-barksdale was down yesterday for 5 hours due to "the mainnode under which your VPS hosted faced some temporary issue". Out of the 89.5 hours I've had this Virpus VPS, it's been down for 10.5 hours and counting, an 88% uptime. It's too bad they can't keep it accessible because everything else is great. I'm seriously considering their 7 day money back satisfaction guarantee right now.
Posted by MikHo, 08-22-2010, 08:07 AM
I would love to know if anyone hosts clients with them though or uses their VPS as a hosting server, anyone?
And I have a few customer sites left on that VPS, I am however looking for another provider so I can move those left away from Virpus.
I have been with Virpus for a very long time now and it has had its ups and downs. But the network problems that we are facing now has increased and I see more often sudden drops in the communication.
Posted by royalduke, 08-22-2010, 08:29 AM
And I have a few customer sites left on that VPS, I am however looking for another provider so I can move those left away from Virpus.
I have been with Virpus for a very long time now and it has had its ups and downs. But the network problems that we are facing now has increased and I see more often sudden drops in the communication.
Posted by iPokz, 08-22-2010, 09:57 AM until now Virpus VPS does not work more than 8hrs.
T.T
Posted by Master Bo, 08-22-2010, 10:09 AM I can't access Virpus main site and VPS control panel from my home location (Novosibirsk, Russia, SibirTelecom ISP), nor through any Moscow-based servers.
Host-Tracker.com reports 50% or so its nodes unable to load Virpus.com site.
I managed to access Virpus user control panel using an USA-based proxy, but VPS control panel times out, community forum is down, VPS is available only occasionally and loads very slowly.
Waiting for the Support response - current state of things is very displeasing.
Update: community forum is online.
Posted by zole, 08-22-2010, 10:34 AM yes, i have same problem also with my VPS.
here replay from them :but im not sure how long it will be up againCode:Hello XXXX, We are currently facing some temporary network issue in the main node in which your VPS is hosted. We have contacted the concerned department.It will be resolved soon.Please try after sometime. Warm Regards, Rachel. Support Engineering Group Virpus Networks, Inc.
Posted by iPokz, 08-22-2010, 10:59 AM i can access to myvirpus.com
but can't access to virpus.com and all my vps
>,<
Posted by NelsonT, 08-22-2010, 11:14 AM
but can't access to virpus.com and all my vps
>,<Location Result min. rrt avg. rrt max. rrt IP
Singapore, Singapore: Packets lost (100%) 208.89.211.212
Amsterdam2, Netherlands: Packets lost (100%) 208.89.211.212
Florida, U.S.A.: Okay 48.9 49.3 49.7 208.89.211.212
Amsterdam3, Netherlands: Packets lost (100%) 208.89.211.212
Hong Kong, China: Packets lost (100%) 208.89.211.212
Sydney, Australia: Packets lost (100%) 208.89.211.212
Munchen, Germany: Packets lost (100%) 208.89.211.212
Cologne, Germany: Okay 136.7 137.1 137.6 208.89.211.212
New York, U.S.A.: Okay 53.8 65.1 78.2 208.89.211.212
Stockholm, Sweden: Packets lost (100%) 208.89.211.212
Santa Clara, U.S.A.: Okay 45.2 45.5 46.1 208.89.211.212
Vancouver, Canada: Okay 45.0 45.4 45.6 208.89.211.212
Krakow, Poland: Okay 161.0 170.9 257.1 208.89.211.212
London, United Kingdom: Okay 114.5 115.4 116.3 208.89.211.212
Madrid, Spain: Okay 157.4 158.5 159.2 208.89.211.212
Padova, Italy: Okay 171.4 175.2 180.5 208.89.211.212
Austin, U.S.A.: Packets lost (100%) 208.89.211.212
Amsterdam, Netherlands: Packets lost (100%) 208.89.211.212
Paris, France: Okay 143.1 143.8 145.0 208.89.211.212
Melbourne, Australia: Packets lost (100%) 208.89.211.212
Shanghai, China: Packets lost (100%) 208.89.211.212
Copenhagen, Denmark: Packets lost (100%) 208.89.211.212
Lille, France: Packets lost (100%) 208.89.211.212
San Francisco, U.S.A.: Okay 40.5 40.9 41.2 208.89.211.212
Zurich, Switzerland: Packets lost (100%) 208.89.211.212
Mumbai, India: Okay 290.8 291.3 291.7 208.89.211.212
Chicago, U.S.A.: Okay 37.9 38.3 38.9 208.89.211.212
Johannesburg, South Africa: Packets lost (100%) 208.89.211.212
Nagano, Japan: Packets lost (100%) 208.89.211.212
Haifa, Israel: Okay 181.0 182.1 188.5 208.89.211.212
Auckland, New Zealand: Packets lost (100%) 208.89.211.212
Antwerp, Belgium: Packets lost (100%) 208.89.211.212
Groningen, Netherlands: Okay 145.7 146.3 147.2 208.89.211.212
Moscow, Russia: Okay 188.2 188.6 189.2 208.89.211.212
Dublin, Ireland: Okay 129.2 129.7 130.1 208.89.211.212
Oslo, Norway: Packets lost (100%) 208.89.211.212
Kharkov, Ukraine: Okay 172.0 172.4 176.0 208.89.211.212
Manchester, United Kingdom: Packets lost (100%) 208.89.211.212
Vilnius, Lithuania: Packets lost (100%) 208.89.211.212
Ashburn, U.S.A.: Packets lost (100%) 208.89.211.212
Bucharest, Romania: Okay 162.3 162.6 163.1 208.89.211.212
Bangkok, Thailand: Packets lost (100%) 208.89.211.212
Kuala Lumpur, Malaysia: Okay 236.0 236.6 238.2 208.89.211.212
Jakarta, Indonesia: Okay 234.4 234.7 235.1 208.89.211.212
Cape Town, South Africa: Packets lost (100%) 208.89.211.212
Glasgow, United Kingdom: Packets lost (100%) 208.89.211.212
Lisbon, Portugal: Packets lost (100%) 208.89.211.212
Chicago, U.S.A.: Okay 37.6 37.9 38.5 208.89.211.212
Dallas, U.S.A.: Okay 11.0 11.3 11.5 208.89.211.212
Posted by zole, 08-22-2010, 11:20 AM here when i trace using my other VPS to my virpus vps : Code:[root@vps ~]# traceroute xxx.xxx.xxx.xxx traceroute to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx), 30 hops max, 40 byte packets 1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0.038 ms 0.021 ms 0.015 ms 2 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0.737 ms 0.720 ms 0.709 ms 3 te7-7.ccr02.lax05.atlas.cogentco.com (38.104.84.37) 0.403 ms 0.638 ms 0.625 ms 4 te0-2-0-2.ccr22.lax01.atlas.cogentco.com (154.54.29.201) 0.622 ms 0.870 ms 0.855 ms 5 te0-0-0-5.ccr21.iah01.atlas.cogentco.com (154.54.0.222) 36.744 ms te0-2-0-2.mpd22.lax01.atlas.cogentco.com (154.54.3.141) 0.570 ms te0-1-0-0.mpd21.lax01.atlas.cogentco.com (154.54.2.118) 0.770 ms 6 te0-3-0-6.mpd22.iah01.atlas.cogentco.com (154.54.0.254) 36.745 ms te0-3-0-6.mpd21.iah01.atlas.cogentco.com (154.54.0.230) 36.674 ms te2-1.ccr02.dfw01.atlas.cogentco.com (154.54.3.177) 42.182 ms 7 te7-3.mpd01.dfw01.atlas.cogentco.com (154.54.5.129) 42.173 ms te4-2.mpd01.dfw01.atlas.cogentco.com (154.54.25.221) 42.239 ms te0-0-0-1.mpd22.mci01.atlas.cogentco.com (154.54.0.202) 52.650 ms 8 te0-2-0-0.mpd22.mci01.atlas.cogentco.com (154.54.30.158) 52.385 ms te4-2.mpd01.mci01.atlas.cogentco.com (154.54.30.174) 52.820 ms te4-4.mpd01.mci01.atlas.cogentco.com (154.54.30.166) 52.810 ms 9 te4-2.mpd01.mci01.atlas.cogentco.com (154.54.30.174) 52.858 ms 53.039 ms te4-4.mpd01.mci01.atlas.cogentco.com (154.54.30.166) 53.025 ms 10 vl3510.na01.b006290-1.mci01.atlas.cogentco.com (38.112.32.70) 52.987 ms 53.311 ms 53.698 ms 11 38.100.176.226 (38.100.176.226) 53.045 ms 53.069 ms 53.250 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * [root@vps ~]#
Posted by webhosting_123, 08-22-2010, 11:27 AM problem not solved till now....
above 10 hour today downtime..
Posted by NelsonT, 08-22-2010, 11:29 AM
Posted by iPokz, 08-22-2010, 11:33 AM Trace from Thailand(CAT-IDC)
[root@sephiroth ~]# traceroute 208.89.211.183
traceroute to 208.89.211.183 (208.89.211.183), 30 hops max, 40 byte packets
1 61.19.251.2 (61.19.251.2) 0.810 ms 0.815 ms 0.859 ms
2 (61.19.240.105) 0.734 ms 0.777 ms 0.876 ms
3 202.129.31.253 (202.129.31.253) 0.632 ms 0.616 ms 0.609 ms
4 202.47.247.98 (202.47.247.98) 0.711 ms 0.764 ms 0.806 ms
5 202.47.247.98 (202.47.247.98) 0.783 ms 0.820 ms 0.866 ms
6 61.19.10.5 (61.19.10.5) 0.597 ms 0.572 ms 0.703 ms
7 61.19.9.65 (61.19.9.65) 2.201 ms 2.183 ms 2.200 ms
8 61.19.9.46 (61.19.9.46) 1.968 ms 2.083 ms 2.071 ms
9 202.47.253.233 (202.47.253.233) 205.778 ms 205.778 ms 205.760 ms
10 vl201.mpd03.lax01.atlas.cogentco.com (38.104.230.37) 351.188 ms 351.480 ms 351.551 ms
11 te0-0-0-6.ccr21.lax01.atlas.cogentco.com (154.54.28.141) 206.634 ms 206.629 ms te0-0-0-6.ccr22.lax01.atlas.cogentco.com (154.54.28.145) 206.910 ms
12 te0-0-0-5.ccr21.iah01.atlas.cogentco.com (154.54.0.222) 244.148 ms te0-1-0-0.mpd22.lax01.atlas.cogentco.com (154.54.25.166) 206.145 ms te0-0-0-5.ccr22.iah01.atlas.cogentco.com (154.54.5.193) 243.426 ms
13 te0-3-0-6.mpd22.iah01.atlas.cogentco.com (154.54.0.254) 242.637 ms te8-3.ccr02.dfw01.atlas.cogentco.com (154.54.1.73) 250.025 ms te0-1-0-0.mpd21.iah01.atlas.cogentco.com (154.54.1.85) 242.794 ms
14 te4-1.mpd01.dfw01.atlas.cogentco.com (154.54.2.14) 295.150 ms te0-2-0-3.ccr22.mci01.atlas.cogentco.com (154.54.5.166) 258.581 ms te0-1-0-0.mpd21.mci01.atlas.cogentco.com (154.54.29.229) 260.268 ms
15 te0-2-0-0.mpd21.mci01.atlas.cogentco.com (154.54.30.161) 260.496 ms te0-3-0-0.mpd22.mci01.atlas.cogentco.com (154.54.25.206) 259.494 ms te0-2-0-0.mpd21.mci01.atlas.cogentco.com (154.54.30.161) 260.113 ms
16 te4-4.mpd01.mci01.atlas.cogentco.com (154.54.30.166) 260.282 ms 38.20.52.162 (38.20.52.162) 259.190 ms 259.773 ms
17 38.20.52.162 (38.20.52.162) 260.681 ms 260.193 ms 259.804 ms
18 * 38.100.176.226 (38.100.176.226) 260.400 ms 261.398 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Trace From Thailand (CSLoxinfo)
[root@zeus ~]# traceroute 208.89.211.183
traceroute to 208.89.211.183 (208.89.211.183), 30 hops max, 40 byte packets
1 210.1.31.253 (210.1.31.253) 1.761 ms 1.965 ms 2.165 ms
2 210.1.0.164 (210.1.0.164) 0.694 ms 0.791 ms 210.1.0.165 (210.1.0.165) 0.4 18 ms
3 203.146.101.97 (203.146.101.97) 1.313 ms 1.297 ms 203.146.101.17 (203.146. 101.17) 1.146 ms
4 202.183.136.37 (202.183.136.37) 1.011 ms 0.998 ms 0.982 ms
5 202.183.136.109 (202.183.136.109) 47.674 ms 47.645 ms 47.649 ms
6 ge1-0-4.singapore1.sin.seabone.net (213.144.176.37) 31.102 ms 30.811 ms 3 1.020 ms
7 pos0-15-3-3.palermo17.pal.seabone.net (195.22.218.194) 275.848 ms 275.585 ms 275.566 ms
8 pos0-9-0-0.milano50.mil.seabone.net (195.22.218.217) 251.388 ms 251.295 ms 251.150 ms
9 te0-14-2-0.franco52.fra.seabone.net (89.221.34.178) 247.548 ms 246.947 ms 246.631 ms
10 ge4-0.franco32.fra.seabone.net (89.221.34.107) 234.111 ms 234.084 ms *
11 te0-7-0-7.ccr22.fra03.atlas.cogentco.com (130.117.15.93) 248.323 ms 248.09 7 ms 248.260 ms
12 te0-2-0-7.mpd22.fra03.atlas.cogentco.com (130.117.49.149) 248.338 ms 248.4 57 ms 248.345 ms
13 te0-0-0-4.ccr21.ymq02.atlas.cogentco.com (154.54.28.93) 325.808 ms te0-1-0- 4.ccr21.ymq02.atlas.cogentco.com (154.54.26.141) 325.618 ms 325.695 ms
14 te0-0-0-6.mpd21.ord01.atlas.cogentco.com (38.20.46.9) 304.279 ms te0-3-0-3. ccr21.mci01.atlas.cogentco.com (154.54.2.189) 306.532 ms te0-0-0-3.ccr22.mci01. atlas.cogentco.com (154.54.30.101) 308.466 ms
15 te0-2-0-3.mpd22.mci01.atlas.cogentco.com (154.54.6.253) 314.617 ms 314.645 ms te0-0-0-3.mpd21.mci01.atlas.cogentco.com (154.54.2.233) 307.687 ms
16 te4-4.mpd01.mci01.atlas.cogentco.com (154.54.30.166) 319.776 ms te4-2.mpd01 .mci01.atlas.cogentco.com (154.54.30.174) 324.808 ms 324.873 ms
17 vl3510.na01.b006290-1.mci01.atlas.cogentco.com (38.112.32.70) 315.242 ms 3 15.477 ms 314.142 ms
18 38.100.176.226 (38.100.176.226) 315.538 ms 314.490 ms 314.197 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Posted by zole, 08-22-2010, 11:35 AM
Yes, i also trying from 3 def source, Indonesia, Singapore and US all stop onafter that all time outCode:15 184 ms 184 ms 183 ms 38.100.176.226
Posted by zole, 08-22-2010, 12:00 PM Now my VPS back Online
but still unable to access :Code:https://manage.virpus.com/
Posted by webhosting_123, 08-22-2010, 12:00 PM now working..
Posted by mahadri, 08-22-2010, 12:03 PM
Posted by iPokz, 08-22-2010, 12:14 PM 173.0.48.x
173.0.49.x
now working but
208.89.211.x
208.89.212.x
not working
Posted by zole, 08-22-2010, 12:21 PM Based on my web monitor :
Down Time: 9 hours 34 minutes 8 seconds
Posted by Flinty, 08-22-2010, 12:24 PM I'm surprised by the lack of communication from Virpus. I've yet to receive any email... or anything telling me they're are aware of the situation.
:/
EDIT: Do'h. Just now got an email.
Posted by mahadri, 08-22-2010, 12:26 PM Email from Virpus:
Overnight, Virpus Networks experienced a routing issues with one of our carriers. It seems routes failed to switch over for one of our ranges (173.0.*.*) to our secondary provider, which caused some of our customers to be down for a long period of time. Our datacenter has corrected this issue at this time, and all customers should be back online. We sincerely apologize for the inconvenience caused by this and have ensured that nothing like this will happen again.
Thank you for your patience, and if you are having any service issues, please e-mail our administration at general@virpusnetworks.net. Note that we will only respond to service issue e-mails related to this issue.
Warm Regards,
Virpus Networks, Inc.
Posted by Master Bo, 08-22-2010, 12:29 PM The Virpus has contacted me rather quickly.
To me, the connectivity to all the mentioned resources is restored. I hope for others, too.
Posted by iPokz, 08-22-2010, 12:31 PM All my vps is online.
Posted by Ankheg, 08-22-2010, 12:34 PM Man, I envy you guys with your mere 10-hour downtime. We're ex-TeamVPS (remember them?) customers on the server VM4, which has been down - with no public announcements, meaningful updates, or information - since Tuesday. On Thursday, I think it was, Ken reluctantly offered to give us a bare VM on a new node. I'm holding out for the old VM and old IP address (69.197.142.130), mainly out of a morbid fascination to see how horribly they can continue to neglect ex-TeamVPS customers. (Customers affected by ovz-disher issues last week got regular updates via Virpus' forums. Customers affected by VM4 being dead get... Nothing.)
There were no customers on the VPS, and I'm very patient.
Posted by amaZe, 08-22-2010, 03:50 PM
Posted by quad3datwork, 08-22-2010, 04:41 PM I'm on ovztitan and has been a roller coaster ride lately. 12h 9min downtime over past 7 days. Honestly, I'm paying few bucks a month for this 'test/dev' VPS so I am not complaining.
You get what you paid for. If you gonna go all cheap out, don't expect enterprise grade product. This is common sense.
Posted by scyllar, 08-22-2010, 09:47 PM
Posted by webhosting_123, 09-06-2010, 01:12 AM again down server
Posted by seikan, 09-06-2010, 02:43 AM Mine is still up. Which node are you located?
Posted by webhosting_123, 09-06-2010, 03:14 AM node is ovz-disher
Posted by DeltaAnime, 09-06-2010, 03:15 AM What's your IP?
Francisco
Posted by webhosting_123, 09-06-2010, 03:18 AM 173.0.48.171
Posted by seikan, 09-06-2010, 03:38 AM Mine is ovz-mike and still up. Did you contacted their support?
Posted by webhosting_123, 09-06-2010, 03:46 AM yes i contact but not receive any reply..
Posted by seikan, 09-06-2010, 03:53 AM I've to admit that their support is kinda very slow sometimes.
Posted by webhosting_123, 09-06-2010, 03:58 AM i face very downtime last 1 month
Posted by Hsunami, 09-06-2010, 02:34 PM Still on ovz-disher? If you want to stay with Virpus, I would suggest you to ask to be moved to a different node. I've had good service since they moved me. It looks like ovz-disher still has some gremlins.
Posted by Ankheg, 09-06-2010, 02:38 PM
(cough, VM4, cough.)
Posted by zole, 09-06-2010, 02:42 PM
Posted by Hsunami, 09-06-2010, 03:45 PM ovz-glacier.
Posted by webhosting_123, 09-08-2010, 06:16 AM again down ovz-disher
Posted by DanielTroncoso, 09-10-2010, 02:18 PM my vos in virpus is down
Ip: 173.0.51.208
its service contract 09/08/2010, I could never use that is down
Posted by ipublishing, 09-19-2010, 06:53 AM
Ip: 173.0.51.208
its service contract 09/08/2010, I could never use that is down
Add to Favourites 
Print this Article
Also Read
