This isn’t a single‑provider blip or a handful of confused users; it’s a repeating platform issue that’s been popping up in forum history for quite a while. Any official word? Incident ID? Status page note? Even “we’ve reproduced it and are digging” would help. Right now we just keep getting scattered “works for me / try again/ it’s an anthropic bug” replies while the error persists across all models. Happy to supply timestamps, logs, whatever. I’ve practically memorized the banner—might print it on a mug soon. Could we consolidate these threads and get a central update? Thanks.