> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/release-notes/jun-25-2026-release.md). # Jun 25, 2026 release ### Rebuilt analytics We dropped by third-party analytics vendor and have rebuilt all of our dashboards from scratch. As a result, they now load much faster and have better drill down functionality. And data export is better. Operationally, it also simplifies a bunch of things for Bunny's engineering team so we now have more time to work on other things. ### Time travel When are you are dealing with recurring subscriptions and invoicing, it can be tricky to test what potentially happens with an account in the future. The new time travel feature allows you to fast forward time for a specific account. For every day traveled, Bunny will run billing, generate invoices, create renewals etc, which makes it much easier to test billing scenarios. This feature is only available in sandboxes. ### AccountsIQ payments sync The integration with AccountsIQ now also imports payment records into Bunny. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bunny.com/guide/release-notes/jun-25-2026-release.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.