Sinch MessageMedia Status
Real-time updates of Sinch MessageMedia issues and outages
Sinch MessageMedia status is Operational
The Hub
REST API
SMPP
Email To SMS
SFTP Automation
Shopify
Hubspot
You're checking on Sinch MessageMedia - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Sinch MessageMedia Outage Survival Guide
Sinch MessageMedia Components
Sinch MessageMedia - Services
The Hub
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
REST API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
SMPP
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Email To SMS
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
SFTP Automation
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Inbound System (Webhooks)
Sinch MessageMedia - Ecosystems
Shopify
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Hubspot
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
NetSuite
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Zoho CRM
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Big Commerce
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Salesforce
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Active Campaign
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Microsoft Dynamics
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Sinch MessageMedia - Legacy APIs
SOAP API (Legacy)
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
HTTP API (Legacy)
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
M4U API (Legacy)
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Sinch MessageMedia Oceania (Australia / New Zealand)
Sinch MessageMedia External Connectivity
APAC
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
North America
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Asia
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Middle East & Africa
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Europe
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
South America
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Sinch MessageMedia Brands
MessageNet
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
DirectSMS
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
MobiPost
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
SMSCentral
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
WholesaleSMS
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Streetdata
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.
Resolved: This incident has been resolved.
Monitoring: A fix has been implemented and we are monitoring the results.
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.
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Sinch MessageMedia Brands Messaging API
MessageNet API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
DirectSMS API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Mobipost API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
SMScentral API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
WholesaleSMS API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.
Streetdata API
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.
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.
Monitoring: 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.
Monitoring: 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.
Monitoring: A fix has been implemented and we are monitoring the results.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate this issue.
Investigating: We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: We are continuing to investigate this issue.
Investigating: 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.
Investigating: 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.
Investigating: 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.
Investigating: 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.
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.