Around lunchtime on Thursday 6th November 2025 it appears that AEMO suffered from some data glitch, which:
1) Created (the appearance of) a rapid ramp in ‘Market Demand’ in the Victorian region … but which was not there in reality
2) Ramping up units to meet this (phantom) increase in demand
3) Which overcooked the system frequency, driving it well beyond the NOFB.
In this category there is a series of articles that explore.
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.
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.
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...
This afternoon we saw mainland frequency briefly step above its normal operating band for approximately 20 minutes — potentially the result of a data glitch. In this quick piece, we unpack some market dynamics while it unfolded.
In the first hasty article about today's (Thu 6th Nov 2025) frequency spike, we see it quickly went past the NOFB. So, in this article, we look at how far ...
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.
A short note with this snapshot from our live frequency reading over the past hour showing a spike well outside of the Normal Operating Frequency Band on Thursday 6th November 2025