K15t GmbH Outage History
6 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded K15t GmbH Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 5, 2026 | Scroll ImageMap may not load## 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… | 15h 4m | Resolved |
| Aug 5, 2026 | Scroll Exporter apps and Scroll ImageMap affected by Atlassian change## 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… | 8h 53m | Resolved |
| Apr 6, 2026 | Scheduled Maintenance for Scroll Exporter appsWe’ve concluded our maintenance work. All Scroll Exporter app features are now available again. If you run into any unexpected problems, please report them either via the in-app error reporting or by creating a support… | 4h 0m | Scheduled |
| Mar 24, 2026 | Scroll Exporter apps affected by Atlassian incidentThe original Atlassian incident has been resolved. | 1h 5m | Resolved |
| Nov 19, 2025 | Scroll Site search is not workingWe have been monitoring the Site Search closely and Site Search is fully operational. | 23h 14m | Resolved |
| Nov 14, 2025 | Scroll Site search is not workingWe have resolved the incident and site search is working since Friday 14:00 UTC. About 20 Scroll Sites that use the site update strategy 'Manual' still have to manually publish their next site version, which then will… | 73h 16m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next K15t GmbH incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This K15t GmbH Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before K15t GmbH acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single K15t GmbH outage in this window ran 3d 1h, against a mean recovery of 20h 55m. If you depend on K15t GmbH in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.