At 12:32:03 on Wednesday 12th August 2026, the AEMO published MN144798 which noted 'AGC Heart Beat has been resolved'. This obviously raises other questions we will be interested to learn more about...
In this 6th article relating to the data glitch triggered frequency excursion on Wednesday 5th August 2026, we take another look at interconnectors, and start compiling a sequence of events.
On Friday 29th May 2026, the AEMO alsodeclared Scheduling Errors (together anointed number 76), with respect to the joint glitches on Thu 6th Nov 2025 and Tue 11th Nov 2025.
Given prior analysis we'd written and published about two recent glitches (Fri 10th April and Sat 11th April 2026) it was not really a surprise, though it’s nice to know, that the AEMO declared both Scheduling Errors.
Yesterday one of our team members noted something strange at Wellington North Solar Farm ... here we take a quick look at the last few days and see a few things.
About the AEMO’s Reviewable Operating Incident Report ‘Self-forecasting errors and frequency excursion on 19 August 2025’.
We start with this unbundled listing of 402 discrete stories about the performance of Semi-Scheduled units (115 solar & 86 wind) units on Friday 10th and Saturday 11th April with the frequency spikes.
Presenting this single image which summarises the sequence of events (for a number of Semi-Scheduled units) over three dispatch intervals across the pair of frequency spikes (on Fri 10th and Sat 11th April 2026).
A number of our ez2view 'large change in demand' alerts have triggered this afternoon Monday 23rd March 2026 with respect to NSW. But what's a 'real' change and what's 'phantom' (with the SCADA issues)?
Yesterday afternoon/evening (Tuesday 10th March 2026) the AEMO experienced a significant glitch in operations. I’ve posted this short note here to provide a more easily-accessible permanent record that we (and others) might refer back to later…
A belated and back-dated article, dated for 19th February 2026, which was when the AEMO declared a ‘Scheduling Error’ – Incident #74 with respect to 16th October 2025
Adding to the list of articles we've collated about the frequency disturbance on Tuesday 19th August 2025, we're copying in what AEMO published in its 2025 Q3 monitoring report about the glitch.
In this article we take another step in trying to understand the source of the gremlins (on Thu 6th Nov 2025 and Tue 11th Nov 2025) that seemed to infect the dispatch process - inflating VIC 'Market Demand' with 'phantom' demand and driving frequency higher.
Following two instances of apparent data glitches (injecting 'phantom demand' and) driving frequency high, here's a collation of some other times (we've written about) where similar has happened.
In what seems to be a repeat of what happened last week Thursday 6th November 2025, some strange (and large) changes in 'Market Demand in Victoria appear to have driven a frequency excursion on Tuesday morning 11th November 2025
Today, we have the advantage of ‘next day public’ data, so are able to peel some more layers of the onion (in this article 'Dispatch Error') - with respect to the significant Frequency Spike on Thursday 6th November 2025 (which appears due to some gremlins...
Given the large ramp in frequency around midday Thu 6th Nov 2025, coincident with a large apparent ramp in 'Market Demand' in Victoria, we suspect a data glitch.
As the 5th article in an evolving series that progressively explores the (apparent self-forecasting glitch and) frequency spike on Tuesday 19th August 2025, we take an early look at Solar Farm performance.
The (concerning) frequency spike across the NEM in the middle of the day (Tuesday 19th August 2025) has triggered many proximate questions - understandable - but also has raised these 3 Broader Questions.
The incident description in the scheduling error declaration provides us with a glimpse into the underlying cause.