Inscribe had 20 outages in the last 2 years totaling 89487h 45m of downtime — averaging 0.8 incidents per month.
There were 20 Inscribe outages since March 6, 2025 totaling 89487h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring the results.
All documents that were affected by this incident have been reprocessed. Webhooks with the complete document response have been resent.
Apr 15, 09:10 UTC Resolved - This incident has been resolved. Apr 15, 08:55 UTC Identified - The issue has been identified and a fix is being implemented.
Apr 13, 18:07 UTC Resolved - This incident has been resolved. Apr 13, 17:18 UTC Monitoring - The earlier issues have been resolved and latency is close to normal expected ranges - we're still monitoring and will update when processing has fully returned to normal. Apr 13, 14:56 UTC Investigating - Increased latency and some processing failures. We are currently investigating the issue.
Web search enabled features were temporarily degraded and have been restored. Regular fraud detection was not affected.
For 3 minutes between 08:54 and 08:57 UTC (00:54–00:57 PT), a small number of API requests returned HTTP 500 errors, impacting some customer creation and document upload requests.
Feb 17, 18:39 UTC Resolved - This incident has been resolved. Feb 17, 18:13 UTC Monitoring - A fix has been applied and document processing times have mostly returned to normal. We're monitoring to ensure the issue is fixed. Feb 17, 18:04 UTC Investigating - We are currently experiencing increased latency and investigating the issue.
Feb 11, 11:37 UTC Resolved - This incident has been resolved. Feb 11, 11:08 UTC Monitoring - A fix has been applied and document processing times have mostly returned to normal. We're monitoring to ensure the issue is fixed. Feb 11, 10:57 UTC Investigating - We are currently investigating decreased latency in the document processing pipeline.
Jan 5, 21:49 UTC Resolved - This incident has been resolved. Jan 5, 20:47 UTC Monitoring - Document processing was delayed - this should now be resolved and we are monitoring to ensure normal document processing times resume.
Nov 18, 15:01 UTC Resolved - The Cloudflare outage is mostly resolved now and our Trust Center is back up and running. Nov 18, 13:49 UTC Identified - Our Trust Center is inaccessible due to the ongoing Cloudflare outage.
Oct 21, 07:36 UTC Resolved - AWS has resolved this issue now so we can move out of monitoring to resolved. Oct 20, 20:33 UTC Update - Document processing statuses were not updating in the Inscribe app in the last 2 hours. UI users would have needed to refresh the page to see the latest statuses. API users were unaffected. All systems are operational as of 12:52 PM PT. Oct 20, 15:38 UTC Update - We have not observed any further problems with our systems but are continuing to monitor. Oct 20, 12:08 UTC Update - All of our services are operational but we are continuing to monitor until the upstream issues with AWS have satisfactory resolved. Oct 20, 09:54 UTC Update - Doc Processing times recovered. Help Center is back up. We will stay monitoring until the AWS incident is marked as fully resolved. Oct 20, 09:18 UTC Monitoring - These issues are due to the AWS outage and related side-effects. We are monitoring closely and will provide updates here.
Oct 8, 16:39 UTC Resolved - Our API and app were down from 15:32 to 15:48 UTC. Customer impact: API Customers received 5XX and 4XX errors during this period. UI users were not able to log in. These issues are now resolved. (edited) Oct 8, 16:16 UTC Monitoring - API is back up. Documents are processing as expected. We are continuing to monitor. Oct 8, 16:00 UTC Investigating - API was briefly down - we are monitoring and investigating.
Aug 20, 18:03 UTC Resolved - This incident has been resolved. Aug 20, 16:25 UTC Monitoring - Recovering now. Aug 20, 15:36 UTC Identified - The issue has been identified and a fix is being implemented.
Aug 14, 09:46 UTC Resolved - Document processing latency was degraded between 08:42 and 09:32 UTC. Aug 14, 09:37 UTC Monitoring - A fix has been implemented and we are monitoring the results.
Aug 11, 17:22 UTC Resolved - This incident has been resolved and web search is back to regular performance. Aug 11, 17:18 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 11, 15:54 UTC Investigating - We are currently experiencing degraded performance due to an outage from a third-party service provider we rely on for web search. Document processing is not affected. We are actively monitoring the situation and will update this page as soon as the provider has resolved the issue.
Jul 8, 22:30 UTC Resolved - This incident has been resolved. Jul 7, 22:29 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul 7, 20:52 UTC Investigating - We have noticed there are a small number of documents are not successfully processing. You will see an error stating: "An error occurred while processing this document. Inscribe has been notified." in the Inscribe app. We are investigating the cause and will update shortly. Thanks for your patience.
Jul 1, 00:13 UTC Resolved - This incident has been resolved. Jun 30, 22:12 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 30, 21:33 UTC Investigating - We are currently investigating this issue.
Jun 9, 08:45 UTC Resolved - This incident has been resolved. Jun 9, 08:30 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 9, 08:18 UTC Identified - Document processing times are currently experiencing delays and webhooks are not being sent for some documents
Apr 2, 16:36 UTC Resolved - This incident has been resolved. Apr 2, 16:06 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 2, 15:45 UTC Investigating - We are currently investigating this issue.
Mar 10, 14:44 UTC Resolved - This incident has been resolved. Mar 10, 14:33 UTC Monitoring - Fix applied. API recovering Mar 10, 14:32 UTC Update - We are continuing to investigate this issue. Mar 10, 14:32 UTC Investigating - We are currently investigating this issue.
Mar 6, 17:00 UTC Resolved - We investigated and fixed an issue causing degraded document processing times for some customers