Subscribe to UpdatesSubscribe
Get email notifications whenever 5c SMS Site Status creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
Dashboard & API
Operational
90 days ago
99.94
% uptime
Today
Message Queues
Operational
90 days ago
100.0
% uptime
Today
Network Providers
Operational
90 days ago
100.0
% uptime
Today
AWS ec2-ap-southeast-2
Operational
AWS sqs-ap-southeast-2
Operational
AWS s3-ap-southeast-2
Operational
AWS lambda-ap-southeast-2
Operational
Cloudflare Sydney, NSW, Australia - (SYD)
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Mar 22, 2026
No incidents reported today.
Mar 21, 2026
No incidents reported.
Mar 20, 2026
No incidents reported.
Mar 19, 2026
No incidents reported.
Mar 18, 2026
No incidents reported.
Mar 17, 2026
No incidents reported.
Mar 16, 2026
Resolved -
We have completed our investigation in coordination with our carriers and confirmed that the root cause has been fully addressed. Delivery rates have been confirmed as normal over the past 24 hours.
Between approximately 6:00 AM and 7:30 AM AEST on 15th March 2026, a carrier-side issue resulted in an elevated number of message failures for a subset of customers during that window. A small number of accounts were affected; those customers have been contacted directly with further details.
Mar 16, 07:56 AEST
Between approximately 6:00 AM and 7:30 AM AEST on 15th March 2026, a carrier-side issue resulted in an elevated number of message failures for a subset of customers during that window. A small number of accounts were affected; those customers have been contacted directly with further details.
Mar 16, 07:56 AEST
Update -
We are continuing to monitor delivery rates, while investigating cases of unexpected failures with carriers.
Mar 15, 13:16 AEST
Mar 15, 13:16 AEST
Monitoring -
Delivery rates have returned to normal, we are continuing to investigate with our carriers
Mar 15, 08:04 AEST
Mar 15, 08:04 AEST
Investigating -
We are have detected message delivery failure rates higher than normal. We are working with network carriers to investigate.
Mar 15, 07:12 AEST
Mar 15, 07:12 AEST
Completed -
SSL/TLS Configuration updated completed.
Mar 16, 00:46 AEST
Mar 16, 00:46 AEST
Scheduled -
On 16th March 2026, we will be upgrading the SSL/TLS configuration on 5centsms.com.au and dingomail.com.au to improve security and align with current industry best practices.
This upgrade may affect integrations using older TLS versions or deprecated cipher suites. We recommend testing your integration against our updated configuration before the cutover date.
To test compatibility now, connect to the Website or API via:
https://wwww.5centsms.com.au
Please note: this is a temporary test environment provided solely to allow compatibility testing ahead of the upgrade. It should not be used for ongoing access or production traffic, and will be decommissioned once the new SSL/TLS configuration has been rolled out across www.5centsms.com.au and the API.
If you experience any issues during testing, please contact our support team as soon as possible so we can assist before the change goes live.
Feb 26, 03:16 AEST
This upgrade may affect integrations using older TLS versions or deprecated cipher suites. We recommend testing your integration against our updated configuration before the cutover date.
To test compatibility now, connect to the Website or API via:
https://wwww.5centsms.com.au
Please note: this is a temporary test environment provided solely to allow compatibility testing ahead of the upgrade. It should not be used for ongoing access or production traffic, and will be decommissioned once the new SSL/TLS configuration has been rolled out across www.5centsms.com.au and the API.
If you experience any issues during testing, please contact our support team as soon as possible so we can assist before the change goes live.
Feb 26, 03:16 AEST
Mar 15, 2026
Completed -
The scheduled maintenance has been completed.
Mar 15, 07:10 AEST
Mar 15, 07:10 AEST
Scheduled -
Services may be intermittently unavailable during this time.
Mar 2, 10:15 AEST
Mar 2, 10:15 AEST
Mar 14, 2026
No incidents reported.
Mar 13, 2026
No incidents reported.
Mar 12, 2026
No incidents reported.
Mar 11, 2026
No incidents reported.
Mar 10, 2026
No incidents reported.
Mar 9, 2026
No incidents reported.
Mar 8, 2026
Resolved -
Root Cause Analysis
A Message from Our Leadership Team
We want to take a moment to sincerely thank our customers for their patience and understanding during the outage on 6 March 2026. We recognise that your ability to send messages and access your account is critical to your operations, and we do not take lightly the disruption this incident caused.
This outage falls below the standard of availability we hold ourselves to, and that our customers rightly expect from us. We are committed to understanding exactly what went wrong, being transparent about it, and putting the right safeguards in place to ensure it is not repeated.
We also want to acknowledge the volume of enquiries our support team received during the incident. Our phone lines and email were overwhelmed, and while our team worked as hard as they could to respond in a timely manner, we understand that wait times were not acceptable. We sincerely apologise for any frustration this caused.
To help keep you informed during any future incidents, we strongly encourage all customers to subscribe to real-time updates at status.5centsms.com.au. Our engineering team posts updates there as incidents develop, so you can stay informed without needing to contact support.
If you would like to discuss this incident further please don't hesitate to reach out to us at hello@5centsms.com.au or your account manager. We are happy to talk through what happened and how we can best support you.
Executive Summary
On 6 March 2026, 5centsms.com.au experienced a service outage affecting the customer dashboard and API. The outage was caused by an automated certificate renewal process that deployed invalid certificate files to backend database nodes, triggering replication failures and a cascading database outage. The team was alerted immediately and began investigation. The root cause was identified and corrected certificates were manually provisioned, restoring core services.
The automated certificate deployment service has been disabled pending a full review and will not be re-enabled until remediation controls are in place.
Incident Timeline (All times AEST on 06/03/2026)
14:36 Automated certificate renewal process deploys invalid certificate files to backend database nodes
14:36 Automated alerts triggered; on-call team notified
14:36 Dashboard and API begin returning errors; investigation commenced
15:40 Root cause identified: invalid certificates causing database replication failure
15:40 Manual certificate provisioning initiated
16:21 Core services (dashboard and API) restored
~16:51 Auxiliary services fully restored
Root Cause
The automated certificate renewal service deployed invalid certificate files to backend database nodes during an automated renewal cycle. The invalid certificates caused database replication to fail across affected nodes. As replication failed, the databases became unavailable, which in turn caused the customer dashboard and API to return errors.
This was not a deliberate or malicious event. The certificate deployment service had not previously issued incorrect certificates, and no prior issues with this process had been observed.
Detection & Response
Automated monitoring detected the failure at the time of the incident and immediately alerted the on-call team. The team commenced investigation without delay.
Troubleshooting was initially impeded by the invalid certificates themselves, engineers were unable to connect directly to the affected database nodes to investigate, as the same certificate failure that caused the outage also blocked administrative access. A workaround was implemented to restore connectivity before root cause investigation could proceed in earnest. This contributed to the time between alert and root cause identification.
The workaround approach and steps taken have been documented to improve response speed and reduce friction in any similar future incident. Once identified, manual certificate provisioning was completed and core services were restored.
Remediation Actions
Immediate
Invalid certificates were removed from all affected database nodes
Correct certificates were manually provisioned across the database cluster
Core services were restored and verified
Auxiliary services were confirmed fully operational
Short-Term
The automated certificate deployment service has been disabled pending a full review
A review of the certificate deployment pipeline is underway to identify how invalid certificate files were generated
Long-Term
The certificate deployment service will not be re-enabled until the following controls are implemented:
1. Staggered deployments: certificate updates will be applied to a single replica at a time, with a minimum 24-hour interval between each node update. This allows the team to detect and halt a bad deployment before it affects the full cluster.
2. Pre-deployment certificate validation: automated checks will verify certificate validity, chain integrity, and expiry before any deployment proceeds.
3. Automated rollback: if a replica fails to successfully apply a new certificate, the process will automatically roll back and halt further deployments, triggering an alert for manual review.
Contact
If you have questions regarding this incident, please contact the 5centsms.com.au support team at hello@5centsms.com.au.
Mar 8, 06:22 AEST
A Message from Our Leadership Team
We want to take a moment to sincerely thank our customers for their patience and understanding during the outage on 6 March 2026. We recognise that your ability to send messages and access your account is critical to your operations, and we do not take lightly the disruption this incident caused.
This outage falls below the standard of availability we hold ourselves to, and that our customers rightly expect from us. We are committed to understanding exactly what went wrong, being transparent about it, and putting the right safeguards in place to ensure it is not repeated.
We also want to acknowledge the volume of enquiries our support team received during the incident. Our phone lines and email were overwhelmed, and while our team worked as hard as they could to respond in a timely manner, we understand that wait times were not acceptable. We sincerely apologise for any frustration this caused.
To help keep you informed during any future incidents, we strongly encourage all customers to subscribe to real-time updates at status.5centsms.com.au. Our engineering team posts updates there as incidents develop, so you can stay informed without needing to contact support.
If you would like to discuss this incident further please don't hesitate to reach out to us at hello@5centsms.com.au or your account manager. We are happy to talk through what happened and how we can best support you.
Executive Summary
On 6 March 2026, 5centsms.com.au experienced a service outage affecting the customer dashboard and API. The outage was caused by an automated certificate renewal process that deployed invalid certificate files to backend database nodes, triggering replication failures and a cascading database outage. The team was alerted immediately and began investigation. The root cause was identified and corrected certificates were manually provisioned, restoring core services.
The automated certificate deployment service has been disabled pending a full review and will not be re-enabled until remediation controls are in place.
Incident Timeline (All times AEST on 06/03/2026)
14:36 Automated certificate renewal process deploys invalid certificate files to backend database nodes
14:36 Automated alerts triggered; on-call team notified
14:36 Dashboard and API begin returning errors; investigation commenced
15:40 Root cause identified: invalid certificates causing database replication failure
15:40 Manual certificate provisioning initiated
16:21 Core services (dashboard and API) restored
~16:51 Auxiliary services fully restored
Root Cause
The automated certificate renewal service deployed invalid certificate files to backend database nodes during an automated renewal cycle. The invalid certificates caused database replication to fail across affected nodes. As replication failed, the databases became unavailable, which in turn caused the customer dashboard and API to return errors.
This was not a deliberate or malicious event. The certificate deployment service had not previously issued incorrect certificates, and no prior issues with this process had been observed.
Detection & Response
Automated monitoring detected the failure at the time of the incident and immediately alerted the on-call team. The team commenced investigation without delay.
Troubleshooting was initially impeded by the invalid certificates themselves, engineers were unable to connect directly to the affected database nodes to investigate, as the same certificate failure that caused the outage also blocked administrative access. A workaround was implemented to restore connectivity before root cause investigation could proceed in earnest. This contributed to the time between alert and root cause identification.
The workaround approach and steps taken have been documented to improve response speed and reduce friction in any similar future incident. Once identified, manual certificate provisioning was completed and core services were restored.
Remediation Actions
Immediate
Invalid certificates were removed from all affected database nodes
Correct certificates were manually provisioned across the database cluster
Core services were restored and verified
Auxiliary services were confirmed fully operational
Short-Term
The automated certificate deployment service has been disabled pending a full review
A review of the certificate deployment pipeline is underway to identify how invalid certificate files were generated
Long-Term
The certificate deployment service will not be re-enabled until the following controls are implemented:
1. Staggered deployments: certificate updates will be applied to a single replica at a time, with a minimum 24-hour interval between each node update. This allows the team to detect and halt a bad deployment before it affects the full cluster.
2. Pre-deployment certificate validation: automated checks will verify certificate validity, chain integrity, and expiry before any deployment proceeds.
3. Automated rollback: if a replica fails to successfully apply a new certificate, the process will automatically roll back and halt further deployments, triggering an alert for manual review.
Contact
If you have questions regarding this incident, please contact the 5centsms.com.au support team at hello@5centsms.com.au.
Mar 8, 06:22 AEST
Update -
Queues are returning to normal operation and backlogs are in the process of being cleared. We are monitoring all systems.
Mar 6, 16:35 AEST
Mar 6, 16:35 AEST
Monitoring -
The Dashboard and API have been restored. Backend services and message queues are expected to return to normal in 10-15 minutes
Mar 6, 16:21 AEST
Mar 6, 16:21 AEST
Identified -
A fix has been deployed. We are currently deploying the required changes to the affected system.
Mar 6, 16:13 AEST
Mar 6, 16:13 AEST
Update -
We have identified the cause of the issue and are looking into a fix. We will provide another update within the next 30 minutes.
Mar 6, 15:56 AEST
Mar 6, 15:56 AEST
Update -
Our team is investigating the cause of the issue which appears to be a failed backend service
Mar 6, 15:37 AEST
Mar 6, 15:37 AEST
Investigating -
We are aware of an issue affecting the dashboard and API - it is currently being investigated
Mar 6, 15:11 AEST
Mar 6, 15:11 AEST