Mathpix Status - Incident history https://status.mathpix.com Mathpix Tue, 24 Mar 2026 22:07:00 +0000 v3/text Disruption Type: Incident Duration: 16 minutes Affected Components: OCR API (us-east-1), OCR API (eu-central-1), OCR API (ap-southeast-1) Mar 24, 22:07:00 GMT+0 - Investigating - We are investigating an issue affecting v3/text in us-east-1 and eu-central-1\. API requests may be returning errors or timeouts. Mar 24, 22:15:00 GMT+0 - Identified - The issue in us-east-1 and eu-central-1 has been resolved. Failover traffic has caused degraded v3/text performance in ap-southeast-1\. We are actively working to resolve this. Mar 24, 22:23:00 GMT+0 - Resolved - All services are fully restored across all regions. Total incident duration was approximately 16 minutes. Type: Incident

Duration: 16 minutes

Affected Components: , ,

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:07:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating an issue affecting v3/text in us-east-1 and eu-central-1\. API requests may be returning errors or timeouts..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:15:00</var> GMT+0</small><br><strong>Identified</strong> - The issue in us-east-1 and eu-central-1 has been resolved. Failover traffic has caused degraded v3/text performance in ap-southeast-1\. We are actively working to resolve this..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:23:00</var> GMT+0</small><br><strong>Resolved</strong> - All services are fully restored across all regions. Total incident duration was approximately 16 minutes. .</p> ]]> Tue, 24 Mar 2026 22:07:00 +0000 https://status.mathpix.com/incident/cmn57s3gs03sm1jv0c0yy9p1m https://status.mathpix.com/incident/cmn57s3gs03sm1jv0c0yy9p1m OCR API Disruption Type: Incident Duration: 1 day and 5 hours Affected Components: OCR API (ap-southeast-1), OCR API (eu-central-1), OCR API (us-east-1) Mar 20, 12:52:00 GMT+0 - Investigating - We are investigating an issue affecting v3/text, v3/pdf, and v3/batch across all regions. API requests may be returning errors or timeouts. Live status: [monitor.mathpix.com](http://monitor.mathpix.com) Mar 20, 12:59:00 GMT+0 - Identified - Global impact has been resolved. We have identified a secondary issue in ap-southeast-1 caused by v3/pdf failover traffic. Customers using v3/text in ap-southeast-1, and some v3/pdf customers whose traffic was routed to that region, may still be experiencing errors. We are actively working to resolve this. Mar 20, 13:21:00 GMT+0 - Resolved - All services are fully restored across all regions. We are conducting a root cause analysis and will implement safeguards to prevent recurrence. Type: Incident

Duration: 1 day and 5 hours

Affected Components: , ,

<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>12:52:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating an issue affecting v3/text, v3/pdf, and v3/batch across all regions. API requests may be returning errors or timeouts. Live status: [monitor.mathpix.com](http://monitor.mathpix.com).</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>12:59:00</var> GMT+0</small><br><strong>Identified</strong> - Global impact has been resolved. We have identified a secondary issue in ap-southeast-1 caused by v3/pdf failover traffic. Customers using v3/text in ap-southeast-1, and some v3/pdf customers whose traffic was routed to that region, may still be experiencing errors. We are actively working to resolve this..</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>13:21:00</var> GMT+0</small><br><strong>Resolved</strong> - All services are fully restored across all regions. We are conducting a root cause analysis and will implement safeguards to prevent recurrence..</p> ]]> Fri, 20 Mar 2026 12:52:00 +0000 https://status.mathpix.com/incident/cmmyyuhbg003o1rtjlm7079h1 https://status.mathpix.com/incident/cmmyyuhbg003o1rtjlm7079h1 OCR API availability issues Type: Incident Duration: 28 minutes Affected Components: OCR API (eu-central-1), OCR API (ap-southeast-1), Snip, OCR API (us-east-1) Dec 27, 07:14:00 GMT+0 - Investigating - We are investigating an issue causing intermittent errors and elevated latency for OCR API requests across multiple regions. Some OCR API requests may fail or time out during this period. Dec 27, 07:42:00 GMT+0 - Resolved - The issue has been resolved and OCR API requests are now processing normally. We will continue monitoring system health. Live status is available at <https://monitor.mathpix.com/>. Type: Incident

Duration: 28 minutes

Affected Components: , , ,

<p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>07:14:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating an issue causing intermittent errors and elevated latency for OCR API requests across multiple regions. Some OCR API requests may fail or time out during this period..</p> <p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>07:42:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue has been resolved and OCR API requests are now processing normally. We will continue monitoring system health. Live status is available at <https://monitor.mathpix.com/>..</p> ]]> Sat, 27 Dec 2025 07:14:00 +0000 https://status.mathpix.com/incident/cmjo0b3us019p44toog89wpq6 https://status.mathpix.com/incident/cmjo0b3us019p44toog89wpq6 PDF API performance issues Type: Incident Duration: 2 hours and 16 minutes Affected Components: Snip, OCR API (us-east-1) Oct 20, 07:11:00 GMT+0 - Identified - We have identified an issue affecting the PDF API due to an ongoing AWS outage impacting services in the US-East-1 region. Customers may experience elevated error rates or failed requests. We are actively monitoring the situation and working to restore normal operation as quickly as possible. Further updates will be provided as more information becomes available. **More details on affected services at:** [https://monitor.mathpix.com/.](https://monitor.mathpix.com/) Oct 20, 09:27:00 GMT+0 - Resolved - This incident has been resolved. AWS services in the US-East-1 region have recovered, and we are no longer observing errors or elevated latency for the PDF API. We are continuing to investigate why traffic was not automatically routed to other regions during the outage and are working to ensure our failover mechanisms handle similar events more effectively in the future. All systems are operating normally at this time. More details on affected services at: <https://monitor.mathpix.com/> . Type: Incident

Duration: 2 hours and 16 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>07:11:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified an issue affecting the PDF API due to an ongoing AWS outage impacting services in the US-East-1 region. Customers may experience elevated error rates or failed requests. We are actively monitoring the situation and working to restore normal operation as quickly as possible. Further updates will be provided as more information becomes available. **More details on affected services at:** [https://monitor.mathpix.com/.](https://monitor.mathpix.com/).</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:27:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. AWS services in the US-East-1 region have recovered, and we are no longer observing errors or elevated latency for the PDF API. We are continuing to investigate why traffic was not automatically routed to other regions during the outage and are working to ensure our failover mechanisms handle similar events more effectively in the future. All systems are operating normally at this time. More details on affected services at: <https://monitor.mathpix.com/> ..</p> ]]> Mon, 20 Oct 2025 07:11:00 +0000 https://status.mathpix.com/incident/cmgyw3k8n03k4yldjwfpgfqpr https://status.mathpix.com/incident/cmgyw3k8n03k4yldjwfpgfqpr The PDF processing API experienced long processing times from approximately 3:15 AM EST - 3:35 AM EST. Type: Incident Affected Components: OCR API (ap-southeast-1), OCR API (eu-central-1), OCR API (us-east-1) May 21, 07:35:00 GMT+0 - Resolved - This incident has been resolved. May 21, 07:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Affected Components: , ,

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>07:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Wed, 21 May 2025 07:15:00 +0000 https://status.mathpix.com/incident/cmay0y41h0050pzr1c25ghwdu https://status.mathpix.com/incident/cmay0y41h0050pzr1c25ghwdu The PDF processing API experienced long processing times from approximately 10:30 AM EST - 1:00 PM EST. Type: Incident Duration: 2 hours Affected Components: OCR API (ap-southeast-1), OCR API (eu-central-1), Snip, OCR API (us-east-1) May 7, 14:30:00 GMT+0 - Identified - We've identified an issue with our autoscaling being limited by AWS GPU capacity. We're adding more availability zones and scaling up manually. May 7, 17:00:00 GMT+0 - Resolved - All systems are back to normal. Type: Incident

Duration: 2 hours

Affected Components: , , ,

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue with our autoscaling being limited by AWS GPU capacity. We're adding more availability zones and scaling up manually..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Resolved</strong> - All systems are back to normal..</p> ]]> Wed, 7 May 2025 14:30:00 +0000 https://status.mathpix.com/incident/cmaechzl5004l9o80vx6ijuaa https://status.mathpix.com/incident/cmaechzl5004l9o80vx6ijuaa OCR API outage Type: Incident Duration: 5 minutes Jan 25, 06:11:09 GMT+0 - Resolved - OCR API is now operational! This update was created by an automated monitoring service. Jan 25, 06:06:01 GMT+0 - Investigating - OCR API cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

<p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>06:11:09</var> GMT+0</small><br><strong>Resolved</strong> - OCR API is now operational! This update was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>06:06:01</var> GMT+0</small><br><strong>Investigating</strong> - OCR API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sat, 25 Jan 2025 06:06:01 +0000 https://status.mathpix.com/incident/cm6bsf02p00nhoumm8wb87ikv https://status.mathpix.com/incident/cm6bsf02p00nhoumm8wb87ikv Convert Image API Disruption Type: Incident Duration: 2 hours Affected Components: OCR API (us-east-1) Sep 13, 12:45:00 GMT+0 - Identified - A service disruption was caused by an error in our autoscaling policy. Unexpected usage patterns from some of our top customers revealed flaws in our autoscaling algorithm. This led to service degradation to our Image Convert API endpoints for customers routed to our US data centers, while customers closer to Europe or Asia were unaffected. Sep 13, 14:45:00 GMT+0 - Resolved - Our engineering team quickly identified the issue and implemented a fix to restore normal service operations. We conducted a thorough investigation to pinpoint the root cause and have developed long-term solutions to strengthen our system: * **Autoscaling Improvements:** We've revised our autoscaling policies and algorithms to better handle unexpected usage behaviors and high-demand scenarios. * **Enhanced Monitoring:** Implementation of advanced monitoring tools to detect anomalies in real-time. * **Resource Allocation:** Additional resources have been allocated to ensure robust performance during traffic surges. Type: Incident

Duration: 2 hours

Affected Components:

<p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>12:45:00</var> GMT+0</small><br><strong>Identified</strong> - A service disruption was caused by an error in our autoscaling policy. Unexpected usage patterns from some of our top customers revealed flaws in our autoscaling algorithm. This led to service degradation to our Image Convert API endpoints for customers routed to our US data centers, while customers closer to Europe or Asia were unaffected..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>14:45:00</var> GMT+0</small><br><strong>Resolved</strong> - Our engineering team quickly identified the issue and implemented a fix to restore normal service operations. We conducted a thorough investigation to pinpoint the root cause and have developed long-term solutions to strengthen our system: * **Autoscaling Improvements:** We've revised our autoscaling policies and algorithms to better handle unexpected usage behaviors and high-demand scenarios. * **Enhanced Monitoring:** Implementation of advanced monitoring tools to detect anomalies in real-time. * **Resource Allocation:** Additional resources have been allocated to ensure robust performance during traffic surges..</p> ]]> Fri, 13 Sep 2024 12:45:00 +0000 https://status.mathpix.com/incident/cm16uiw53000a1jmnutrpzbnh https://status.mathpix.com/incident/cm16uiw53000a1jmnutrpzbnh The PDF processing API was unavailable for processing requests from approximately 9:32-10:35 UTC Type: Incident Affected Components: OCR API (us-east-1) Jan 20, 19:32:00 GMT+0 - Resolved - This incident has been resolved. The PDF processing API was unavailable for processing requests from approximately 9:32-10:35 UTC Type: Incident

Affected Components:

<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>19:32:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. The PDF processing API was unavailable for processing requests from approximately 9:32-10:35 UTC .</p> ]]> Sat, 20 Jan 2024 19:32:00 +0000 https://status.mathpix.com/incident/clro1hoh475712bgmu4dhtjeid https://status.mathpix.com/incident/clro1hoh475712bgmu4dhtjeid The PDF processing API was unavailable for processing requests from approximately from 18:30 to 21:00 UTC. Type: Incident Affected Components: OCR API (us-east-1) Jan 20, 16:30:00 GMT+0 - Resolved - This incident has been resolved. The PDF processing API was unavailable for processing requests from approximately from 18:30 to 21:00 UTC. Type: Incident

Affected Components:

<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. The PDF processing API was unavailable for processing requests from approximately from 18:30 to 21:00 UTC..</p> ]]> Sat, 20 Jan 2024 16:30:00 +0000 https://status.mathpix.com/incident/clro1kj6h76939b7mujhjsk9s1 https://status.mathpix.com/incident/clro1kj6h76939b7mujhjsk9s1 Degraded Performance Type: Incident Affected Components: OCR API (us-east-1) Dec 11, 04:44:59 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>04:44:59</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 11 Dec 2023 04:44:59 +0000 https://status.mathpix.com/incident/clq0fjozz49998beonez7ciyuy https://status.mathpix.com/incident/clq0fjozz49998beonez7ciyuy