Historial de interrupciones de Cexio

1. 26 de junio de 2026 a las 11:03 UTCinvestigating

   We are currently investigating this issue.

2. 26 de junio de 2026 a las 12:02 UTCresolved

   This incident has been resolved.

1. 25 de junio de 2026 a las 17:20 UTCinvestigating

   We are currently investigating this issue.

2. 26 de junio de 2026 a las 6:45 UTCresolved

   This incident has been resolved.

1. 25 de junio de 2026 a las 13:04 UTCinvestigating

   We are currently supporting the TON to GRAM token migration. For step-by-step instructions and important details, please refer to our Help Center article https://support.cex.io/en/articles/15554208-announcement-regarding-toncoin-ton-migration-to-gram-gram

2. 13 de julio de 2026 a las 10:57 UTCresolved

   This incident has been resolved.

1. 24 de junio de 2026 a las 8:42 UTCinvestigating

   We are currently investigating this issue.

2. 24 de junio de 2026 a las 11:16 UTCresolved

   This incident has been resolved.

1. 9 de junio de 2026 a las 9:35 UTCinvestigating

   We are currently investigating this issue.

2. 10 de junio de 2026 a las 8:28 UTCresolved

   This incident has been resolved.

1. 8 de junio de 2026 a las 10:53 UTCinvestigating

   We are currently investigating this issue.

2. 8 de junio de 2026 a las 10:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

1. 1 de junio de 2026 a las 8:02 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 14 de julio de 2026 a las 13:22 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de mayo de 2026 a las 11:16 UTCinvestigating

   We are currently investigating this issue.

2. 23 de junio de 2026 a las 8:50 UTCresolved

   This incident has been resolved.

1. 25 de mayo de 2026 a las 13:41 UTCinvestigating

   We are currently investigating this issue.

2. 25 de mayo de 2026 a las 16:51 UTCresolved

   This incident has been resolved.

1. 1 de mayo de 2026 a las 8:57 UTCinvestigating

   We are currently investigating this issue.

2. 1 de mayo de 2026 a las 9:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 1 de mayo de 2026 a las 10:24 UTCresolved

   This incident has been resolved.

1. 29 de abril de 2026 a las 8:40 UTCinvestigating

   We are currently investigating this issue.

2. 4 de mayo de 2026 a las 8:19 UTCresolved

   This incident has been resolved.

1. 24 de abril de 2026 a las 9:00 UTCinvestigating

   We are currently investigating this issue.

2. 24 de abril de 2026 a las 9:22 UTCresolved

   This incident has been resolved.

1. 9 de abril de 2026 a las 14:05 UTCinvestigating

   We are currently investigating this issue.

2. 22 de abril de 2026 a las 14:33 UTCresolved

   This incident has been resolved.

1. 5 de marzo de 2026 a las 17:37 UTCinvestigating

   We are currently investigating this issue.

2. 1 de abril de 2026 a las 16:36 UTCresolved

   Swift transfers have been retired.

1. 4 de marzo de 2026 a las 7:59 UTCinvestigating

   We are currently investigating this issue.

2. 20 de marzo de 2026 a las 14:32 UTCresolved

   This incident has been resolved.

1. 25 de febrero de 2026 a las 15:30 UTCinvestigating

   We are currently investigating this issue.

2. 25 de febrero de 2026 a las 16:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 25 de febrero de 2026 a las 18:30 UTCresolved

   This incident has been resolved.

1. 23 de febrero de 2026 a las 11:58 UTCinvestigating

   We are currently investigating this issue.

2. 23 de febrero de 2026 a las 12:35 UTCresolved

   This incident has been resolved.

1. 18 de febrero de 2026 a las 14:42 UTCinvestigating

   We are currently investigating this issue.

2. 18 de febrero de 2026 a las 14:55 UTCresolved

   This incident has been resolved.

1. 16 de febrero de 2026 a las 12:49 UTCinvestigating

   We are currently investigating this issue.

2. 4 de marzo de 2026 a las 13:03 UTCresolved

   This incident has been resolved.

1. 15 de febrero de 2026 a las 13:00 UTCinvestigating

   We are currently investigating this issue.

2. 16 de febrero de 2026 a las 7:44 UTCresolved

   This incident has been resolved.