Historical record of incidents for DocRaptor
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateOur billing platform had an issue causing some users to see an "Over document limit" error. This has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Primary Database Failover"
Last updateA 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.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateAn unusually high request load resulted in some slowdowns in document creation for a period of approximately 20 minutes. We have added additional capacity to the system to handle the workload and will continue to monitor the situation and increase capacity further if necessary.
This incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
We were forced to switch from our primary to our standby database. While no data was lost, document production was affected for a 1-2 minutes. The secondary database took over just like it supposed to, and all systems are running normally now. We're continuing to monitor to ensure there are no further issues.
Our monitoring has alerted us to an issue. We are currently investigating and will update this status as we learn more.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
We have detected an issue with a backend bookkeeping system, but there should be no impact to the DocRaptor API or website at this time.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved. Hardware failure resolved by moving workload.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateAutomatic failover was unsuccessful, but manual hardware replacement resolved the issue.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateMomentary hardware failure resolved by automatic failover.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateA momentary hardware issue has been resolved. A small number of docs in flight may have failed, but retrying would immediately succeed.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateDocRaptor has been restored to normal functionality, with API functionality restored as of 12:24 EST (around 2 hours ago). AWS is not yet fully restored, so we continue to monitor closely and ensure our backup facilities are ready for additional issues.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.
Report: "Investigating Alerts"
Last updateThis incident has been resolved.
AWS is having a significant issues, including the inability to log in.
Our monitoring has alerted us to a potential issue. We are currently investigating and will update this status as we learn more.