tag:status.playtomic.com,2005:/history Playtomic Status - Incident history 2026-02-16T09:30:31.282+00:00 Playtomic tag:status.playtomic.com,2005:Incident/cmlp2ejd71dufp2a9kqrtewss 2026-02-16T09:30:31.282+00:00 2026-02-16T09:30:31.282+00:00 Chats feature at PT-Manager Type: Incident

Duration: 1 hour and 35 minutes

Affected Components: PT Manager

Feb 16, 09:30:31 GMT+0
Investigating - We are currently investigating this incident..

Feb 16, 10:00:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Feb 16, 10:50:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Feb 16, 11:05:29 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.playtomic.com,2005:Incident/cmljhxkhy0axthht9cqfnamj2 2026-02-12T08:40:00.000+00:00 2026-02-12T08:40:00.000+00:00 DNS resolution problem on manager.playtomic.io record Type: Incident

Duration: 50 minutes

Affected Components: PT Manager

Feb 12, 08:40:00 GMT+0
Investigating - The record has been accidentally deleted. Access to [manager.playtomic.io](http://manager.playtomic.io) is affected. Users who have not been able to resolve the DNS name will not be able to access it. Users who have somehow been served a cached DNS resolution, or even assets stored in their browser cache, may still experience a degraded user experience..

Feb 12, 09:08:00 GMT+0
Monitoring - The record has been created back. Because of how DNS propagation works, the fix will take several minutes to completely propagate to end-users..

Feb 12, 09:30:00 GMT+0
Resolved - We consider the issue fixed for all customers based on the metrics.

]]> tag:status.playtomic.com,2005:Incident/cmkqphwkl0ajb109yc5c51kx6 2026-01-23T08:30:17.637+00:00 2026-01-23T09:24:17.637+00:00 App Service Degradation Type: Incident

Duration: 54 minutes

Affected Components: Playtomic

Jan 23, 09:24:17 GMT+0
Resolved - This incident has been resolved..

Jan 23, 08:30:17 GMT+0
Identified - Users are reporting not being able to log in to the Playtomic APP.

]]> tag:status.playtomic.com,2005:Incident/cmkqpp0n40aq89fxzyt32ok36 2026-01-15T21:50:00.000+00:00 2026-01-15T22:10:00.000+00:00 Partial System degradation Type: Incident

Duration: 50 minutes

Affected Components: PT Manager

Jan 15, 22:10:00 GMT+0
Identified - The issue has been detected; Syltek's DB is not available. Playtomic Manager Clubs Operative is operating normally. We are continuing to work on a fix for this incident..

Jan 15, 22:40:00 GMT+0
Resolved - This incident has been resolved. All systems are stable..

Jan 15, 21:50:00 GMT+0
Investigating - Some clubs are reporting issues with accessing their management platform. Core operative (bookings, payments, matches) is not working in some clubs. We are currently investigating this incident..

]]> tag:status.playtomic.com,2005:Incident/cmkqqaeag0ax1109yvwqmqp5g 2026-01-14T21:25:00.000+00:00 2026-01-15T08:15:00.000+00:00 Users report difficulties when login via Playtomic App Type: Incident

Duration: 11 hours and 35 minutes

Affected Components: Playtomic

Jan 15, 08:15:00 GMT+0
Identified - We have identified the source of the issue and are working on a fix. Users affected <10% of the user base.

Jan 14, 21:25:00 GMT+0
Investigating - We are currently investigating this incident..

Jan 15, 09:00:00 GMT+0
Resolved - This incident has been resolved..

Jan 14, 22:15:00 GMT+0
Investigating - We are currently investigating this incident..

]]> tag:status.playtomic.com,2005:Incident/cmg5af9ay011a22bfayfka3f5 2025-09-29T14:00:56.964+00:00 2025-09-29T14:00:56.964+00:00 Courses partially unavailable in the application Type: Incident

Duration: 15 hours and 29 minutes

Affected Components: Academy

Sep 29, 14:00:56 GMT+0
Identified - We've detected stability issues with the course search function in our application. This functionality will remain disabled until the system is stable again. PT Manager and all other sections of the application are not affected..

Sep 29, 14:30:00 GMT+0
Monitoring - .

Sep 30, 05:30:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.playtomic.com,2005:Incident/cmfcej8zx004v8zjypuiwxus3 2025-09-09T09:40:00.000+00:00 2025-09-09T09:40:00.000+00:00 Booking process failed based on client's language Type: Incident

Duration: 25 minutes

Affected Components: Playtomic

Sep 9, 09:40:00 GMT+0
Identified - During the booking process, a system error occurred due to a mismatch between the client's language preference and the available language options..

Sep 9, 10:05:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.playtomic.com,2005:Incident/cmf5laafe007q13tvnd1l82jc 2025-09-04T13:50:00.000+00:00 2025-09-04T15:30:00.000+00:00 Partial degration of club search Type: Incident

Duration: 1 hour and 40 minutes

Affected Components: Playtomic.com

Sep 4, 15:30:00 GMT+0
Resolved - This incident has been resolved..

Sep 4, 13:50:00 GMT+0
Identified - Club search (<https://playtomic.com/search?q=Madrid>) unavailable due to improvements in the web caches..

]]> tag:status.playtomic.com,2005:Incident/cmeslppoo000v6a82cwwkzsy3 2025-08-25T19:10:00.000+00:00 2025-08-25T19:10:00.000+00:00 Academy Service Degradation Type: Incident

Duration: 2 hours and 30 minutes

Affected Components: Academy

Aug 25, 19:10:00 GMT+0
Identified - We experienced a partial service degradation affecting the Academy product. During this period, the service remained operational for most clubs, but some users faced reduced performance and functionality issues. Impact: The majority of clubs were able to continue using Academy without interruption. However, a subset of clubs encountered degraded functionality..

Aug 26, 06:50:00 GMT+0
Resolved - Resolution: Our team mitigated the issue and service is now stable. Next steps: We are investigating the root cause to prevent similar occurrences..

]]> tag:status.playtomic.com,2005:Incident/cme13zlsn00dvzufdswbxrega 2025-08-06T15:55:00.000+00:00 2025-08-06T15:55:00.000+00:00 Partial downtime in some clients due to DNS record recreation Type: Incident

Duration: 10 minutes

Affected Components: Playtomic

Aug 6, 15:55:00 GMT+0
Identified - An internal DNS record was recreated and some clients were unable to connect to the services. We need to wait until the new record is propagated to all the clients. This is only affecting the clients that don't have the DNS record cached..

Aug 6, 16:05:00 GMT+0
Resolved - This incident has been resolved and the new DNS record .

]]> tag:status.playtomic.com,2005:Incident/cmcubo3v0004ds52kq5cvogsg 2025-07-08T08:55:00.000+00:00 2025-07-08T08:55:00.000+00:00 PT Manager service disruption due to HTTPS record failure Type: Incident

Duration: 15 hours

Affected Components: PT Manager

Jul 8, 08:55:00 GMT+0
Identified - Several web clients, including PT Manager, could not connect to our API services. The error is connected to an optimization to solve HTTPS using DNS records via DNS..

Jul 8, 09:10:00 GMT+0
Resolved - This incident has been resolved..

]]> tag:status.playtomic.com,2005:Incident/cm9igwcsm003v9n5htnr9c1d2 2025-04-15T12:00:00.000+00:00 2025-04-15T12:30:00.000+00:00 Service disruption due to an error in a load balancer. Type: Incident

Duration: 1 day and 6 hours

Affected Components: Playtomic

Apr 15, 12:30:00 GMT+0
Resolved - As part of the previous operations, a load balancer was removed by mistake. After several deployments due to new functionality, those new deployments were inaccessible from the internet. Because the removal went unnoticed, subsequent rollouts silently failed..

Apr 15, 12:00:00 GMT+0
Investigating - We are currently investigating this incident..

]]> tag:status.playtomic.com,2005:Incident/cm9i7tetj000r13cynnlmupoz 2025-04-15T04:47:00.000+00:00 2025-04-15T05:30:00.000+00:00 Service disruption due to infrastructure update Type: Incident

Duration: 43 minutes

Affected Components: Playtomic

Apr 15, 05:30:00 GMT+0
Resolved - This incident has been resolved..

Apr 15, 04:47:00 GMT+0
Investigating - From 04:47 to 05:30 UTC, our service was completely unavailable due to a networking configuration issue introduced during a one-time infrastructure modernization effort. This update aimed to make our systems more replicable across multiple regions but unintentionally caused all services to become unreachable. The issue was identified and resolved, and full service was restored by 05:30 UTC..

]]>