Bunnynet

Mar 6, 04:43 UTC
Resolved - This incident has been resolved.

Mar 5, 23:45 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 5, 15:29 UTC
Investigating - Our Engineering team are aware of and currently working to address Log Forwarding failures. Any zones configured with Log Forwarding is affected. Standard logging is not affected.

Mar 4, 14:32 UTC
Resolved - Migration to our new Logging Platform is now complete, and near real-time logs should be visible again.

Unfortunately, we had to accelerate the migration timeline as our legacy platform began struggling much sooner than expected. Because of this, we made the difficult decision to complete the migration before fully backfilling the expected 3 days of retained logging history.

At the moment, approximately 1.5 days of logs are available on the new platform. This will gradually increase and return to the full 3-day retention by Friday.

The raw, unprocessed logs remain stored on the legacy logging platform. If you …

Mar 2, 11:21 UTC
Resolved - This issue is now resolved.

Mar 2, 10:15 UTC
Monitoring - Our Engineering team has applied a fix, and a delayed pull zone backlog of configurations are now processing. We will monitor the situation.

Mar 2, 09:18 UTC
Investigating - We are currently looking into pull zone configuration delays. Existing configurations and platform traffic are not affected.

Feb 22, 19:11 UTC
Resolved - The issue affecting one server in our German storage array has been fully resolved. All services are now operating normally. We will continue monitoring to ensure stability.

Feb 20, 16:13 UTC
Identified - We currently are experiencing an outage with one server within our German storage array. There may be isolated timeouts from Storage API, as well as timeouts on CDN, where no replication is enabled, or where some assets are uncached on the CDN network.

Our Engineering team are working to restore the server.

Feb 11, 22:32 UTC
Resolved - This is now fully resolved and the zone updates are publishing as normal.

Feb 11, 16:10 UTC
Monitoring - Our Engineering team has identified and applied a fix to a process causing propagation delays on zone configurations. There is a backlog of configurations to be applied as a result of the issue, and we are monitoring the situation.

Feb 11, 13:53 UTC
Investigating - We are currently investigating delayed zone configurations. This does not affect traffic on the platform