Due to a database issue related to the MMS 5.3 update, the NemPrices widget was unavailable and/or showing stale dispatch intervals from 10:10 NEM time through 11:10 NEM time.

This problem has now been resolved, but you may need to click the “refresh” button on the NemPrices widget in ez2view to get the latest data.

Due to an apparent data gap caused by a new unit in the next day public bid files as produced by AEMO for trading day 2024-03-04, all FCAS bids displayed in ez2view may have been incomplete, slow to load, or not visible at all in ez2view this morning.

This has now been resolved.

From midnight on Saturday Feb 3rd through approx 7:45am NEM time our Trends engine which provides functionality that backs NEMReview online and Trends editor in ez2View (amongst other things) was unavailable.

The issue was caused by an upstream data provider fixing a typo in a single entry, which led to a duplicate data error at our end, which in turn caused the trends engine to fail to start up.

We apologise for the downtime and we are investigating ways to be more resilient to this kind of failure in the future.

Due to a number of compounding issues, the Live Supply Demand widget was showing data 5 minutes behind real time for the whole day starting midnight NEM time.

At around 3:40pm NEM time, the web service host attempted to restart the widget backend, but it was unable to restart successfully. Clients attempting to access Live Supply Demand from this time would have seen either a blank page or a “ 503” error.

The widget was back online at around 4:40pm NEM time.

Some real time SCADA data was not loaded into the full-history hosted MMS database between approx 11:40AM and 12:05PM NEM time. This affected the timely data presentation in some NEMreview trends and generation of up to date Live Supply Demand data. NEMwatch fuel type data may also have been affected during the time period.

The cause was a backlog of older market data files being back-filled into the database at the time, which consequently blocked real-time inserts of SCADA data.

We are reviewing our procedures for back-filling data to avoid a recurrence of this kind of issue.