#FlexibleLeverage for #MT5 updated to v1.36
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.36.0
- fixed mistake with NOP Groups and Logins field;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.FlexibleLeverage/1.36.0
#AMF plugin for #MT4 updated
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.AMF/1.22.0
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT4Plugin.AMF/1.22.0
#WebAPI updated to most recent version
MT4ManAPI.dll updated to v1415
https://cloud.mywebapi.com/History
Our downtime was : 30 seconds, equals to 99.9988799% SLA
99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
MT4ManAPI.dll updated to v1415
https://cloud.mywebapi.com/History
Our downtime was : 30 seconds, equals to 99.9988799% SLA
99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
CPlugin news
#WebAPI updated to most recent version MT4ManAPI.dll updated to v1415 https://cloud.mywebapi.com/History Our downtime was : 30 seconds, equals to 99.9988799% SLA 99.9% SLA (Microsoft Azure conditions) = 44 minutes per month of downtime allowed.
#AMF plugin for #MT5 updated
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.AMF/1.22.0
- bugfix related to TP restrictions;
https://nuget.cplugin.com/feeds/apps/CPlugin.MT5Plugin.AMF/1.22.0
#WebAPI IMPORTANT
tonight we run two more additional mirrors of WebAPI:
Hong-Kong
IP
London
IP
Your systems from regions above will get single digit latency value (in milliseconds).
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything else on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
tonight we run two more additional mirrors of WebAPI:
Hong-Kong
IP
103.252.117.172London
IP
83.229.68.30Your systems from regions above will get single digit latency value (in milliseconds).
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything else on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
cloud.mywebapi.comπ1
#Toolbox on staging got update.
Some of your assigned application forgot their settings.
https://pre.toolbox.cplugin.net
Some of your assigned application forgot their settings.
https://pre.toolbox.cplugin.net
#WebAPI IMPORTANT
new mirror run in Singapore
IP:
make sure you allow these IPs to connect to your MT4/MT5
No need to change anything on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
new mirror run in Singapore
IP:
5.223.43.1make sure you allow these IPs to connect to your MT4/MT5
103.252.117.17283.229.68.30194.233.70.35 - is out of service, forever. you can remove it from whitelists.No need to change anything on your side, traffic will be routed to closest to your origin mirror. To make it happen, always use address
cloud.mywebapi.com#WebAPI
today we are updating
Minimal interruptions should be during maintenance.
No actions required from your side. As we have bunch of mirrors, we update one after another without downtime.
today we are updating
auth.cplugin.net to serve requests faster using updated code and hardware.Minimal interruptions should be during maintenance.
No actions required from your side. As we have bunch of mirrors, we update one after another without downtime.
#WebAPI got major performance gain, in addition to Identity server.
Requests, addressed to pumping connection will be executed during 5ms.
Before, it was ~300ms.
Enjoy!
Requests, addressed to pumping connection will be executed during 5ms.
Before, it was ~300ms.
Enjoy!
#Toolbox major update on PROD
1. New architecture is going to be rolled out, expect outages on production toolbox until further notices.
Some features might not working.
bye, bye, legacy toolbox.cplugin.net
welcome new toolbox.cplugin.com. Still, most modules are not yet migrated.
2. Old staging at pre.toolbox.cplugin.net is going to be shut down soon.
upd: backend is shut down. no apps is going to run. Use new toolbox.cplugin.com to manage your apps.
Only UI is functional (plugins settings, general management, etc)
3. new staging will be here: pre.toolbox.cplugin.com
4. remember, you always have admin.cplugin.net and pre.admin.cplugin.net (staging) for basic management.
1. New architecture is going to be rolled out, expect outages on production toolbox until further notices.
Some features might not working.
bye, bye, legacy toolbox.cplugin.net
welcome new toolbox.cplugin.com. Still, most modules are not yet migrated.
2. Old staging at pre.toolbox.cplugin.net is going to be shut down soon.
upd: backend is shut down. no apps is going to run. Use new toolbox.cplugin.com to manage your apps.
Only UI is functional (plugins settings, general management, etc)
3. new staging will be here: pre.toolbox.cplugin.com
4. remember, you always have admin.cplugin.net and pre.admin.cplugin.net (staging) for basic management.
CPlugin news
#Toolbox major update on PROD 1. New architecture is going to be rolled out, expect outages on production toolbox until further notices. Some features might not working. bye, bye, legacy toolbox.cplugin.net welcome new toolbox.cplugin.com. Still, most modulesβ¦
#Toolbox - old sites are shut down permanently.
toolbox.cplugin.net replaced with toolbox.cplugin.com
pre.toolbox.cplugin.net replaced with pre.toolbox.cplugin.com
toolbox.cplugin.net replaced with toolbox.cplugin.com
pre.toolbox.cplugin.net replaced with pre.toolbox.cplugin.com
We have temporary outage. Very soon it will get back to work. No need to worry. matter of minutes.
CPlugin news
We have temporary outage. Very soon it will get back to work. No need to worry. matter of minutes.
Problem resolved. Thank you for patience and understanding!
Issue noted and appropriate actions will be applied.
Issue noted and appropriate actions will be applied.
β€1
We have updated our infrastructure, some serviced might not be available during period of 17:12 .. 17:26
π1
π₯2
#Toolbox (https://toolbox.cplugin.com)
Good morning, everyone. Earlier today we resolved an infrastructure incident that, over the past few days, may have been affecting you as slowness or intermittent app behaviour. The service is fully restored, and we've added safeguards to prevent a repeat. Thanks for bearing with us β and our apologies for the disruption π
Good morning, everyone. Earlier today we resolved an infrastructure incident that, over the past few days, may have been affecting you as slowness or intermittent app behaviour. The service is fully restored, and we've added safeguards to prevent a repeat. Thanks for bearing with us β and our apologies for the disruption π
π V2 API is in open beta β the full MT4 surface, end to end
We've been rebuilding the API on a faster, cleaner v2 foundation β and it now covers practically the entire MT4 ManagerAPI. Time to put it through its paces.
What's in the beta:
β’ Complete MT4 coverage β every practical ManagerAPI method is now a v2 endpoint (just one method can't be expressed over REST by design)
β’ One clean response shape β every call returns the same tidy JSON envelope (
β’ Version in the path β call
β’ Faster JSON β source-generated serialization, zero runtime reflection: lower latency and fewer allocations per response
β’ New realtime hub
v1 stays stable and fully supported β migrate at your own pace.
π Try it on Sandbox and browse the v2 docs: pre.mywebapi.com/redoc_v2
Tell us what breaks β that's what a beta is for.
We've been rebuilding the API on a faster, cleaner v2 foundation β and it now covers practically the entire MT4 ManagerAPI. Time to put it through its paces.
What's in the beta:
β’ Complete MT4 coverage β every practical ManagerAPI method is now a v2 endpoint (just one method can't be expressed over REST by design)
β’ One clean response shape β every call returns the same tidy JSON envelope (
data / error / meta) with a plain HTTP 200: read error instead of juggling status codes, parse one predictable structure every timeβ’ Version in the path β call
/api/v2/β¦ directly, no api-version query parameter to rememberβ’ Faster JSON β source-generated serialization, zero runtime reflection: lower latency and fewer allocations per response
β’ New realtime hub
/hubs/mt4/v2 β ticks, margins and trade events over SignalRv1 stays stable and fully supported β migrate at your own pace.
π Try it on Sandbox and browse the v2 docs: pre.mywebapi.com/redoc_v2
Tell us what breaks β that's what a beta is for.