Completed -
The scheduled maintenance has been completed.
Apr 17, 10:19 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 17, 10:00 CEST
Scheduled -
We will upgrade parts of our infrastructure. During this time, some functionality or workspaces will not be available. We appreciate your patience and understanding.
Apr 15, 10:27 CEST
Completed -
The scheduled maintenance has been completed.
Apr 11, 22:39 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 11, 22:00 CEST
Scheduled -
We will upgrade parts of our infrastructure. During this time, some functionality or workspaces will not be available. We appreciate your patience and understanding.
Apr 4, 10:40 CEST
Completed -
The scheduled maintenance has been completed.
Apr 10, 10:16 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 10, 10:00 CEST
Scheduled -
We will upgrade parts of our infrastructure. During this time, some functionality or workspaces will not be available. We appreciate your patience and understanding.
Apr 4, 10:39 CEST
Completed -
The scheduled maintenance has been completed.
Apr 9, 22:17 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 9, 22:00 CEST
Scheduled -
We will upgrade parts of our infrastructure. During this time, some functionality or workspaces will not be available. We appreciate your patience and understanding.
Apr 4, 10:37 CEST
Resolved -
Some of our customers have been utilizing a specific IP for their ServiceNow and Signavio integrations. In June 2023, we upgraded our infrastructure and informed our customers about the need to transition to new IP ranges. While the majority of customers have successfully migrated, a small number have yet to complete this transition.
On Tuesday, April 2nd at 12:46 UTC, during a routine maintenance procedure, the legacy IP unexpectedly became inaccessible.
The issue was first identified on Friday, April 5th at 8:32 UTC. Upon investigation, we discovered that the IP had been deallocated from Microsoft Azure and could not be reinstated. As a result, all affected customers will need to transition to the new IP ranges.
Apr 5, 08:30 CEST