What's causing MT5 to drop around 200 times every 24 hours? - page 8

 

Nope, still not working.  Down 16 times between 4:30 and 6:30.  That's 16-32 minutes PER HOUR of downtime.  Unusable platform.

These are not normal.  Normal is a couple times a day for less than a minute.  These are lasting between 2 and 3 minutes each.  

You cannot trade when the platform is down 25-50% of each hour.

 
8am eastern cash open and it disconnects.  Such a useful platform.
 
Clearview #:

Nope, still not working.  Down 16 times between 4:30 and 6:30.  That's 16-32 minutes PER HOUR of downtime.  Unusable platform.

These are not normal.  Normal is a couple times a day for less than a minute.  These are lasting between 2 and 3 minutes each.  

You cannot trade when the platform is down 25-50% of each hour.

I understand your frustration but the only way to maybe have a solution is to push the broker to collaborate. As suggested in private communication.
 
Down for 42 minutes so far.  8:06am to 8:48am.
 
Alain Verleyen #:
I understand your frustration but the only way to maybe have a solution is to push the broker to collaborate. As suggested in private communication.

I've pushed.  One of the VPS providers has pushed.  You've pushed.  I will continue to update on here until they fix it.  Who knows, maybe MQ will get sick of me posting and push AMP Futures also.

MQL5 refused to credit the instance of the indicator I use that the platform rejected after whatever change was made yesterday.  

I'm tired of the run around.  Sick to my stomach every day now because of it.

I might be off a day, but I think today is day 32 since I first contacted AMP about this.

 

For the time being, I am not inclined to say AMP or Metatrade is the culprit, but rather the VPS provider(s), while ATM I believe your best bet would be to use the home PC.. Having said that, I am also inclined to go find a VPS and try out my self :)

greets

 
democog #:

For the time being, I am not inclined to say AMP or Metatrade is the culprit, but rather the VPS provider(s), while ATM I believe your best bet would be to use the home PC.. Having said that, I am also inclined to go find a VPS and try out my self :)

greets

For now we don't really have a confirmed clue about "the culprit", but AMP is the most probably, not the VPS providers.

One way to have more information is to use an other broker on the same VPS, preferably with a real account. Then we will know.

 
Alain Verleyen #:

For now we don't really have a confirmed clue about "the culprit", but AMP is the most probably, not the VPS providers.

One way to have more information is to use an other broker on the same VPS, preferably with a real account. Then we will know.

Yep, all right, I am busy for now,, but in the next couple hours I am going to find a VPS and use my real AMP account, 

greets

 
democog #:
I believe your best bet would be to use the home PC
Thank you reiterating my previous suggestion. Again, removing the VPS service from the equation will reduce the number of variables involved--even if only done for testing purposes. If the issue persists without the VPS service involved, then obviously the issue is likely not the VPS service. If the issue resolves without the VPS service involved, then the isuue is likely the VPS service.
 
Ryan L Johnson #:
Thank you reiterating my previous suggestion. Again, removing the VPS service from the equation will reduce the number of variables involved--even if only done for testing purposes. If the issue persists without the VPS service involved, then obviously the issue is likely not the VPS service. If the issue resolves without the VPS service involved, then the isuue is likely the VPS service.

Clearview has mentioned that the home PC is working fine, so I would agree that it looks like that the VPS provider has the problem. Also, while the info about the problem is quite scarce, I mean the issue likely exists for about a month, but what about before? I am saying so because I asked ..Copilot about the AWS outage where clearly states that since the problem was about DNS resolving, cloud providers should go on and flush DNS caches and so on - the resolution should be applied by both parties, not only Amazon.. Also, it could be that the outage went on  gradually, maybe for days, and this could be what Clearview witnessed

greets