Every monitored K15t GmbH system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.
Operational·Checked just now·Live · 60s while moving
Know the moment K15t GmbH breaks
K15t GmbH is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.
Free, no password, no card. Unsubscribe in one click.
How we know: the official K15t GmbH status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works
K15t GmbH Component Status
The main K15t GmbH systems on this page. All 12 are operational right now.
12operational
Backbone Issue Sync for Jira
Operational
Scroll Apps for Confluence » Scroll Content Quality
Operational
Scroll Apps for Confluence » Scroll Documents
Operational
9 more components tracked
Their status is in the bar above. Free accounts see every component by name.
Also tracking Scroll Apps for Confluence » Scroll Exporter Extensions, Scroll Apps for Confluence » Scroll HTML Exporter, Scroll Apps for Confluence » Scroll ImageMap, Scroll Apps for Confluence » Scroll PDF Exporter, Scroll Apps for Confluence » Scroll Sites, Scroll Apps for Confluence » Scroll Viewport, Scroll Apps for Confluence » Scroll Word Exporter, Scroll Apps for Confluence » Translations for Scroll Documents, Scroll Apps for Confluence » Variants for Scroll Documents.
Component statuses may change independently during partial outages.
Recent K15t GmbH Outages & Incidents
Incident history from the official K15t GmbH status page, including resolution updates.
Scroll ImageMap may not loadResolved Aug 5, 2026 · 15h 4mResolved
## Summary
On August 5, 2026, between 12:00 AM and 2:30 PM UTC, users of K15t’s Scroll Exporter apps and Scroll ImageMap experienced service disruption across all cloud regions. During this window, attempted exports failed for Scroll Exporter apps, and Scroll ImageMap content failed to render on Confluence pages. The incident was caused by an upstream change on Atlassian’s platform that blocked access to an API endpoint required for normal app operation. Upon detecting the issue, we immediately escalated it to Atlassian, who rolled back the change across Cloud instances. In parallel, our engineering team deployed a fallback fix to automatically reroute requests to an alternative API endpoint if the primary one becomes unavailable. Full service was restored for all affected apps once these changes were deployed.
## Impact & Scope
The incident affected Confluence customers across all Cloud regions and tenants on August 5, 2026, between 12:00 AM and 2:30 PM UTC.
* **Scroll Exporter Apps \(PDF, Word, HTML\):** Export functionality was completely unavailable during the incident window. Users attempting to export received an error notification in the Confluence UI upon failure.
* **Scroll ImageMap:** Image-related content and corresponding hotspot navigation links failed to display within Scroll ImageMap macros on Confluence page views.
## Root Cause & Resolution
The incident was caused by a configuration change on Atlassian's side affecting a Confluence Cloud REST API endpoint. The change resulted in requests to this endpoint being blocked, causing follow-up errors in Scroll PDF, Word, and HTML Exporters as well as Scroll ImageMap.
Upon detection, we escalated the issue to Atlassian as a Priority 1 ticket. Atlassian subsequently deployed a hotfix reverting the change and restoring access to the blocked endpoint. In parallel, we also deployed cloud updates enabling our apps to automatically failover to an alternative endpoint whenever the primary endpoint is unavailable.
Normal service for the Scroll Exporters was fully restored by 14:30 UTC on August 5, 2026.
Full rendering capability for Scroll ImageMap was also restored on August 5, 2026, with extended monitoring continuing until August 6, 2026 at 06:30 UTC, when the incident was officially marked as resolved.
## Remedial Actions Plan & Next Steps
We know how critical these apps are to your team's day-to-day work, and we apologize for the disruption caused by this incident. To prevent similar issues and improve our response in the future, we are prioritizing the following actions:
* **Strengthen vendor communication:** Establish tighter communication channels with Atlassian regarding planned API and platform changes to safeguard against unexpected breaking updates.
* **Enhance monitoring and alerting:** Evaluate our monitoring tooling to identify coverage gaps and enable faster automated detection of upstream endpoint failures.
* **Implement in-app incident alerts:** Improve user visibility during incidents by embedding status updates directly within our app interfaces, linked to the [K15t status page](https://status.k15t.com/).
Thank you for your patience and understanding while we resolved this issue, and please don't hesitate to reach out to our support team via [help@k15t.com](mailto:help@k15t.com) if you have any further questions.
Thanks,
The K15t Team
---
[2026-08-06T08:30:14.445+02:00] (resolved) Every instance of Scroll ImageMap is back to normal again.
---
[2026-08-05T17:26:05.372+02:00] (investigating) We are investigating this issue.
Scroll Exporter apps and Scroll ImageMap affected by Atlassian changeResolved Aug 5, 2026 · 8h 53mResolved
## Summary
On August 5, 2026, between 12:00 AM and 2:30 PM UTC, users of K15t’s Scroll Exporter apps and Scroll ImageMap experienced service disruption across all cloud regions. During this window, attempted exports failed for Scroll Exporter apps, and Scroll ImageMap content failed to render on Confluence pages. The incident was caused by an upstream change on Atlassian’s platform that blocked access to an API endpoint required for normal app operation. Upon detecting the issue, we immediately escalated it to Atlassian, who rolled back the change across Cloud instances. In parallel, our engineering team deployed a fallback fix to automatically reroute requests to an alternative API endpoint if the primary one becomes unavailable. Full service was restored for all affected apps once these changes were deployed.
## Impact & Scope
The incident affected Confluence customers across all Cloud regions and tenants on August 5, 2026, between 12:00 AM and 2:30 PM UTC.
* **Scroll Exporter Apps \(PDF, Word, HTML\):** Export functionality was completely unavailable during the incident window. Users attempting to export received an error notification in the Confluence UI upon failure.
* **Scroll ImageMap:** Image-related content and corresponding hotspot navigation links failed to display within Scroll ImageMap macros on Confluence page views.
## Root Cause & Resolution
The incident was caused by a configuration change on Atlassian's side affecting a Confluence Cloud REST API endpoint. The change resulted in requests to this endpoint being blocked, causing follow-up errors in Scroll PDF, Word, and HTML Exporters as well as Scroll ImageMap.
Upon detection, we escalated the issue to Atlassian as a Priority 1 ticket. Atlassian subsequently deployed a hotfix reverting the change and restoring access to the blocked endpoint. In parallel, we also deployed cloud updates enabling our apps to automatically failover to an alternative endpoint whenever the primary endpoint is unavailable.
Normal service for the Scroll Exporters was fully restored by 14:30 UTC on August 5, 2026.
Full rendering capability for Scroll ImageMap was also restored on August 5, 2026, with extended monitoring continuing until August 6, 2026 at 06:30 UTC, when the incident was officially marked as resolved.
## Remedial Actions Plan & Next Steps
We know how critical these apps are to your team's day-to-day work, and we apologize for the disruption caused by this incident. To prevent similar issues and improve our response in the future, we are prioritizing the following actions:
* **Strengthen vendor communication:** Establish tighter communication channels with Atlassian regarding planned API and platform changes to safeguard against unexpected breaking updates.
* **Enhance monitoring and alerting:** Evaluate our monitoring tooling to identify coverage gaps and enable faster automated detection of upstream endpoint failures.
* **Implement in-app incident alerts:** Improve user visibility during incidents by embedding status updates directly within our app interfaces, linked to the [K15t status page](https://status.k15t.com/).
Thank you for your patience and understanding while we resolved this issue, and please don't hesitate to reach out to our support team via [help@k15t.com](mailto:help@k15t.com) if you have any further questions.
Thanks,
The K15t Team
---
[2026-08-05T17:23:35.735+02:00] (resolved) Scroll PDF Exporter, Scroll Word Exporter, Scroll HTML Exporter are since 14:30 UTC back to normal.
---
[2026-08-05T13:51:17.022+02:00] (monitoring) The issue should be mitigated for
Scroll PDF Exporter
Scroll Word Exporter
Scroll HTML Exporter
We will continue to closely monitor the situation.
---
[2026-08-05T13:29:07.239+02:00] (identified) Due to some unexpected platform issue from Atlassians end, there has been some delays in the deployment.
We are closely monitoring the situation and working in parallel to mitigate this issue.
---
[2026-08-05T12:07:33.401+02:00] (identified) Atlassian confirmed that the hotfix rollout should be complete by approximately 13:00 CEST.
---
[2026-08-05T11:24:46.218+02:00] (investigating) The deployment of the Atlassian hotfix has reached some tenants now but much of it is still in progress.
---
[2026-08-05T10:23:56.397+02:00] (investigating) Atlassian is currently rolling out a hotfix to resolve this problem.
We will leave another update once the rollout has been completed.
---
[2026-08-05T08:44:23.832+02:00] (investigating) Scroll ImageMap is also affected by this incident
---
[2026-08-05T08:30:41.495+02:00] (investigating) We are continuing to investigate this issue.
---
[2026-08-05T08:30:20.787+02:00] (investigating) We are aware of an incident that is causing Scroll Exporter exports on Confluence Cloud to fail.
We have reported this to Atlassian and they are currently investigating.
K15t GmbH Uptime History
Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a K15t GmbH incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.
Uptime history49 days observed
Aug 8100.00% averageSep 25
Live K15t GmbH Outage Reports
Problems reported by engineers using K15t GmbH. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.
Reports, last 24 hours0 total
24h agoNothing reportednow
No K15t GmbH problems reported yet.
Something wrong with K15t GmbH on your end?
Reports are anonymous, take about ten seconds, and help the next engineer who checks.
About K15t GmbH
Is K15t GmbH down? K15t GmbH reports live availability for 13 components at status.k15t.com, among them Scroll Documents, Variants for Scroll Documents and Scroll Apps for Confluence. Track K15t GmbH outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.
Over the past 30 days, PulsAPI has measured K15t GmbH uptime at 100.00%. Response times, incident history, and SLA tracking for K15t GmbH are available on the PulsAPI dashboard.
K15t GmbH Status FAQ
Is K15t GmbH down right now?
The verdict at the top of this page comes from the latest poll of the official K15t GmbH status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.
What should I do if K15t GmbH is not working?
Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until K15t GmbH recovers.
How do I check K15t GmbH uptime history?
PulsAPI tracks K15t GmbH uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever K15t GmbH changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.
How fast does PulsAPI detect K15t GmbH outages?
PulsAPI reads the official K15t GmbH status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.
Does PulsAPI track individual K15t GmbH components?
Yes. PulsAPI monitors 12 individual K15t GmbH components, so you can see which service or region is affected instead of a generic "service degraded" banner.
Can I get alerts when K15t GmbH goes down?
Yes. Create a free account and subscribe to K15t GmbH: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.
How do I report an issue with K15t GmbH to the community?
Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot K15t GmbH problems early. Official status pages often lag real incidents by 10 to 20 minutes.
Is there a free way to monitor K15t GmbH?
Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so K15t GmbH plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.
Track K15t GmbH with the rest of your stack
2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.