История сбоев Docraptor

1. 27 октября 2026 г. в 01:39 UTCinvestigating

   Наш мониторинг предупредил нас о потенциальной проблеме. В настоящее время мы расследуем и обновим этот статус, когда узнаем больше.

2. 27 октября 2026 г. в 01:40 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 27 октября 2026 г. в 01:36 UTCinvestigating

   Наш мониторинг предупредил нас о потенциальной проблеме. В настоящее время мы расследуем и обновим этот статус, когда узнаем больше.

2. 27 октября 2026 г. в 01:37 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 8 марта 2026 г. в 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 марта 2026 г. в 12:54 UTCresolved

   This incident has been resolved.

1. 21 января 2026 г. в 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 января 2026 г. в 04:43 UTCresolved

   This incident has been resolved.

1. 19 января 2026 г. в 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 января 2026 г. в 21:12 UTCresolved

   This incident has been resolved.

1. 19 января 2026 г. в 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 января 2026 г. в 13:48 UTCresolved

   This incident has been resolved.

1. 19 января 2026 г. в 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 января 2026 г. в 01:17 UTCresolved

   This incident has been resolved.

1. 18 января 2026 г. в 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 января 2026 г. в 01:50 UTCresolved

   This incident has been resolved.

1. 15 января 2026 г. в 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 января 2026 г. в 01:24 UTCresolved

   This incident has been resolved.

1. 12 января 2026 г. в 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 января 2026 г. в 16:19 UTCresolved

   This incident has been resolved.

1. 13 ноября 2025 г. в 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 ноября 2025 г. в 04:41 UTCresolved

   This incident has been resolved.

1. 11 ноября 2025 г. в 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 ноября 2025 г. в 18:35 UTCresolved

   This incident has been resolved.

1. 11 ноября 2025 г. в 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 ноября 2025 г. в 13:49 UTCresolved

   This incident has been resolved.

1. 20 октября 2025 г. в 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 октября 2025 г. в 09:02 UTCresolved

   This incident has been resolved.

1. 2 февраля 2025 г. в 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 февраля 2025 г. в 16:40 UTCresolved

   This incident has been resolved.

1. 1 января 2025 г. в 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 января 2025 г. в 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 июля 2024 г. в 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 июля 2024 г. в 21:24 UTCresolved

   This incident has been resolved.

1. 23 мая 2024 г. в 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 мая 2024 г. в 16:22 UTCresolved

   This incident has been resolved.

1. 15 декабря 2023 г. в 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 декабря 2023 г. в 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 декабря 2023 г. в 09:59 UTCresolved

   This incident has been resolved.