Firetext incident

Messages not being received on our EE Reply Numbers

Minor Resolved View vendor source →

Firetext experienced a minor incident on November 4, 2025 affecting Outbound SMS and Inbound SMS, lasting 23h 22m. The incident has been resolved; the full update timeline is below.

Started
Nov 04, 2025, 10:02 AM UTC
Resolved
Nov 05, 2025, 09:24 AM UTC
Duration
23h 22m
Detected by Pingoru
Nov 04, 2025, 10:02 AM UTC

Affected components

Outbound SMSInbound SMS

Update timeline

  1. investigating Nov 04, 2025, 10:02 AM UTC

    We're observing connectivity issues with our partners at EE, inbound messages to our EE reply numbers are currently not being delivered to us and outbound SMS, specifically via our EE route, is degraded. We're working to identify and rectify the issue, the messages should deliver once re-connected.

  2. investigating Nov 04, 2025, 05:07 PM UTC

    We continue to see connectivity issues with our partners at EE, inbound messages to our EE reply numbers are currently not being delivered to us and outbound SMS, specifically via our EE route, is degraded. Our team is working directly with EE to pinpoint the exact cause of the problem on their side and get a fix implemented.

  3. investigating Nov 04, 2025, 05:08 PM UTC

    We are continuing to investigate this issue.

  4. investigating Nov 04, 2025, 08:26 PM UTC

    A fix has been applied to resolve the issue, we are now monitoring and can see backlogged inbound and outbound messages delivering.

  5. monitoring Nov 04, 2025, 08:26 PM UTC

    A fix has been applied to resolve the issue, we are now monitoring and can see backlogged inbound and outbound messages delivering.

  6. monitoring Nov 04, 2025, 08:28 PM UTC

    A fix has been applied to resolve the issue, we are now monitoring and can see backlogged inbound and outbound messages delivering.

  7. resolved Nov 05, 2025, 09:24 AM UTC

    This incident has been resolved.