Details:
▎ - Rovo was working until approximately June 26, 2026
▎ - Now shows "Something went wrong" when using Rovo chat in Jira
▎ - Browser DevTools shows 403 on use-rovo-chat-eligibility endpoint
▎ - Rovo Settings page in admin.atlassian.com shows "An error occurred while loading bookmarks"
▎ - Rovo access blocklist is clean (only Compass)
▎ - Atlassian Intelligence is enabled
▎ - No changes made on our side around the time it broke
▎ - There was a similar issue on June 15-17 at https://rovo.status.atlassian.com/, Rovo access blocklist incident — this may be a lingering effect
▎ Please check Rovo entitlements and service status, if you need more details let me know please.
NOTE: Last week we added IP Allowlist to include all Rovo IPs and Rovo started working, but then got broken again.
Hi @Vadym Chu ,
I can just say that I've experienced the same/similar thing on Friday or Saturday. Haven't used Rovo much today, so can't comment much on how things look now.
Although I didn't experience a full outage - only specific chats were 'broken '- I could resume work within a couple of minutes or an hour. 👀
What you (or any other app admin on your site) could do is reach out to Atlassian Support. To raise a ticket, I believe you could simply select any other paid app (in case the system automatically redirects you to the Community forums when you select 'Rovo') and submit this.
Cheers,
Tobi
@Vadym Chu welcome to the community. Since the 403 is coming from Rovo’s eligibility check and your blocklist/configuration hasn’t changed, I’d avoid chasing local fixes too far. IP allowlists can affect Rovo/MCP access, but if the required ranges are already allowed and the failure affects Rovo Chat itself, Atlassian Support should verify the site/user entitlement state and backend logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.