We are doing our best to keep our services always up and running. Despite all commitment and caution it can happen that you experience a disruption of our services. While you and we rely on a number of third party services, the problem (and solution) may even be beyond our power. On this page we will log incidents with some background information of what happened and once the cause is known, the details will be shared.
Issue affecting dashboards and configuration pages for some customers (June 2026)
On 9 June 2026, between 16:48 UTC and 18:58 UTC, some Uptrends customers experienced failures when opening specific dashboards and other pages in the Uptrends application.
The issue was limited to parts of the web application used to display or configure data. Monitoring execution and alerting were not affected. The issue only affected accounts using private locations, but actual monitoring checks running from their private locations were not impacted.
Our team identified the issue and deployed a hotfix at 18:20 UTC, which temporarily restored service. We then deployed a durable fix across our web cluster. As of 18:58 UTC, our logs confirmed that the issue was resolved.
The underlying cause was an application-side limit being reached in one of the data retrieval paths used by the affected pages. We have adjusted this logic to prevent the same failure mode from recurring, and further review confirmed that this issue will not happen again.
We apologize for any inconvenience this caused. If you have questions about this incident, please contact our Support team.
SMS Gateway outage (August 2025)
On 15 August 2025, we identified issues with our primary Europe SMS gateway (SMS Gateway based in Europe). Our system automatically failed over to SMS Gateway 2 based in Europe for SMS delivery.
Incident details
- Affected service: SMS alerting (Europe)
- Impact: SMS alert delivery was routed through the secondary Europe SMS gateway while the primary gateway was unavailable.
The primary Europe SMS gateway has been restored and operational.
We apologize for any inconvenience this may have caused.
Incident affecting transaction monitors (April 2025)
Between 1 April and 3 April, transaction monitors reported an incorrect total time metric for measurements made from specific checkpoint locations.
Incident details
- Affected service: Transaction monitors
- Start time: 1 April 2025, 10:20 CET
- End time: 3 April 2025, 11:40 CET
- Impact: Incorrect total time metrics for measurements from specific checkpoint locations
Next steps
-
Uptime recalculation: We acknowledge inaccuracies in total time metrics for affected measurements during this incident. For more information about clearing errors and recalculating your uptime, please see this knowledge base article.
-
Alert reviewing: We recommend reviewing any alerts received during this time frame for accuracy.
We understand the importance of accurate monitoring and the inconvenience this may have caused. The problem was fully resolved by 11:40 CET on 3 April 2025, and we have taken steps to prevent such incidents in the future.