Jul <var data-var='date'> 1</var>, <var data-var='time'>15:56</var> AEST Resolved - This incident has been resolved. Jul <var data-var='date'> 1</var>, <var data-var='time'>11:08</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 1</var>, <var data-var='time'>09:20</var> AEST Investigating - We are currently investigating an issue with messages being over stamped with unverified that is affecting a small subset of customers that have account hierarchies containing multiple sub-accounts. For these impacted accounts, registered and verified alphanumeric sender IDs may be incorrectly replaced with unverified sender IDs. Our engineering teams are actively investigating the cause and working to restore normal sender ID behaviour as quickly as possible. We will provide a further update as soon as more information becomes available.

Australia - Issue Affecting Verified Alphanumeric Sender IDs

Jun <var data-var='date'>26</var>, <var data-var='time'>14:47</var> AEST Resolved - This incident has now been resolved, and our platform messaging services is operating normally. Message flow has returned to regular capacity, and no further issues are being observed. As part of the recovery process, messages submitted between 2:40 PM AEST on 25 June 2026 and 1:00 AM AEST on 26 June 2026 may remain in an ENROUTE status but will not be delivered. If these messages are still required, they will need to be resent. Our engineering teams are continuing to work with all relevant parties to complete a thorough root cause investigation. A Root Cause Analysis (RCA) will be shared once the investigation has concluded. We apologise for the disruption this incident caused and thank you for your patience and understanding throughout the recovery process. Jun <var data-var='date'>26</var>, <var data-var='time'>12:02</var> AEST Update - Messaging services within our platform continue to operate at normal capacity, with message sending and delivery performing as expected. Our engineering teams are not observing any further issues related to this incident and continue to closely monitor platform performance to ensure ongoing stability. Work is now focused on a comprehensive investigation into the outage that occurred yesterday. Our engineering teams are collaborating with all relevant parties to determine the root cause and will provide further information as it becomes available. Jun <var data-var='date'>26</var>, <var data-var='time'>03:25</var> AEST Update - A fix has been implemented and messaging services have recovered. We have completed validation testing and confirmed message sending and delivery are functioning as expected. Our teams will continue to closely monitor platform performance to ensure stability. We are not currently observing any further issues related to this incident. Jun <var data-var='date'>26</var>, <var data-var='time'>01:53</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>26</var>, <var data-var='time'>01:42</var> AEST Update - We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available. Jun <var data-var='date'>26</var>, <var data-var='time'>01:03</var> AEST Update - We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>23:53</var> AEST Update - We are continuing to investigate this issue. We are working on high priority together with external resources to restore service. Further updates will follow as more information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>22:48</var> AEST Update - We are continuing to investigate this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>22:16</var> AEST Update - We are continuing to investigate this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>21:59</var> AEST Update - We are continuing to investigate this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>21:43</var> AEST Update - We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible. Jun <var data-var='date'>25</var>, <var data-var='time'>21:12</var> AEST Update - We are continuing to investigate this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>20:36</var> AEST Update - We are continuing to investigate an issue affecting outbound message delivery. As a precaution, new message submissions are currently paused while we stabilise the system. Our engineering teams are actively working to restore normal service. Further updates will follow as more information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>20:07</var> AEST Update - We are continuing to investigate this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>19:52</var> AEST Update - Our investigation is ongoing, and we have not yet been able to definitively identify the root cause of the issue affecting outbound message delivery within the platform. To prevent further message backlog growth and reduce the risk of additional duplicate deliveries, we have implemented the following mitigation measures: Message submissions are being temporarily blocked and will return Failed responses. Message workers have been stopped to prevent further processing of impacted traffic. Queued messages are being redirected to a new queue for post-incident analysis and recovery efforts. Customers using SMPP may still be able to submit messages during this period. As a result, some message duplication may continue to occur until the incident is fully resolved. Our engineering teams remain actively engaged in identifying the root cause and restoring normal service. We will continue to provide updates as new information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>18:42</var> AEST Update - We have identified an issue within the internal systems responsible for routing messages to downstream mobile network operators. Since approximately 14:30 AEST, messages within our platform have been intermittently becoming stuck in a router worker process, resulting in delays to outbound message delivery. While the issue is ongoing, small batches of queued messages are continuing to be processed and delivered approximately every few minutes. Customers may also observe duplicate message deliveries in some cases as a result of this issue. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. Once the issue has been resolved, we expect queued messages to resume processing and be delivered automatically. We will provide further updates as more information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>18:10</var> AEST Update - We are still investigating an issue impacting outbound message delivery and engaging additional resources to help restore normal service as quickly as possible. Further updates will be provided as more information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>16:42</var> AEST Update - We are investigating an issue impacting outbound message delivery across all regions. Customers will experience delays in message processing and delivery, with message statuses remaining in "Enroute" for longer than expected. This issue is affecting outbound message sending across our platform. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available. Jun <var data-var='date'>25</var>, <var data-var='time'>15:56</var> AEST Investigating - We are currently investigating an issue causing message delivery degradation. Customers may experience delays in message processing, with some message statuses remaining in "Enroute" for longer than expected. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

Message Delivery Degredation

Jun <var data-var='date'>18</var>, <var data-var='time'>12:36</var> AEST Resolved - We can confirm that this incident has now been resolved and message deliverability has been fully restored. Following a thorough investigation, the root cause was identified as a carrier-side issue within Vodafone's network environment. No faults were identified within Sinch's platform or infrastructure. We proactively adjusted our traffic routing to minimise customer impact while Vodafone worked to resolve the issue. Vodafone has since restored normal service, and message delivery has returned to expected levels. Jun <var data-var='date'>18</var>, <var data-var='time'>11:16</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>18</var>, <var data-var='time'>09:57</var> AEST Investigating - Delays in message deliverability have been recorded for Australian/APAC carriers . We are currently investigating the cause of this issue.

APAC - Message deliverability/delay issues

Jun <var data-var='date'> 4</var>, <var data-var='time'>10:00</var> AEST Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>09:23</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 4</var>, <var data-var='time'>06:58</var> AEST Investigating - We're currently investigating an issue affecting the New Message screen, which may be unusable for some users. As a workaround, users can continue sending messages through the Inbox or by using Quick Message functionality. Our team is actively working to resolve the issue and will provide updates as more information becomes available.

New Message Screen Unavailable

May <var data-var='date'>28</var>, <var data-var='time'>16:16</var> AEST Resolved - This incident has been resolved. May <var data-var='date'>28</var>, <var data-var='time'>11:49</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>28</var>, <var data-var='time'>11:20</var> AEST Investigating - We are currently investigating an issue with the Web Portal UI impacting the processing of new Australian Alpha Tag registration requests. Requests are timing out and users are unable to proceed to the next step of the registration process. This issue is limited to the registration interface only. There is no impact to existing Alpha Tags or current message sending services.

Web Portal - Australian Alpha Tag Registration Delays

May <var data-var='date'>19</var>, <var data-var='time'>00:10</var> AEST Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>00:07</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>19</var>, <var data-var='time'>00:03</var> AEST Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>19</var>, <var data-var='time'>00:03</var> AEST Investigating - We are currently investigating an issue affecting the Contacts section within the Sinch MessageMedia and Engage UI. Customers may experience errors, blank pages, or inability to access or manage contacts. Messaging delivery services and APIs are currently operating normally. We will provide further updates as more information becomes available.

Contacts UI unavailable or failing to load

May <var data-var='date'>14</var>, <var data-var='time'>00:46</var> AEST Resolved - The incident has been resolved and all systems are operational. May <var data-var='date'>14</var>, <var data-var='time'>00:34</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>14</var>, <var data-var='time'>00:27</var> AEST Investigating - We’re currently investigating an issue causing Inbox to fail to load for some users. Affected users may see the following error message: “Something unforeseen happened. We have been notified and are working on a solution.” Our team is actively working to identify the root cause and restore service as quickly as possible. We’ll share additional updates as they become available.

Investigating — Inbox Unavailable

May <var data-var='date'> 8</var>, <var data-var='time'>08:53</var> AEST Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>08:13</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 8</var>, <var data-var='time'>03:19</var> AEST Investigating - We are currently observing delivery issues towards United States - AT&T through 10DLC route. Estimated Incident Start Time: 2026-05-06 14:00 UTC Impact: Delayed delivery for concatenated 10DLC MT messages submitted towards AT&T US. We will update as soon as we have more information.

Delivery Issue United States - AT&T - 10DLC

May <var data-var='date'> 7</var>, <var data-var='time'>11:01</var> AEST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 7</var>, <var data-var='time'>10:30</var> AEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>27</var>, <var data-var='time'>10:24</var> AEST Scheduled - Dear Customer, We will be performing a certificate update for m4ud.messagemedia.com. This will take place during the following window: Start: 07/05/2026 10:30 UTC+10 (07/05/2026 12:30 UTC) End: 07/05/2026 11:00 UTC+10 (07/05/2026 01:00 UTC) During this period, there is no expected impact to the service, including downtime or message delays. Customers who store or pin the certificate locally will need to update their systems to trust the new certificate once the change has been completed. If you have any questions regarding this update, please contact support@messagemedia.com.

Certificate Update m4ud.messagemedia.com

May <var data-var='date'> 7</var>, <var data-var='time'>11:00</var> AEST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 7</var>, <var data-var='time'>10:00</var> AEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>27</var>, <var data-var='time'>13:23</var> AEST Update - We will be undergoing scheduled maintenance during this time. Apr <var data-var='date'>24</var>, <var data-var='time'>09:37</var> AEST Scheduled - Dear Customer, We will be performing maintenance on our API SMS Database Service during the following window: Start: Thursday, 07 May 2026, 10:00 AM AEDT End: Thursday, 07 May 2026, 11:00 AM AEDT During this maintenance window, messages sent via API may experience temporary failures of up to 5 minutes. Impact details: - Messages sent via API between 10:00 AM and 11:00 AM AEDT may temporarily fail for up to 5 minutes. - There will be no impact to scheduled messages via the Hub during this time. - All Hub messages, including immediate sends and inbound messages, will continue to send and receive as normal. Impacted Brands: - Mobipost - SMS Central Please contact the Support Team if you require any further information or assistance.

API Service Upgrade

May <var data-var='date'> 1</var>, <var data-var='time'>12:38</var> AEST Resolved - This incident has been resolved. May <var data-var='date'> 1</var>, <var data-var='time'>05:55</var> AEST Update - Our Provider is still continuing to investigate this issue. May <var data-var='date'> 1</var>, <var data-var='time'>03:56</var> AEST Investigating - We are currently observing delivery issues with 10DLCs in US to AT&T carrier. Our Provider is currently investigating the issue and we will update as soon as we have more information. Impact: Delayed MT's/Delayed MO's/Missing delivery receipts/Late delivery receipts

10DLC Delivery Issue US - AT&T

Apr <var data-var='date'>23</var>, <var data-var='time'>10:55</var> AEST Resolved - This incident has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>09:50</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>23</var>, <var data-var='time'>09:49</var> AEST Investigating - We experienced connectivity issues with our EU3 endpoint. Start Time (UTC): Apr 22, 2026 – 20:29 UTC Impact - Some messages may be delayed - No message loss has been identified - Incoming messages (MO) may be impacted due to connectivity issues We have implemented a fix and are monitoring to ensure full connectivity is restored.

EU3 Endpoint Connectivity Issues Causing Message Delays

Apr <var data-var='date'>17</var>, <var data-var='time'>22:34</var> AEST Resolved - This incident has been resolved. Apr <var data-var='date'>17</var>, <var data-var='time'>22:06</var> AEST Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>17</var>, <var data-var='time'>21:19</var> AEST Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>17</var>, <var data-var='time'>19:16</var> AEST Investigating - We are currently investigating an issue affecting Social Campaigns where users are unable to create new campaigns from the Social Messaging > All Campaigns section.

Social Campaigns Creation Failure – “Create” Button Not Responding

Mar <var data-var='date'>31</var>, <var data-var='time'>03:01</var> AEDT Resolved - This incident has been resolved. Mar <var data-var='date'>31</var>, <var data-var='time'>03:00</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>31</var>, <var data-var='time'>01:52</var> AEDT Investigating - We are currently investigating an issue in which MMS is not functional. Customers will not be able to send/receive MMS.

MMS Degradation

Mar <var data-var='date'>26</var>, <var data-var='time'>16:22</var> AEDT Resolved - 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. Mar <var data-var='date'>26</var>, <var data-var='time'>15:28</var> AEDT Monitoring - 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.

Delays in Inbound Messaging

Mar <var data-var='date'>25</var>, <var data-var='time'>02:58</var> AEDT Resolved - This incident has been resolved. Mar <var data-var='date'>25</var>, <var data-var='time'>02:27</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>25</var>, <var data-var='time'>02:26</var> AEDT Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>25</var>, <var data-var='time'>02:25</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>25</var>, <var data-var='time'>01:45</var> AEDT Investigating - We are currently experiencing an issue where the Hub Inbox is not automatically refreshing to display new messages. Impact: Customers may not see incoming messages in real time. To view new messages, please manually refresh the page. Status: Our team is investigating the issue and we will provide an update as soon as possible.

Hub Inbox Auto-Refresh Issue

Mar <var data-var='date'>10</var>, <var data-var='time'>16:30</var> AEDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>10</var>, <var data-var='time'>16:00</var> AEDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>23</var>, <var data-var='time'>12:53</var> AEDT Scheduled - Dear Customer, We will be performing maintenance on our Scheduling Service. This will be done in the following window: Start: Tuesday 10 March 2026 16:00 AEDT (Tuesday 10 March 2026 05:00 UTC) End: Tuesday 10 March 2026 16:30 AEDT (Tuesday 10 March 2026 05:30 UTC) As part of this maintenance, any messages scheduled to be sent during the upgrade window will be delayed by up to 30 minutes. The following will be impacted during the upgrade: - Messages scheduled to be sent between 4:00 PM and 4:30 PM AEDT may be delayed by up to 30 minutes. - There will be no impact to scheduling new messages during this time. - All other messages (including immediate sends and inbound messages) will continue to send and receive as normal. Please contact the Support Team if you require any further information or assistance.

Scheduling Service Upgrade

Mar <var data-var='date'>10</var>, <var data-var='time'>03:56</var> AEDT Resolved - This incident has been resolved. Mar <var data-var='date'>10</var>, <var data-var='time'>03:44</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>10</var>, <var data-var='time'>12:30</var> AEDT Identified - In the Inbox, when a new conversation is created or a previously closed conversation is re-opened, the system sends a duplicate SMS to the customer. This duplication only occurs on the first message associated with the new or re-opened conversation. Any subsequent SMS messages are sent correctly as a single message. The issue has been identified and a fix is being implemented.

Duplicate SMS Sent for New or Re-Opened Conversations in Inbox

Mar <var data-var='date'> 2</var>, <var data-var='time'>14:50</var> AEDT Resolved - This incident has been resolved. Mar <var data-var='date'> 2</var>, <var data-var='time'>14:49</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 2</var>, <var data-var='time'>13:24</var> AEDT Update - We are continuing to investigate this issue. Mar <var data-var='date'> 2</var>, <var data-var='time'>11:18</var> AEDT Investigating - We are currently experiencing issues with emails sent to all support addresses. In the meantime, please contact Support via Live Chat until the issue is resolved. Our IT team is working on this as a priority and will provide updates as soon as they become available.

Support Emails Not Working

Feb <var data-var='date'>11</var>, <var data-var='time'>13:23</var> AEDT Resolved - This incident has been resolved. Feb <var data-var='date'>11</var>, <var data-var='time'>12:31</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>11</var>, <var data-var='time'>11:15</var> AEDT Investigating - We are currently investigating an issue where end users are unable to add or edit contacts within the platform. No error message appears, but updates are not being saved. Our engineers are actively working to resolve this issue and will provide updates as soon as possible

Issue Adding or Editing Contacts in the UI

Feb <var data-var='date'> 9</var>, <var data-var='time'>14:42</var> AEDT Resolved - This incident has been resolved. Feb <var data-var='date'> 9</var>, <var data-var='time'>14:23</var> AEDT Identified - The issue has been identified and a fix is being implemented. Feb <var data-var='date'> 9</var>, <var data-var='time'>13:43</var> AEDT Update - Telstra has confirmed the issue on their end and they currently working to resolve it. SMS delivery and sending may be impacted. Feb <var data-var='date'> 9</var>, <var data-var='time'>12:59</var> AEDT Update - We are continuing to investigate this issue. Feb <var data-var='date'> 9</var>, <var data-var='time'>12:59</var> AEDT Investigating - Dear Customer, We are currently investigating an issue with messages not being sent and stuck in Enroute status. Our engineers are reviewing this and working to resolve it as quickly as possible.

AU - Outbound Message Delays

Jan <var data-var='date'>16</var>, <var data-var='time'>00:27</var> AEDT Resolved - This incident has been resolved. Jan <var data-var='date'>15</var>, <var data-var='time'>23:33</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'>15</var>, <var data-var='time'>23:26</var> AEDT Identified - The issue has been identified and a fix is being implemented. Jan <var data-var='date'>15</var>, <var data-var='time'>07:56</var> AEDT Update - We are continuing to investigate this issue. Jan <var data-var='date'>15</var>, <var data-var='time'>06:05</var> AEDT Investigating - We are currently observing delivery issues in US - Verizon. Incident Start Time: 2026-01-14 17:00 UTC Impact: Delayed MT's/Delayed MO's/Missing delivery receipts/Late delivery receipts We will update as soon as we have more information.

Delivery Issue US - Verizon

Jan <var data-var='date'>13</var>, <var data-var='time'>07:30</var> AEDT Resolved - This incident has been resolved. Jan <var data-var='date'>13</var>, <var data-var='time'>07:25</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'>13</var>, <var data-var='time'>07:24</var> AEDT Identified - The issue has been identified and a fix is being implemented. Jan <var data-var='date'>13</var>, <var data-var='time'>07:19</var> AEDT Update - We are continuing to investigate this issue. Jan <var data-var='date'>13</var>, <var data-var='time'>06:52</var> AEDT Investigating - We are currently investigating an issue in which end users are currently unable to add a contact within the inbox for a new number they are in communication with. End users might observe see a red error stating "error on saving the contact" within the Hub. We also have received reports that end users are also unable to save contacts within the contacts portion of the hub via contacts → all contacts → add contact.

Unable to add a contact within the inbox or within contacts of the UI

Jan <var data-var='date'> 8</var>, <var data-var='time'>06:08</var> AEDT Resolved - This incident has been resolved. Jan <var data-var='date'> 8</var>, <var data-var='time'>06:06</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'> 8</var>, <var data-var='time'>05:47</var> AEDT Investigating - We are currently investigating an issue in which end users will experience longer wait times upon attempting to load hub.messagemedia.com. The page eventually loads after some time if the end user waits.

Higher loading times for hub.messagemedia.com

Dec <var data-var='date'>15</var>, <var data-var='time'>13:21</var> AEDT Resolved - This incident has been resolved. Dec <var data-var='date'>15</var>, <var data-var='time'>13:00</var> AEDT Monitoring - A fix has been implemented and we are monitoring the results. Dec <var data-var='date'>15</var>, <var data-var='time'>12:30</var> AEDT Investigating - We are currently investigating an issue impacting inbound SMS delivery to Call Forwarding dedicated numbers. Outbound messaging and voice services are operating normally. At this stage, the impact is limited to inbound messages originating from a specific provider. Further updates will be shared as more information becomes available.

Is MessageMedia down?

MessageMedia status is UP

Lastest published events

Australia - Issue Affecting Verified Alphanumeric Sender IDs

Message Delivery Degredation

APAC - Message deliverability/delay issues

MessageMedia Services, Components and Regions

Recent MessageMedia events

Australia - Issue Affecting Verified Alphanumeric Sender IDs

Message Delivery Degredation

APAC - Message deliverability/delay issues

New Message Screen Unavailable

Web Portal - Australian Alpha Tag Registration Delays

Contacts UI unavailable or failing to load

Get your FREE account now,
5 monitors included!

Is MessageMedia down?

MessageMedia status is UP

Lastest published events

Australia - Issue Affecting Verified Alphanumeric Sender IDs

Message Delivery Degredation

APAC - Message deliverability/delay issues

MessageMedia Services, Components and Regions

Recent MessageMedia events

Australia - Issue Affecting Verified Alphanumeric Sender IDs

Message Delivery Degredation

APAC - Message deliverability/delay issues

New Message Screen Unavailable

Web Portal - Australian Alpha Tag Registration Delays

Contacts UI unavailable or failing to load

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!