MessageMedia incident

Australia - Call Forwarding Degradation

Minor Resolved View vendor source →

MessageMedia experienced a minor incident on June 19, 2025 affecting APAC, lasting 6d 21h. The incident has been resolved; the full update timeline is below.

Started
Jun 19, 2025, 05:11 AM UTC
Resolved
Jun 26, 2025, 02:14 AM UTC
Duration
6d 21h
Detected by Pingoru
Jun 19, 2025, 05:11 AM UTC

Affected components

APAC

Update timeline

  1. investigating Jun 19, 2025, 05:11 AM UTC

    We are currently investigating an issue affecting our Australian Call Forwarding services. A subset of dedicated numbers is experiencing problems where calls are either not being forwarded as expected or are disconnecting prematurely. Our team is actively working to identify the root cause and implement a fix. We will provide further updates as they become available.

  2. investigating Jun 20, 2025, 12:16 AM UTC

    We are still investigating the issue affecting a subset of dedicated numbers in our Australian Call Forwarding service. Our engineering team is actively working with our provider to identify the root cause. We’ll continue to provide updates as more information becomes available.

  3. investigating Jun 22, 2025, 11:09 PM UTC

    We are continuing to investigate the issue affecting a subset of dedicated numbers in our Australian Call Forwarding service. Our engineering team remains actively engaged with our upstream provider to isolate the root cause. Further updates will be provided as soon as new information becomes available.

  4. investigating Jun 24, 2025, 11:17 PM UTC

    Our teams are still actively investigating the issue impacting a subset of dedicated numbers on our Australian Call Forwarding service. We're continuing to work closely with our upstream provider to pinpoint the root cause. We'll share further updates as soon as more information becomes available.

  5. identified Jun 25, 2025, 11:13 PM UTC

    The issue has been identified and a fix is being implemented.

  6. monitoring Jun 26, 2025, 01:04 AM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Jun 26, 2025, 02:14 AM UTC

    This incident has been resolved.