Histórico de interrupções do Docraptor

1. 27 Here 2026 da 01:39 UTCinvestigating

   O nosso controlo alertou-nos para uma questão potencial. Estamos atualmente investigando e atualizaremos esse status conforme soubermos mais.

2. 27 Here 2026 da 01:40 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Here 2026 da 01:36 UTCinvestigating

   O nosso controlo alertou-nos para uma questão potencial. Estamos atualmente investigando e atualizaremos esse status conforme soubermos mais.

2. 27 Here 2026 da 01:37 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Meurzh 2026 da 12:34 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 8 Meurzh 2026 da 12:54 UTCresolved

   This incident has been resolved.

1. 21 Genver 2026 da 04:34 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 21 Genver 2026 da 04:43 UTCresolved

   This incident has been resolved.

1. 19 Genver 2026 da 20:56 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 19 Genver 2026 da 21:12 UTCresolved

   This incident has been resolved.

1. 19 Genver 2026 da 13:44 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 19 Genver 2026 da 13:48 UTCresolved

   This incident has been resolved.

1. 19 Genver 2026 da 01:07 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 19 Genver 2026 da 01:17 UTCresolved

   This incident has been resolved.

1. 18 Genver 2026 da 00:58 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 18 Genver 2026 da 01:50 UTCresolved

   This incident has been resolved.

1. 15 Genver 2026 da 00:35 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 15 Genver 2026 da 01:24 UTCresolved

   This incident has been resolved.

1. 12 Genver 2026 da 15:37 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 12 Genver 2026 da 16:19 UTCresolved

   This incident has been resolved.

1. 13 Du 2025 da 04:34 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 13 Du 2025 da 04:41 UTCresolved

   This incident has been resolved.

1. 11 Du 2025 da 18:11 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 11 Du 2025 da 18:35 UTCresolved

   This incident has been resolved.

1. 11 Du 2025 da 12:45 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 11 Du 2025 da 13:49 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 08:22 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 20 Here 2025 da 09:02 UTCresolved

   This incident has been resolved.

1. 2 Cʼhwevrer 2025 da 16:35 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 2 Cʼhwevrer 2025 da 16:40 UTCresolved

   This incident has been resolved.

1. 1 Genver 2025 da 08:15 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 1 Genver 2025 da 09:08 UTCresolved

   Our billing platform had an issue causing some users to see an "Over document limit" error. This has been resolved.

1. 4 Gouere 2024 da 21:19 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 4 Gouere 2024 da 21:24 UTCresolved

   This incident has been resolved.

1. 23 Mae 2024 da 15:58 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 23 Mae 2024 da 16:22 UTCresolved

   This incident has been resolved.

1. 15 Kerzu 2023 da 04:18 UTCresolved

   A few minutes ago, we were forced to switch from our primary to our standby database. No data was lost, but document production was affected for approximately 75 seconds. The secondary database took over just like it supposed to, and all systems are running normally now. We work hard to make sure that Doc Raptor outages are extremely rare and as brief as possible, and are sorry, if this impacted you.

1. 11 Kerzu 2023 da 08:44 UTCinvestigating

   Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.

2. 11 Kerzu 2023 da 09:59 UTCresolved

   This incident has been resolved.