OIT incident

Inbound and Outbound NativeFax Failures

Resolved after 1 day 23 hours, on August 19, 2026.

monitoring Aug 25, 2026, 04:57 PM UTC

This incident was resolved on August 21st at 5:15 PM ET, and the Major Incident Report (MIR) is now available. * **Major Incident Report (MIR):** .

Started
Aug 19, 2026, 09:14 PM UTC
Resolved
Aug 21, 2026, 09:11 PM UTC
Duration
1d 23h
Detected by Pingoru
Aug 19, 2026, 09:14 PM UTC

Update timeline

  1. identified Aug 19, 2026, 09:14 PM UTC

    **What Occurred:** At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing. **What is Affected:** Inbound and Outbound faxes on the NativeFax platform are failing. **When it began:** August 19th, 2026, at 3:21 PM ET **Current Status:** We have identified the root cause, a failure of the fax port server, and are currently working to restore service. **Next Update:** August 19th, 2026 at 6:00pm ET.

  2. monitoring Aug 19, 2026, 09:57 PM UTC

    **What Occurred:** At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing. **What is Affected:** Inbound and Outbound faxes on the NativeFax platform are failing. **When it began:** August 19th, 2026, at 3:21 PM ET **Current Status:** We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability. **Next Update:** August 20th, 2026, at 3:30 pm ET.

  3. identified Aug 20, 2026, 08:21 PM UTC

    What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing. What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing. When it began: August 19th, 2026, at 3:21 PM ET Current Status: * We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026. * At 3:51 PM ET on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * We are actively working to restore service and will provide further details as they become available. Next Update: August 20th, 2026, at 5:15 pm ET.

  4. monitoring Aug 20, 2026, 09:01 PM UTC

    What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing. What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing. When it began: August 19th, 2026, at 3:21 PM ET Current Status: * We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026. * At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * As of 4:35 PM ET, we have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability. Next Update: August 21st, 2026, at 4:15 pm ET.

  5. identified Aug 20, 2026, 11:49 PM UTC

    **Identified** What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing. What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing. When it began: August 19th, 2026, at 3:21 PM ET Current Status: * We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026. * At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * At 4:46 PM ET, on August 20th, 2026, the port server service was restored. * At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * We are actively working to restore service and will provide further details as they become available. Next Update: August 20th, 2026, at 8:45 pm ET.

  6. identified Aug 21, 2026, 01:32 AM UTC

    **Identified** What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing. What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing. When it began: August 19th, 2026, at 3:21 PM ET Current Status: * We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026. * At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * At 4:46 PM ET, on August 20th, 2026, the port server service was restored. * At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail. * We're continuing to work on bringing the port server service back online, alongside the vendor's engineers. Further updates to follow as they're available. Next Update: August 20th, 2026, at 10:30 pm ET.

  7. monitoring Aug 21, 2026, 02:15 AM UTC

    **What Occurred:** At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing. **What is Affected:** Inbound and Outbound faxes on the NativeFax platform are failing. **When it began:** August 19th, 2026, at 3:21 PM ET **Current Status:** We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability. **Next Update:** August 21st, 2026, at 5 PM ET.

  8. resolved Aug 21, 2026, 09:11 PM UTC

    What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing. What was Affected: Inbound and Outbound faxes on the NativeFax platform When it began: August 19th, 2026, at 3:21 PM ET Current Status: * After 24 hours of monitoring and observing server stability, we are considering this incident resolved. The MIR will be provided within 48 business hours..

  9. monitoring Aug 25, 2026, 04:57 PM UTC

    This incident was resolved on August 21st at 5:15 PM ET, and the Major Incident Report (MIR) is now available. * **Major Incident Report (MIR):** .

Your product runs on more than OIT

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →