Is Tideways down?

Tideways operations team is aware of the upcoming critical PHP security release and preparing for responses as more information and patches are becoming available. We are updating you here on this page about our progress. Tideways is not only monitoring your PHP applications, the servier side of Tideways is also written in PHP itself. So as the day continues we are not ruling out to shut down Tideways for a short period of time should this become necessary. Related: * https://www.php.net/archive/2026.php#2026-10-20-1

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Packages have been released and are currently rolled out on our systems. We will keep monitoring the situation and keep you posted.

Updates went smooth, everything looks good on our end. We will keep monitoring our systems closely for a few more hours. Thank you for your patience and best of luck with your updates.

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.

We are currently investigating this issue.

We are continuing to investigate this issue.

A maintenance query rolled out during a deployment caused more load than expected, overloading the server. The query was aborted and is now being rolled back, still taking time to process. We hopefully expect the process to be completed in a few minutes.

Database is responsive again.

## **Summary** A maintenance query to delete old entries in a large table was not adequately optimized and required a lot of load. This brought the primary database server under heavy load. Cancelling the query lead to a rollback that also took a while for the system to recover finally. Customers experienced a dataloss of incoming data between 13:42 and 14:28 UTC time on October 16th, 2026. We are very sorry for the inconvenience and you can be assured that we are following up on this incident to make sure a similar mistake does not happen again and is otherwise softened by better automatic recovery and retry mechanisms. ## **Timeline** * **13:30 UTC** - Maintenance query to large table was started. * **13:42 UTC** - Database server load increased to a level that made UI/Ingest unavailable. * **13:49 UTC** - query was killed and started to roll back. * **14:28 UTC** - system recovered and load normalized. ## **Root Cause** An unoptimized maintenance SQL query to cleanup a large table caused high load. ## **Impact** * ~45 minute total data gap across customers \(13:42–14:28 UTC\) * Possible transient UI errors during the incident window ## **Follow-ups** * Current defined best-practices from Ops team were not followed for the maintenance query, so work is being done on reviewing them in the team and potentially surfacing them during code-reviews automatically. * We are investigating how the retry mechanism of daemons from customer machines worked and if we can optimize and improve it for the future.

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.