MessageMedia incident

Delays in Inbound Messaging

Resolved after 54 minutes, affecting MessageNet and APAC and 1 more, on March 26, 2026.

resolved Mar 26, 2026, 05:22 AM UTC

Between 10:57 AEDT and 15:08 AEDT on 26 March 2026, customers experienced issues with message delivery due to intermittent connection failures. This impacted both inbound and outbound messaging, where messages were delayed in processing. During this period, outbound messages were queued within the platform and delivered once connectivity was restored. Inbound messages were also affected, with delays in receipt. The issue was caused by changes to underlying network routing and connectivity, which disrupted message traffic paths. Connectivity was restored by establishing a new, direct, and stable network path. Following this change, all queued messages were successfully processed and delivered. All services are now fully operational, and connectivity has remained stable since 15:08 AEDT.

Started
Mar 26, 2026, 04:28 AM UTC
Resolved
Mar 26, 2026, 05:22 AM UTC
Duration
54m
Detected by Pingoru
Mar 26, 2026, 04:28 AM UTC

Affected components

MessageNetAPACDirectSMSMobiPostSMSCentralWholesaleSMSStreetdata

Update timeline

  1. monitoring Mar 26, 2026, 04:28 AM UTC

    We have determined there were delays in receiving inbound traffic (MO) from between 12:45 AEDT and 15:09. The issue has been identified and resolved, however we continue to monitor for now.

  2. resolved Mar 26, 2026, 05:22 AM UTC

    Between 10:57 AEDT and 15:08 AEDT on 26 March 2026, customers experienced issues with message delivery due to intermittent connection failures. This impacted both inbound and outbound messaging, where messages were delayed in processing. During this period, outbound messages were queued within the platform and delivered once connectivity was restored. Inbound messages were also affected, with delays in receipt. The issue was caused by changes to underlying network routing and connectivity, which disrupted message traffic paths. Connectivity was restored by establishing a new, direct, and stable network path. Following this change, all queued messages were successfully processed and delivered. All services are now fully operational, and connectivity has remained stable since 15:08 AEDT.

Your product runs on more than MessageMedia

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 →