Their log delivery api is delayed by over 3 days, despite them promising only "up to 5 minutes delay" in their docs: https://docs.bunny.net/cdn/logging
Why isn't it on the status page you might ask? Oh, that's because a delay is not "critical", but I fear I am losing loglines now, their retention is 3 days.
It's an interesting strategy for them, because it doesn't inspire confidence in me about their other offerings. When they can't reliably operate a log delivery API or be transparent about issues, it's hard to trust them with something as critical as a database.
We’re currently working through a backlog of approximately 2.5M log files. I’ve spent the last day optimizing our backlog processing pipeline, which has significantly increased throughput.
Based on the current processing rate, we expect the backlog to be fully cleared within the next 12–18 hours (estimate), and real-time log delivery should progressively return closer to real-time as the backlog drains.
Apologies for the inconvenience this has caused. We’re also in the process of migrating away from our existing logging infrastructure to a ClickHouse-based system to significantly improve reliability and throughput and prevent this from happening again.
We’ve published a status page incident and will continue posting updates there as progress is made.
Thank you for your update, it's really appreaciated, it will be good to get this sorted :) It sounds like quite a challenge you're working on with the ingest and backlog!