Filters doesn't work on C-chain API endpoint

I’m playing around with the Web3J library, connected to the public C-Chain API RPC endpoint (https://api.avax.network/ext/bc/C/rpc).
While most features work as expected I’ve hit a problem with the log filters and I’d like to clarify a few things:

These are the relevant logs from the two involved calls (eth_newFilter, eth_getFilterLogs):

→ POST https://api.avax.network/ext/bc/C/rpc
Content-Type: application/json; charset=utf-8
Content-Length: 241
{“jsonrpc”:“2.0”,“method”:“eth_newFilter”,“params”:[{“topics”:[“0x0d3648bd0f6ba80134a33ba9275ac585d9d315f0ad8355cddefde31afa28d0e9”],“fromBlock”:“earliest”,“toBlock”:“latest”,“address”:[“0x9Ad6C38BE94206cA50bb0d90783181662f0Cfa10”]}],“id”:0}
→ END POST (241-byte body)

← 200 https://api.avax.network/ext/bc/C/rpc (840ms)
{“jsonrpc”:“2.0”,“id”:0,“result”:“0xfb0e666e8d8db3ed8ed5b3b50817061a”}
← END HTTP (70-byte body)

→ POST https://api.avax.network/ext/bc/C/rpc
Content-Type: application/json; charset=utf-8
Content-Length: 101
{“jsonrpc”:“2.0”,“method”:“eth_getFilterLogs”,“params”:[“0xfb0e666e8d8db3ed8ed5b3b50817061a”],“id”:1}
→ END POST (101-byte body)

← 200 https://api.avax.network/ext/bc/C/rpc (116ms)
content-type: application/json
{“jsonrpc”:“2.0”,“id”:1,“error”:{“code”:-32000,“message”:“filter not found”}}
← END HTTP (77-byte body)

i didn’t find details on this neither the Ethereum docs nor the Avalanche docs but based on these logs it seems such filters are implemented in a stateful manner. if so, it seems like a reasonable choice to disable this on a public endpoint which would be very quickly overwhelmed by artitrarily created filters.
Can somebody this? If yes, wouldn’t it be a better option to already reject the creation of the filter and not the subsequent retrieval? If no, what else could the the reason for this error?

Would this work out of the box on a own node or does this require special settings?

Any help and/or lobks to relevant docs is appreciated!