openfeed status
Known issues affecting the openfeed platform, along with those originating upstream in the CDR ecosystem, and workarounds where they are available. Select an issue to view the full details.
Only current issues are listed. Once an issue is resolved it's removed from this page, so if something you were tracking no longer appears here, it has been fixed.
openfeed platform
Confirmed defects and known-broken behaviour in the openfeed platform — issues we own and are working to fix.
No known platform issues are currently reported.
Data holder issues
Problems that originate upstream at a bank or energy retailer's CDR implementation, or the CDR register — not in openfeed. We detect, verify and document them, and work around them where we can, but the fix sits with the data holder.
Missing token_type field breaks consent finalisation
Suncorp and ING return token responses without the token_type field, causing consent finalisation to fail with a parse exception.
First identified: 23 July 2026
ANZ credit card transactions returned with a null transactionId
ANZ returns some credit card transactions with a null transactionId, which is permitted where the field is conditional under CDR rules. openfeed generates a synthetic transaction ID so these transactions can still be ingested and served.
First identified: 20 July 2026
Report it in our developer community and we'll triage it — confirmed issues land on this page. It's also where we share workarounds and hear what you're building.
Join the openfeed Discord →
See also Error handling and theAPI reference.