- Detected by Pingoru
- Oct 20, 2026, 06:40 AM UTC
- Resolved
- Oct 20, 2026, 08:42 PM UTC
- Duration
- 14h 2m
Affected: Backend (Web App)Frontend (Web App)
Timeline · 4 updates
-
investigating Oct 20, 2026, 06:40 AM UTC
We are currently experiencing an issue with our cloud provider that is affecting analytics services. We are investigating the issue and working to restore normal functionality as soon as possible. We apologize for any inconvenience and appreciate your patience.We are currently investigating this incident.
-
identified Oct 20, 2026, 09:01 AM UTC
We have identified the issue as a Google Cloud Platform (GCP) outage affecting our analytics services. Services have been restored, but some trade analytics data may remain out of sync. Our team is working to resolve any remaining discrepancies.
-
monitoring Oct 20, 2026, 09:03 AM UTC
Our analytics services experienced a complete outage due to issues with Google Cloud Platform (GCP), which reported disruptions across multiple services on its status page. We have restored our services, but some trade analytics data may not yet be fully synced. If you notice any discrepancies, please contact our support team to resync the affected account. We apologize for the inconvenience caused by this GCP outage and appreciate your patience while we address any remaining data synchronization issues.
-
resolved Oct 20, 2026, 08:42 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 08:22 AM UTC
- Resolved
- Mar 16, 2026, 08:22 AM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 02:58 PM UTC
- Resolved
- Feb 24, 2026, 02:58 PM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 04:25 PM UTC
- Resolved
- Jan 19, 2026, 04:25 PM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 12:47 AM UTC
- Resolved
- Jan 13, 2026, 12:47 AM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 02:52 PM UTC
- Resolved
- Dec 11, 2025, 02:52 PM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 11:30 PM UTC
- Resolved
- Dec 10, 2025, 11:30 PM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:02 AM UTC
- Resolved
- Dec 05, 2025, 09:02 AM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 12:21 PM UTC
- Resolved
- Nov 06, 2025, 12:21 PM UTC
- Duration
- —
Affected: Traders Connect
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2025, 08:29 AM UTC
- Resolved
- Sep 17, 2025, 08:29 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 12:44 AM UTC
- Resolved
- Jul 23, 2025, 12:44 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2025, 08:00 AM UTC
- Resolved
- Jul 19, 2025, 08:00 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 06:01 AM UTC
- Resolved
- Jul 02, 2025, 06:01 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 04:36 PM UTC
- Resolved
- Jun 23, 2025, 04:36 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 06:11 AM UTC
- Resolved
- Jun 10, 2025, 06:11 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 03:42 PM UTC
- Resolved
- Jun 03, 2025, 03:42 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 01:53 PM UTC
- Resolved
- Jun 03, 2025, 01:53 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 10:19 AM UTC
- Resolved
- May 23, 2025, 10:19 AM UTC
- Duration
- —
Read the full incident report →