Studentnet Outage History

Started Aug 06, 2026, 11:21 PM UTC· resolved Aug 07, 2026, 02:52 AM UTC

1. investigating Aug 06, 2026, 11:21 PM UTC

   We are currently investigating a performance issue being generated by a very large number of accesses.

2. monitoring Aug 07, 2026, 01:40 AM UTC

   Performance is returning to normal but further investigation and monitoring will be undertaken.

3. resolved Aug 07, 2026, 02:52 AM UTC

   The incident has been resolved. Further investigations will be completed for longer term protection.

Read the full incident report →

Started Jun 25, 2026, 06:04 AM UTC· resolved Jun 26, 2026, 12:54 AM UTC

1. investigating Jun 25, 2026, 06:04 AM UTC

   Our SMS gateway, SMS Broadcast, is reporting a technical issue leading to significant delay in the transmission of SMSs. This may affect users attempting to login using SMS as the 2nd factor in their MFA authentication.

2. investigating Jun 25, 2026, 09:32 AM UTC

   SMS Broadcast have provided the following update... Update - We have identified an issue within the internal systems responsible for routing messages to downstream mobile network operators. Since approximately 14:30 AEST, messages within our platform have been intermittently becoming stuck in a router worker process, resulting in delays to outbound message delivery. While the issue is ongoing, small batches of queued messages are continuing to be processed and delivered approximately every few minutes. Customers may also observe duplicate message deliveries in some cases as a result of this issue. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. Once the issue has been resolved, we expect queued messages to resume processing and be delivered automatically.

3. monitoring Jun 25, 2026, 07:01 PM UTC

   SMS Broadcast have provided the following update: Update - A fix has been implemented and messaging services have recovered. We have completed validation testing and confirmed message sending and delivery are functioning as expected. Our teams will continue to closely monitor platform performance to ensure stability. We are not currently observing any further issues related to this incident. Jun 26, 2026 - 03:26 AEST Monitoring - A fix has been implemented and we are monitoring the results. Jun 26, 2026 - 01:51 AEST Update - We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available. Jun 26, 2026 - 01:44 AEST Update - We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available. Jun 26, 2026 - 01:04 AEST Update - We are continuing to investigate this issue. We are working on high priority together with external resources to restore service. Further updates will follow as more information becomes available. Jun 25, 2026 - 23:53 AEST Update - We are continuing to investigate this issue. Jun 25, 2026 - 22:53 AEST Update - We are continuing to investigate this issue. Jun 25, 2026 - 22:17 AEST Update - We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible. Jun 25, 2026 - 21:44 AEST Update - We are continuing to investigate this issue. Jun 25, 2026 - 21:12 AEST Update - We are continuing to investigate an issue affecting outbound message delivery. As a precaution, new message submissions are currently paused while we stabilise the system. Our engineering teams are actively working to restore normal service. Further updates will follow as more information becomes available. Jun 25, 2026 - 20:36 AEST Update - Our investigation is ongoing, and we have not yet been able to definitively identify the root cause of the issue affecting outbound message delivery within the platform. To prevent further message backlog growth and reduce the risk of additional duplicate deliveries, we have implemented the following mitigation measures: Message submissions are being temporarily blocked and will return Failed responses. Message workers have been stopped to prevent further processing of impacted traffic. Queued messages are being redirected to a new queue for post-incident analysis and recovery efforts. Customers using SMPP may still be able to submit messages during this period. As a result, some message duplication may continue to occur until the incident is fully resolved. Our engineering teams remain actively engaged in identifying the root cause and restoring normal service. We will continue to provide updates as new information becomes available. Jun 25, 2026 - 19:52 AEST Update - We have identified an issue within the internal systems responsible for routing messages to downstream mobile network operators. Since approximately 14:30 AEST, messages within our platform have been intermittently becoming stuck in a router worker process, resulting in delays to outbound message delivery. While the issue is ongoing, small batches of queued messages are continuing to be processed and delivered approximately every few minutes. Customers may also observe duplicate message deliveries in some cases as a result of this issue. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. Once the issue has been resolved, we expect queued messages to resume processing and be delivered automatically. We will provide further updates as more information becomes available. Jun 25, 2026 - 18:42 AEST Update - We are still investigating an issue impacting outbound message delivery and engaging additional resources to help restore normal service as quickly as possible. Further updates will be provided as more information becomes available. Jun 25, 2026 - 18:10 AEST Update - We are investigating an issue impacting outbound message delivery across all regions. Customers will experience delays in message processing and delivery, with message statuses remaining in "Enroute" for longer than expected. This issue is affecting outbound message sending across our platform. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available. Jun 25, 2026 - 16:46 AEST Investigating - We are currently investigating an issue causing message delivery degradation. Customers may experience delays in message processing, with some message statuses remaining in "Enroute" for longer than expected. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available. Jun 25, 2026 - 15:58 AEST

4. resolved Jun 26, 2026, 12:54 AM UTC

   SMS message delivery appears to have been resolved. Messages are flowing through smoothly and promptly. We are closing this incident for now. If there is any further please contact us immediately on (02) 9281 1626. Thank you.

Read the full incident report →

Started Feb 10, 2026, 09:40 PM UTC· resolved Feb 10, 2026, 10:20 PM UTC

1. investigating Feb 10, 2026, 09:40 PM UTC

   We are currently investigating an AWS outage that may affect a handful of schools. More information on the AWS incident is located here: https://health.aws.amazon.com/health/status

2. resolved Feb 10, 2026, 10:20 PM UTC

   All of the monitoring canaries have returned to the OK state. So schools should no longer be affected at this stage. Please report any incidents to (02) 9281 1626

Read the full incident report →

Started Feb 09, 2026, 02:11 AM UTC· resolved Feb 09, 2026, 03:58 AM UTC

1. investigating Feb 09, 2026, 02:11 AM UTC

   We are currently investigating an incident with SMS broadcast. All outbound SMSs are showing as being "enroute" meaning that they are being processed and will eventually be processed but there will be some form of delay.

2. identified Feb 09, 2026, 02:31 AM UTC

   We have identified this as being an issue at our SMS gateway SMS Broadcast. They have acknowledged the problem on their status page located at: https://smsbroadcast.statuspage.io/

3. identified Feb 09, 2026, 02:49 AM UTC

   Further information about the SMS delivery issue... Telstra has confirmed the issue on their end and they are currently working to resolve it. SMS delivery and sending may continue to be impacted. Some SMS messages are being delivered but the majority are "Enroute"

4. monitoring Feb 09, 2026, 03:44 AM UTC

   Studentnet is starting to see the successful delivery of outbound SMS text messages but we have yet to receive confirmation from either SMS Broadcast or Telstra that the issue has been resolved.

5. resolved Feb 09, 2026, 03:58 AM UTC

   The incident has been reolved. We will be requirng further information from our gateway. Please report any further issues to (02) 9281 1626.

Read the full incident report →

Started Jan 08, 2026, 08:22 PM UTC· resolved Jan 09, 2026, 09:41 PM UTC

1. investigating Jan 08, 2026, 08:22 PM UTC

   We are receiving alerts from Sendgrid that some Microsoft mail receiver servers are rate limiting are attempts to send mail to them. We have commenced a process with Microsoft to lift the rate limit being applied to us. This is only affecting non-commercial Microsoft email addresses and only affecting Microsoft email addresses(eg hotmail.com, live.com, msn.com and outlook.com). Non-commercial Microsoft mail servers are the smallest category of mail servers receiving our email traffic. Microsoft 365 mail servers are unaffected as are all other mail services(gmail etc). We estimate that this is affecting about 10% of our mail delivery sends.

2. investigating Jan 09, 2026, 09:39 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 09, 2026, 09:40 PM UTC

   We are continuing to investigate this issue.

4. resolved Jan 09, 2026, 09:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 18, 2025, 10:53 PM UTC· resolved Dec 19, 2025, 08:20 AM UTC

1. investigating Dec 18, 2025, 10:53 PM UTC

   Studentnet is aware of a login issue affecting schools using the Edumate SIS. The cause appears to be related due to an upgrade distributed by Edumate. Any school experiencing this issue is advised to log a ticket with Edumate by either: - sending an email to [email protected] or - calling them on 1300 309 931. All Studentnet systems are operational and fully functional. Studentnet is liaising directly with Edumate.

2. resolved Dec 19, 2025, 08:20 AM UTC

   Configuration change has now been completed for new Edumate communication protocol.

Read the full incident report →

Started Aug 03, 2025, 11:30 PM UTC· resolved Aug 04, 2025, 12:39 AM UTC

1. investigating Aug 03, 2025, 11:30 PM UTC

   We are investigating a back end performance issue affecting login spead and failed login attempts.

2. monitoring Aug 03, 2025, 11:46 PM UTC

   Corrective action has been taken. This appears to have alleviated the immediate issue. Further investigation is underway for a permanent solution. Please report any failed logins to (02) 9281 1626.

3. resolved Aug 04, 2025, 12:39 AM UTC

   Immediate incident has been resolved. Longer term investigation is underway to avert any future occurrence. A PIR will be issued upon completion of investigation. Please report any login problems immediately to (02) 9281 1626.

Read the full incident report →

Started Jul 23, 2025, 03:55 AM UTC· resolved Jul 23, 2025, 04:30 AM UTC

1. monitoring Jul 23, 2025, 03:55 AM UTC

   AWS have reported "an issue that impacts the availability of some EC2 instances in the ap-southeast-2 Region". This issue may have temporary impact on the responsiveness of some Studentnet services.

2. resolved Jul 23, 2025, 04:30 AM UTC

   AWS have advised that their issue has been resolved: "Between Wed, 23 Jul 2025 03:11:09 GMT and Wed, 23 Jul 2025 04:20:00 GMT, a subset of EC2 instances were unavailable in the ap-southeast-2 Region. The issue has been resolved and the service is operating normally. "

Read the full incident report →

Started Oct 25, 2024, 09:59 AM UTC· resolved Oct 25, 2024, 05:35 PM UTC

1. identified Oct 25, 2024, 09:59 AM UTC

   AWS outage affecting ECS in the whole of the Sydney region

2. monitoring Oct 25, 2024, 10:45 AM UTC

   AWS services are beginning to come back online. We're waiting on final confirmation that all service is fully restored.

3. identified Oct 25, 2024, 10:49 AM UTC

   Services are still being affected - awaiting update.

4. identified Oct 25, 2024, 11:43 AM UTC

   AWS Health Service update: "We continue to see increased API error rates in the ap-southeast-2 Region. The issue is impacting one of the three cells for ECS in the region. Engineers are actively engaged and working to resolve the issue. We will provide additional updates as we have them available."

5. monitoring Oct 25, 2024, 12:33 PM UTC

   Services have stabilised. Formal notification from AWS is still pending so the issue is still being monitored by our team. Upon formal notification from AWS the issue will be marked as resolved and a PIR will be forthcoming.

6. resolved Oct 25, 2024, 05:35 PM UTC

   As of midnight 25/10, AWS has marked the issue as resolved. Services have been stable for over 4 hours. Follow up is now being sought from AWS as to cause, and preventative measures to ensure no recurrence. Studentnet PIR will follow and will be attached to this incident and will be available from this status page.

Read the full incident report →