Welcome to the MessageMedia status page. Subscribe for real-time information about the status of our service via the subscribe link above.

All Systems Operational

Sinch MessageMedia Operational
The Hub ? Operational
REST API ? Operational
SMPP ? Operational
Email To SMS ? Operational
SFTP Automation ? Operational
Inbound System (Webhooks) ? Operational
Sinch MessageMedia - Ecosystems Operational
Shopify ? Operational
Hubspot ? Operational
NetSuite ? Operational
Zoho CRM ? Operational
Big Commerce ? Operational
Salesforce ? Operational
Active Campaign ? Operational
Microsoft Dynamics ? Operational
Sinch MessageMedia - Legacy APIs Operational
SOAP API (Legacy) ? Operational
HTTP API (Legacy) ? Operational
M4U API (Legacy) ? Operational
External Connectivity Operational
APAC ? Operational
North America ? Operational
Asia ? Operational
Middle East & Africa ? Operational
Europe ? Operational
South America ? Operational
Brands Operational
MessageNet ? Operational
DirectSMS ? Operational
MobiPost ? Operational
SMSCentral ? Operational
WholesaleSMS ? Operational
Streetdata ? Operational
Brands Messaging API Operational
MessageNet API Operational
DirectSMS API Operational
Mobipost API Operational
SMScentral API Operational
WholesaleSMS API Operational
Streetdata API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

MMS Maintenance Jul 30, 2025 16:00-17:00 AEST

Dear Customer,

We will be doing a planned maintenance on our MMS services. This will be done in the following window:

Start: Wednesday 30th July 04:00 PM AEST (Wednesday 30th July 06:00 AM UTC)
End: Wednesday 30th July 05:00 PM AEST (Wednesday 30th July 07:00 AM UTC)

As part of the maintenance, there is a planned outage of one hour. During this downtime, a subset of customers will not be able to send/receiving MMS messages. Any MMS sent during this downtime will fail.

There will be no impact on SMS messages.

Please contact support@messagemedia.com should you require further information or assistance.
Posted on Jul 09, 2025 - 10:27 AEST
Jul 9, 2025

No incidents reported today.

Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

Jul 3, 2025

No incidents reported.

Jul 2, 2025

No incidents reported.

Jul 1, 2025

No incidents reported.

Jun 30, 2025

No incidents reported.

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025
Australia - Call Forwarding Degradation
Resolved - This incident has been resolved.
Jun 26, 12:14 AEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 26, 11:04 AEST
Identified - The issue has been identified and a fix is being implemented.
Jun 26, 09:13 AEST
Update - 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.
Jun 25, 09:17 AEST
Update - 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.
Jun 23, 09:09 AEST
Update - 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.
Jun 20, 10:16 AEST
Investigating - 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.
Jun 19, 15:11 AEST
Jun 25, 2025
← Incident History Powered by Atlassian Statuspage