March 2026: MMS Degradation
MessageMedia experienced an MMS service outage that prevented customers from sending or receiving MMS messages through The Hub platform. The incident lasted approximately 1.2 hours before being fully resolved.
Every past MessageMedia outage tracked by IsDown, with detection times, duration, and resolution details.
There were 242 MessageMedia outages since March 2021. The 39 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.
MessageMedia experienced an MMS service outage that prevented customers from sending or receiving MMS messages through The Hub platform. The incident lasted approximately 1.2 hours before being fully resolved.
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.
MessageMedia's Hub Inbox experienced an auto-refresh issue that prevented new messages from displaying in real time, requiring users to manually refresh the page to see incoming messages. The Hub component was affected for 1.3 hours while the team investigated and implemented a fix. The incident was resolved after monitoring confirmed the fix was working properly.
MessageMedia's Inbox experienced an issue where duplicate SMS messages were sent to customers when creating new conversations or re-opening previously closed ones, affecting only the first message in each conversation. The Hub component was impacted for 55 minutes before a fix was implemented and the incident was resolved.
MessageMedia experienced a 3.6-hour outage where all support email addresses were non-functional, affecting the Email To SMS service component. Users were directed to use Live Chat as an alternative support channel during the incident. The issue was resolved after investigation by the IT team.