deco - Notice history

Our infrastructure provider blocked the problematic IP from being associated with our machines, and the issues related to this query ceased.

VTEX's team responds, confirming that only one IP was blocked and had been since 2021. However, this specific IP had started generating traffic volume from March 6th, coinciding with the start of the incident.

VTEX informs us of the blocked IP and indicates that action could be taken on Monday.

We contacted our infrastructure provider requesting the rotation of this IP and its exclusion from allocation to our sites.

We are continuing to work on a fix for this incident.First contact made with VTEX, accompanied by all collected evidence.

Throughout the day, manual interventions were carried out on the stores to reduce the number of errors, such as redeployments, blocking potential bots, and reducing calls to VTEX. Efforts were also made to enhance error logging to pinpoint the root cause.

The team observes a recurrence of the error across different stores, with the common denominator being the integration with VTEX. Initial suspicions were towards VTEX throttling, as not all VTEX customers were affected, and those who were did not experience it 100% of the time.

This incident has been resolved.

We are investigating reports of other sites experiencing failures.

Deno Deploy has identified an issue and is actively working on a solution.

We have escalated the issue to Deno Deploy. It appears to be related to Deno KV and is primarily affecting sites utilizing the experimental loader cache feature.