Core Practice Outage History

Core Practice is up right now

There were 4 Core Practice outages since February 4, 2026 totaling 57h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.corepractice.com.au

Major April 28, 2026

Logged out when Generating Invoices

Detected by Pingoru
Apr 28, 2026, 11:12 PM UTC
Resolved
Apr 29, 2026, 08:23 AM UTC
Duration
9h 11m
Affected: Core Practice Application
Timeline · 8 updates
  1. investigating Apr 28, 2026, 11:12 PM UTC

    We are aware of an issue with generating invoices and are currently investigating. We apologise for the inconvenience and will provide an update in 15 mins.

  2. identified Apr 28, 2026, 11:31 PM UTC

    We have identified a permission issue that is affecting a number of users. A hotfix is currently being prepared, and we will have a further update in the next 15mins.

  3. identified Apr 28, 2026, 11:50 PM UTC

    We are continuing to work on the hotfix for the permission issue affecting invoice generation. Our development team has identified the root cause and the fix is currently being prepared and tested before deployment. We will provide a further update in 30 minutes, or sooner if the hotfix is ready to deploy. We appreciate your patience while we work to resolve this.

  4. identified Apr 29, 2026, 12:25 AM UTC

    The hotfix for the permission issue affecting invoice generation has been completed and is now being packaged for deployment. We will provide a further update once deployment is underway, or within 30 minutes — whichever is sooner. We appreciate your patience while we work to resolve this.

  5. identified Apr 29, 2026, 01:27 AM UTC

    Apologies for the delay in this update. The hotfix has been completed and is currently undergoing final testing before deployment. We will provide a further update once deployment begins. We appreciate your patience while we work to resolve this

  6. identified Apr 29, 2026, 02:10 AM UTC

    The hotfix has completed testing and is scheduled for deployment between 12:30pm and 1:00pm AEST. Users may experience brief intermittent slowness during the window. We will provide a further update once deployment is complete and the fix has been verified. We appreciate your patience while we work to resolve this.

  7. monitoring Apr 29, 2026, 03:11 AM UTC

    The hotfix has been deployed. We are now monitoring the system to confirm the issue is fully resolved. Users should now be able to generate invoices as normal. If you continue to experience issues, please contact support. We will provide a further update shortly to confirm full resolution.

  8. resolved Apr 29, 2026, 08:23 AM UTC

    Summary: Between 07:00 AEST and 13:00 AEST, a number of users were unexpectedly logged out when attempting to generate invoices. The issue was caused by a regression in the most recent application release. A hotfix was deployed between 12:30pm and 1:00pm AEST and testing confirmed users are no longer being logged out. We will continue to monitor closely. Investigation: Telemetry indicated a consistent pattern of authorisation failures on an endpoint called during the invoice generation workflow. Further review identified that recent changes were causing some users to be logged out when this response was received, rather than handling it gracefully. Next Steps: The hotfix has corrected the client-side handling of these responses. Some users may need to refresh their browser to receive the updated application files. A problem ticket has been raised to review our pre-release testing process, specifically to ensure least-privileged user scenarios are covered in regression testing for permission-sensitive workflows. We apologise for the inconvenience caused and thank affected users for their patience.

Read the full incident report →

Minor March 5, 2026

Platform performance degradation

Detected by Pingoru
Mar 05, 2026, 05:37 AM UTC
Resolved
Mar 05, 2026, 07:12 AM UTC
Duration
1h 34m
Timeline · 4 updates
  1. investigating Mar 05, 2026, 05:37 AM UTC

    We are currently investigating elevated CPU utilisation on some instances, which may cause intermittent slowness for some users. Our team is monitoring the situation and working to stabilise performance. We will provide further updates as more information becomes available.

  2. investigating Mar 05, 2026, 05:58 AM UTC

    The performance issue has now subsided and system performance has returned to normal levels. Our team will continue to monitor the platform closely to ensure ongoing stability. We apologise for the inconvenience and appreciate your patience.

  3. monitoring Mar 05, 2026, 06:01 AM UTC

    The earlier performance degradation has now stabilised and services are operating normally. Our team will continue monitoring the environment to ensure stability. We apologise for any inconvenience caused and appreciate your patience.

  4. resolved Mar 05, 2026, 07:12 AM UTC

    Status: Resolved Summary: Between 16:20 and 16:45, we experienced elevated CPU utilisation across multiple instances, which caused intermittent slowness for some users. The affected servers have since stabilised and were progressively returned to the pool, with all instances restored by approximately 17:20. Investigation: Initial monitoring through DataDog did not show a common request pattern across the affected servers. Further review of instance logs indicates a consistent sequence of events: spikes in network traffic → RAM saturation → CPU spikes. Next Steps: A detailed log analysis is currently underway to determine the root cause. A problem ticket has been raised to track the investigation and any corrective actions. We apologise for any inconvenience caused and will continue to monitor system performance closely.

Read the full incident report →

Major February 25, 2026

Performance Degradation

Detected by Pingoru
Feb 25, 2026, 12:42 AM UTC
Resolved
Feb 25, 2026, 06:10 AM UTC
Duration
5h 28m
Timeline · 5 updates
  1. investigating Feb 25, 2026, 12:42 AM UTC

    We are aware of a current issue that is partially affecting system performance. Some users may experience intermittent slowness, while other areas of the platform remain fully operational. Our technical team is actively investigating the cause and working to restore full performance as quickly as possible. We are closely monitoring the situation and prioritising resolution. We will provide a further update once the issue has been resolved or if there are any significant developments.

  2. identified Feb 25, 2026, 01:34 AM UTC

    We have provisioned additional servers to stabilise system performance while our investigation continues. We are currently observing recovery in server load levels and overall response times are improving. Our team will continue to closely monitor the environment to ensure stability is maintained. Further updates will be provided as necessary.

  3. investigating Feb 25, 2026, 01:34 AM UTC

    We are currently investigating this issue.

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

    Server performance has returned to normal levels and services are operating as expected. We will continue to monitor the system closely to ensure ongoing stability.

  5. resolved Feb 25, 2026, 06:10 AM UTC

    Between 10:55am and 12:05pm 25/02/2026, we saw resource spikes on some of our front end instances. The issue has been resolved, additional servers were provisioned to stabilise performance and server load has returned to normal levels. Response times are back to expected benchmarks. Root cause investigation is ongoing. A post-incident report will be published once completed.

Read the full incident report →

Minor February 4, 2026

Inbound SMS Delivery Issues

Detected by Pingoru
Feb 04, 2026, 05:06 AM UTC
Resolved
Feb 05, 2026, 10:46 PM UTC
Duration
1d 17h
Affected: SMS CARRIER NETWORK - APAC
Timeline · 4 updates
  1. identified Feb 04, 2026, 05:06 AM UTC

    Identified We are aware of an issue impacting inbound SMS messages for a subset of Australian phone numbers. Core Practice uses Twilio as our SMS delivery provider. Twilio has confirmed an incident on their platform where some inbound SMS messages are not being received. Their engineering team has identified the cause and is actively working on deploying a fix. Impact Inbound SMS replies may be delayed or not received for some Australian numbers. We are monitoring the situation closely and will provide further updates as more information becomes available from Twilio.

  2. identified Feb 04, 2026, 10:43 PM UTC

    Twilio has confirmed they have identified the cause of the issue impacting inbound SMS messages for a subset of Australian phone numbers and are continuing to deploy a fix. Inbound SMS replies may still be delayed or not received for some numbers at this time. Outbound SMS messages continue to send as expected. Twilio expects to provide another update within 24 hours, or sooner if additional information becomes available. We will continue to monitor the situation closely and share further updates as they are provided.

  3. monitoring Feb 05, 2026, 04:49 AM UTC

    Twilio has advised they are seeing recovery for the issue impacting inbound SMS messages for a subset of Australian phone numbers. Inbound SMS replies may now be successfully received, however some delays may still occur while full recovery is confirmed. Outbound SMS messages continue to send as expected. We will continue to monitor the situation closely and will provide another update within 2 hours, or sooner if more information becomes available.

  4. resolved Feb 05, 2026, 10:46 PM UTC

    Twilio has confirmed the issue impacting inbound SMS messages for a subset of Australian phone numbers has been resolved. We are no longer seeing delivery issues and inbound SMS messages are functioning as expected. Outbound SMS messages were not impacted during this incident. We will continue to monitor, but no further action is required at this time.

Read the full incident report →

Looking to track Core Practice downtime and outages?

Pingoru polls Core Practice's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Core Practice reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Core Practice alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Core Practice for free

5 free monitors · No credit card required