- Detected by Pingoru
- Sep 26, 2026, 07:38 AM UTC
- Resolved
- Oct 05, 2026, 12:10 PM UTC
- Duration
- 9d 4h
Affected: Platform Connectors (Tradovate Connector)
Timeline · 1 update
-
identified Sep 26, 2026, 07:38 AM UTC
Tradovate underwent maintenance which temporarily prevented us from refreshing authentication tokens for connected accounts. As a result, some Tradovate profiles have been disconnected and will require re-authentication before trading functionality can resume. If your Tradovate account is affected, please reconnect it from Traders Connect. We’re continuing to monitor the integration and are reviewing ways to reduce the impact of similar maintenance events in the future.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2026, 05:53 PM UTC
- Resolved
- Sep 16, 2026, 06:02 AM UTC
- Duration
- 9d 12h
Affected: Platform Connectors (MatchTrader Connector)Third Party (MatchTrader API)
Timeline · 3 updates
-
identified Sep 06, 2026, 05:53 PM UTC
We have identified a connectivity issue affecting MatchTrader accounts with some prop firms. The issue appears to be related to the MatchTrader API/integration layer. We are working closely with the relevant team to identify the exact cause and resolve the issue as soon as possible. MatchTrader accounts with other prop firms and our other broker integrations are currently unaffected. We will provide further updates as we make progress.
-
identified Sep 11, 2026, 11:21 AM UTC
We are continuing to work closely with the Match-Trader team to resolve this issue. We are pleased to report that progress is being made, and Match-Trader have informed us that they expect to resolve their connectivity issues in the coming days. Thank you for your continued patience.
-
monitoring Sep 16, 2026, 03:08 AM UTC
MatchTrader has deployed a fix, and connectivity has now been restored for the affected accounts. We are continuing to monitor the service closely to ensure everything remains stable. Thank you for your patience while this was being resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2026, 03:50 AM UTC
- Resolved
- Aug 05, 2026, 01:24 PM UTC
- Duration
- 4d 9h
Affected: Platform Connectors (Tradovate Connector)
Timeline · 4 updates
-
investigating Aug 01, 2026, 03:50 AM UTC
Tradovate’s token refresh service experienced an upstream interruption, causing existing profile authentication tokens to expire and connected Tradovate accounts to be disconnected. The token refresh service is now operational; however, affected users must reconnect and re-authenticate their Tradovate accounts to restore the connection. We are continuing to monitor the situation.
-
identified Aug 05, 2026, 05:03 AM UTC
We are continuing to work on a fix for this incident.
-
monitoring Aug 05, 2026, 01:24 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Aug 05, 2026, 01:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 08:37 PM UTC
- Resolved
- Jul 01, 2026, 10:23 AM UTC
- Duration
- 1d 13h
Affected: Third Party (cTrader API)
Timeline · 3 updates
-
identified Jun 29, 2026, 08:37 PM UTC
We've traced this to an issue on cTrader's side affecting the account authorization flow for new connections. This is outside of our platform's control. We've reported it to cTrader (Spotware) support, and their team is actively investigating a fix. Existing connections and copy configurations are unaffected.
-
monitoring Jul 01, 2026, 07:13 AM UTC
The Ctrader team has implemented a fix and is currently monitoring the result.
-
resolved Jul 01, 2026, 10:23 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 12:08 PM UTC
- Resolved
- Jun 29, 2026, 02:51 PM UTC
- Duration
- 2h 43m
Affected: Third Party (TradeLocker API | Live)Third Party (TradeLocker API | Demo)Platform Connectors (TradeLocker Connector)
Timeline · 2 updates
-
identified Jun 29, 2026, 12:08 PM UTC
We're seeing Tradelocker API issues for a very small number of accounts beyond our control. The development team has informed the Tradelocker team and is waiting for a response.
-
resolved Jun 29, 2026, 02:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 06:44 PM UTC
- Resolved
- Apr 22, 2026, 07:05 PM UTC
- Duration
- 21m
Affected: Traders ConnectBackend (Web App)Frontend (Web App)
Timeline · 3 updates
-
investigating Apr 22, 2026, 06:44 PM UTC
We are currently investigating this incident.
-
monitoring Apr 22, 2026, 06:54 PM UTC
Auth0 have implemented a fix and are currently monitoring the result.
-
resolved Apr 22, 2026, 07:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 08:30 AM UTC
- Resolved
- Apr 07, 2026, 08:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 07, 2026, 08:30 AM UTC
Type: Incident Duration: 5 days and 53 minutes Affected Components: cTrader Connector Apr 7, 08:30:00 GMT+0 - Identified - We're seeing intermittent cTrader API issues beyond out control. The development team have informed cTrader support and are waiting for a response. Apr 10, 09:15:00 GMT+0 - Identified - cTrader deployed a fix which caused their API to disconnect globally, not only for Traders Connect. We're awaiting further information. Apr 12, 09:22:55 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 08:22 AM UTC
- Resolved
- Mar 16, 2026, 08:22 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 02:58 PM UTC
- Resolved
- Feb 24, 2026, 02:58 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 24, 2026, 02:58 PM UTC
Type: Incident Duration: 2 hours and 47 minutes Affected Components: TradeLocker Connector Feb 24, 14:58:45 GMT+0 - Investigating - We’re seeing issues with the Tradelocker API due to an incident on their side. For further information please reach out to Tradelocker directly. We are currently monitoring the situation. Feb 24, 17:46:11 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 04:25 PM UTC
- Resolved
- Jan 19, 2026, 04:25 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 19, 2026, 04:25 PM UTC
Type: Incident Duration: 59 minutes Affected Components: TradeLocker Connector Jan 19, 16:25:03 GMT+0 - Investigating - We are currently investigating this incident. Jan 19, 17:23:50 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 12:47 AM UTC
- Resolved
- Jan 13, 2026, 12:47 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 13, 2026, 12:47 AM UTC
Type: Incident Duration: 7 hours and 25 minutes Affected Components: cTrader Connector Jan 13, 00:47:18 GMT+0 - Identified - We're seeing issues on the cTrader API currently, this issue comes from cTrader's side. We have informed their support team and are currently waiting for an update. Jan 13, 08:12:13 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 02:52 PM UTC
- Resolved
- Dec 11, 2025, 02:52 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 11, 2025, 02:52 PM UTC
Type: Incident Duration: 1 hour and 28 minutes Affected Components: Internal API Dec 11, 16:19:55 GMT+0 - Resolved - This incident has been resolved. Dec 11, 14:52:13 GMT+0 - Investigating - We're currently seeing delays with our analytics data. These delays are impacting analytics only, not the trade copier. Dec 11, 15:28:52 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 11:30 PM UTC
- Resolved
- Dec 10, 2025, 11:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 10, 2025, 11:30 PM UTC
Type: Incident Duration: 12 hours and 8 minutes Affected Components: MetaTrader 5, MetaTrader 4 Dec 11, 11:38:46 GMT+0 - Resolved - This incident has been resolved. Dec 10, 23:30:55 GMT+0 - Investigating - We're seeing an increased rate of account connection errors since swap ours. Our development team are working on the issue. Dec 11, 00:35:21 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:02 AM UTC
- Resolved
- Dec 05, 2025, 09:02 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 05, 2025, 09:02 AM UTC
Type: Incident Duration: 31 minutes Affected Components: Support Channels Dec 5, 09:02:52 GMT+0 - Investigating - We're currently seeing an issue with our Live Chat software due to an outage at Cloudflare. Dec 5, 09:05:18 GMT+0 - Identified - The issue is due to a Cloudflare outage beyond our control. We're waiting for the service to resume. Dec 5, 09:19:41 GMT+0 - Monitoring - Cloudflare appears to have recovered and our live chat services are working again. Dec 5, 09:33:37 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 12:21 PM UTC
- Resolved
- Nov 06, 2025, 12:21 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 06, 2025, 12:21 PM UTC
Type: Incident Duration: 22 hours and 33 minutes Affected Components: TradeLocker Connector Nov 6, 12:21:00 GMT+0 - Investigating - **Incident Summary:** We are currently experiencing issues with our TradeLocker BETA connectors. **Current Status:** The issue has been identified as originating from TradeLocker’s side. Our team has already contacted TradeLocker Support and we are awaiting their response. We will continue to monitor the situation closely and provide updates as soon as more information becomes available. Nov 6, 15:57:27 GMT+0 - Monitoring - The situation with Tradelocker has improved, we're monitoring the performance closely. Nov 7, 10:53:59 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2025, 08:29 AM UTC
- Resolved
- Sep 17, 2025, 08:29 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 17, 2025, 08:29 AM UTC
Type: Incident Duration: 2 hours and 7 minutes Affected Components: MetaTrader 5 Sep 17, 08:29:55 GMT+0 - Investigating - We're seeing reports of MT5 trades failing to copy, the developers are investigating the root cause. Sep 17, 09:51:43 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 17, 10:36:27 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 12:44 AM UTC
- Resolved
- Jul 23, 2025, 12:44 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 23, 2025, 12:44 AM UTC
Type: Incident Duration: 4 minutes Affected Components: TradeLocker Connector Jul 23, 00:48:09 GMT+0 - Resolved - This incident has been resolved. Jul 23, 00:44:23 GMT+0 - Investigating - We're currently seeing issues connecting accounts on our TradeLocker BETA connector. This is affecting users who have connected TradeLocker accounts to the BETA connector for master use. The issue is coming from TradeLockers side, we have informed their support team and we're waiting for a response. As soon as their service recovers the accounts will be reconnected. Jul 23, 00:46:10 GMT+0 - Monitoring - TradeLocker BETA accounts are now connected again. We're monitoring the situation closely.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2025, 08:00 AM UTC
- Resolved
- Jul 19, 2025, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 19, 2025, 08:00 AM UTC
Type: Maintenance Duration: 5 hours Affected Components: Web App, Internal API Jul 19, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 19, 08:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 19, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 06:01 AM UTC
- Resolved
- Jul 02, 2025, 06:01 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 02, 2025, 06:01 AM UTC
Type: Incident Duration: 2 hours and 8 minutes Jul 2, 06:01:00 GMT+0 - Investigating - We're seeing a high rate of account connection errors. We're currently investigating. Jul 2, 07:50:54 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 2, 07:25:59 GMT+0 - Identified - This incident is affecting a small number of MetaTrader dediccated environments. Our team are still working to resolve the issue. Jul 2, 08:08:50 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 04:36 PM UTC
- Resolved
- Jun 23, 2025, 04:36 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 06:11 AM UTC
- Resolved
- Jun 10, 2025, 06:11 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 10, 2025, 06:11 AM UTC
Type: Incident Duration: 2 hours and 3 minutes Jun 10, 07:19:15 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 10, 06:11:32 GMT+0 - Investigating - We are currently investigating some connection errors affecting a small number of MT4 and MT5 accounts. Jun 10, 06:42:09 GMT+0 - Identified - The developers have identified the issue and we're working on a fix. Jun 10, 08:14:02 GMT+0 - Resolved - The incident is now resolved. We experienced a connectivity issue due to a loss of connection to two of our core switches at the Equinix datacenter. This resulted in some nodes losing internet connectivity. Our team responded immediately and migrated affected nodes to our backup core network. Connectivity has since been restored and remains stable. We are actively working with Equinix to identify the root cause of the core switch failure and will provide further updates as necessary. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 03:42 PM UTC
- Resolved
- Jun 03, 2025, 03:42 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 03, 2025, 03:42 PM UTC
Type: Incident Duration: 49 minutes Affected Components: Internal API Jun 3, 15:42:13 GMT+0 - Investigating - We’re currently experiencing delays in our Internal Trade Retry system. Our engineering team is actively investigating and working to restore normal performance. All other services remain operational. We’ll provide the next update within 30 minutes or as soon as we have more information. Jun 3, 16:18:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 3, 16:30:46 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 01:53 PM UTC
- Resolved
- Jun 03, 2025, 01:53 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 03, 2025, 01:53 PM UTC
Type: Incident Duration: 2 hours and 38 minutes Jun 3, 13:53:03 GMT+0 - Investigating - We're seeing IC Markets MT5 servers currently down, this is affecting many users who have accounts on IC Markets. Please reach out to IC Markets directly with questions. Jun 3, 13:53:30 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 3, 14:23:17 GMT+0 - Resolved - This incident has been resolved. Jun 3, 15:39:11 GMT+0 - Identified - We're still seeing a large number of connection issues to IC Markets servers. The developers are monitoring. Jun 3, 16:30:59 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 10:19 AM UTC
- Resolved
- May 23, 2025, 10:19 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2025, 07:00 AM UTC
- Resolved
- Apr 12, 2025, 07:00 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →