MessageMedia experienced delays in both inbound and outbound messaging between 10:57 AEDT and 15:08 AEDT on March 26, 2026, caused by network routing and connectivity changes that disrupted message traffic paths. During the incident, outbound messages were queued within the platform and inbound messages were delayed in processing. The issue was resolved by establishing a new, direct, and stable network path, after which all queued messages were successfully processed and delivered.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with