Scroll Documents: Created or updated page content might be broken for legacy editor based storage format
Update - We are continuing to work on a fix for this issue.
Oct 22, 2025 - 11:07 CEST
Identified - We are searching for a solution together with Atlassian.
Oct 21, 2025 - 14:30 CEST
Uptime over the past 90 days. View historical uptime.
Scroll Apps for Confluence Degraded Performance
90 days ago
99.95 % uptime
Today
Scroll Documents ? Degraded Performance
90 days ago
100.0 % uptime
Today
Variants for Scroll Documents ? Degraded Performance
90 days ago
100.0 % uptime
Today
Translations for Scroll Documents ? Degraded Performance
90 days ago
100.0 % uptime
Today
Scroll Content Quality ? Operational
90 days ago
100.0 % uptime
Today
Scroll Viewport ? Operational
90 days ago
100.0 % uptime
Today
Scroll PDF Exporter ? Operational
90 days ago
100.0 % uptime
Today
Scroll Word Exporter ? Operational
90 days ago
100.0 % uptime
Today
Scroll HTML Exporter ? Operational
90 days ago
100.0 % uptime
Today
Scroll Sites ? Operational
90 days ago
97.93 % uptime
Today
Backbone Issue Sync for Jira ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 30, 2025

No incidents reported today.

Oct 29, 2025

No incidents reported.

Oct 28, 2025

No incidents reported.

Oct 27, 2025

No incidents reported.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025
Detecting Content Changes in Scroll Sites Does Not Work
Resolved - We monitored our webhook intake and have not observed further interruptions. We are resolving this incident now.
If you have applied changes to content (pages, blog posts, Scroll Documents) during the incident period (01:00 UTC to 21:00 UTC on 22/10/2025) these changes have not triggered updates on your Scroll Sites.
To resolve this you can either modify the affected pages again or trigger a full site update, as described here https://help.k15t.com/scroll-sites/manually-trigger-a-full-site-update
We apologise for the inconvenience.
Oct 23, 13:51 CEST
Update - We are continuing to monitor for any further issues.
Oct 23, 10:03 CEST
Monitoring - Atlassian has deployed a fix at 20:47 UTC on 22/10/2025. We can confirm the intake of webhooks starting at 21:06 UTC.
Atlassian has also communicated that webhooks for events during the incident will not be delivered. This means that any changes on content (pages, blog posts, Scroll Documents) you have applied during the incident period (01:00 UTC to 21:00 UTC on 22/10/2025) will not trigger updates on your Scroll Sites.
Oct 23, 08:33 CEST
Update - The problem report to Atlassian has been acknowledged and being worked on. Atlassian is tracking the incident here https://developer.status.atlassian.com/incidents/41ggtwj1f9f0
Oct 22, 14:27 CEST
Identified - We have become aware of a problem with change detection in Scroll Sites.
We have identified that Confluence is not sending any webhooks since 22/10/2025 ~3am GMT. We have informed Atlassian and are awaiting further information.
Oct 22, 11:22 CEST
Oct 22, 2025
Exported format (e.g. PDF, webpage) of newly created confluences pages could be broken.
Resolved - All exports are working as expected.
Oct 22, 11:01 CEST
Monitoring - All exports are working again.
Oct 21, 14:28 CEST
Update - Exporters are fully functional again. We communicate with Atlassian about the creation of "legacy"-pages by Scroll Documents.
Oct 16, 20:20 CEST
Update - There might be still some formatting issues with blog posts. Confluence pages are working again without layout issues. (Exports and publishing with Scroll Sites.)
Oct 15, 18:07 CEST
Update - We are working on fixing this issue and are planning to bring it on production tomorrow (Wednesday).
Oct 14, 10:59 CEST
Identified - We identified the issue.
For newly created confluence pages we don't get a specific content property.
We are in contact with Atlassian to find a solution/work around.
Oct 13, 17:38 CEST
Update - We are continuing to investigate this issue.
Oct 13, 15:30 CEST
Investigating - We are currently investigating this issue and are in contact with Atlassian.
Oct 13, 14:08 CEST
Oct 21, 2025
Oct 20, 2025

No incidents reported.

Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

Oct 17, 2025

No incidents reported.

Oct 16, 2025
← Incident History Powered by Atlassian Statuspage