Resolved after 48 minutes, affecting 3rd Party Component Services, on August 28, 2025.
A fix was implemented at 11:08 AEST with ongoing monitoring can confirm the issue has been fixed. Transactions/SMS's do not need to be re-sent as SMS's were queued and should have since been delivered.
Affected components
Update timeline
- identified Aug 28, 2025, 12:54 AM UTC
Customer Degraded Messaging Burst SMS (used by many customers in the APAC regioN) have identified a potential issue in their systems and are currently investigating remediation options. Users may also additionally see intermittent issues logging into their account via the UI. Note: Messages should be added to queues and not lost. Live incident updates with Burst can be tracked here: https://status.transmitsms.com/incidents/2qtyfkq6hkmc
- resolved Aug 28, 2025, 01:56 AM UTC
A fix was implemented at 11:08 AEST with ongoing monitoring can confirm the issue has been fixed. Transactions/SMS's do not need to be re-sent as SMS's were queued and should have since been delivered.
Your product runs on more than IDVerse
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services