pingoru pingoru Tideways had 11 outages in the last 2 years totaling 28h 29m of downtime, averaging 0.5 incidents per month.
There were 11 Tideways outages since April 2, 2025 totaling 28h 29m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Like this afternoon, we are seeing network issues in our data center, leading to some requests failing and some working. We have contacted the hosting provider to fix the problem.
Recovered on its own for now.
We are currently experiencing a partial outage of our hosting infrastructure. We are in contact with our hosting partner to resolve the issue.
Stability is still not fully there, but incoming data is processed and the backlog is slowly shrinking. We keep monitoring the situation and keep you updated.
System performance is still not back to 100 percent but seems to have stabilized. Backlogs still need quite some time to catch up, we will keep you posted.
The measurements data backlog has been cleared (section "Performance"), while trace processing is still lagging. If current performance keeps up, we expect the outstanding traces to be processed in the next hours. If anything in this prediction changes, we will update you with the new information.
We estimate the remaining backlog to be cleared by 4-5pm UTC. Other than that, everything is back to normal operations. Thank you for your patience.
All queues have caught up. Data is up-to-date and everything is operational.
Trace processing is currently delayed. We suspect degraded I/O performance on our servers and are working with our hosting provider to investigate.
We confirmed the I/O latency issues and are working on a quick solution. Processing speed has already improved and the backlog is no longer growing. We are monitoring the situation and keep you updated of any changes to the situation.
Trace processing speeds are back to normal. The backlog is currently processed and will be fully caught within the next 30-60 minutes.
The MySQL database server is currently unavailable, leading to an outage of all services of Tideways.
After recovering our MySQL database server, everything is back online. Sorry for the interruption.
Following performance issues in our data collection pipeline (https://status.tideways.io/incidents/fg5p17f0rsrl) we have temporarily reduced the number of traces collected to roughly 80%. We expect to lift this limit on July, 8th around 11:00-14:00 CEST, when additional servers have been provisioned.
Trace collection rate is back to 100%
We are investigating slow processing of historical data aggregation job.
The issue was identified as not locking the processing for the same application/project, which lead to all workers re-processing the same project which was taking a few minutes and then breaking with an out of memory error. Multiple fixes are now in place and the queue for historical data is processing to close the gap as soon as possible.
Processing queue has dropped from over 60k tasks to 39k tasks now. All historical data for June 12th have been processed and now those from June 13th are being processed as fast as possible.
Processing will be up to date in the next 60-90 minutes, before processing for June 14th gets scheduled. This restores equilibrium in processing historical data.
Due to Cloudflare having a major outage, our landingpage https://tideways.com is currently not reachable. The Tideways application can still be accessed through https://app.tideways.io You can find details about the Cloudflare outage on https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
We are continuing to monitor for any further issues.
A fix has been implemented on Cloudflare's end; our landingpage is back online.
Our hosting provider has a hardware node malfunction that affects the performance of data ingest and UI.
All hardware nodes are back up, UI and ingest performance are back to normal.