Degraded Performance on T‑Cloud Public (OTC)

Mon, 29 Jun 2026 09:51:00 +0000

(29. Jun, 16:19) Disrupted - The issue has been further isolated to a peering problem between T‑Cloud Public and AWS. T‑Cloud Public has involved their internet service provider for further investigation. At the moment, we are dependent on updates from third-party providers. We will share the next update by tomorrow 12:00 PM at the latest, or earlier if significant new information becomes available.

(29. Jun, 13:08) Disrupted - We are continuing to investigate the issue together with T‑Cloud Public (OTC). We still observe that only a small percentage of requests are impacted by timeouts and increased latency. At this stage, we have identified the issue as being related to network traffic between AWS and T Cloud Public. The root cause appears to be peering-related errors. Customers using our AWS-based offerings in combination with T Cloud Public-only products (e.g. d.velop sign) may experience intermittent issues. We will continue to provide updates as more information becomes available and will share the next update within 4 hours at the latest, or earlier if significant new insights arise.

(29. Jun, 09:51) Disrupted - We are currently observing increased latency and occasional timeouts affecting all products hosted on T‑Cloud Public (OTC). The issue started on 27 June at 09:30 UTC. A small percentage of requests are impacted by timeouts or delays. Due to resilient software design, the overall impact is low and most customers are unlikely to notice any disruption, although some may experience intermittent end‑to‑end issues. We are actively investigating the issue together with T‑Cloud Public (OTC) and will share further updates as soon as more information becomes available. We expect to provide the next update within 4 hours or earlier if significant new insights arise.

otc-contracts on status.d-velop.cloud

Degraded Performance on T‑Cloud Public (OTC)