deco - Operational
Previous page
Next page
deno - Operational
deno
VTEX - Operational
VTEX
Third Party: Amazon Web Services (AWS) → AWS ec2-sa-east-1 - Operational
Third Party: Cloudflare → Cloudflare Sites and Services → API - Operational
Third Party: Cloudflare → Cloudflare Sites and Services → CDN/Cache - Operational
Third Party: Cloudflare → Cloudflare Sites and Services → DNS Root Servers - Operational
Third Party: Cloudflare → Cloudflare Sites and Services → SSL Certificate Provisioning - Operational
Third Party: Cloudflare → Cloudflare Sites and Services → Workers - Operational
Third Party: Fly.io → AWS s3-sa-east-1 - Operational
Third Party: Fly.io → Application Hosting → GRU - São Paulo, Brazil - Operational
Third Party: Github → Actions - Operational
Third Party: Github → API Requests - Operational
Third Party: Github → Git Operations - Operational
Third Party: Github → Pull Requests - Operational
Third Party: Github → Webhooks - Operational
Third Party: Shopify → Shopify API & Mobile - Operational
Third Party: Shopify → Shopify Checkout - Operational
Third Party: Shopify → Shopify Point of Sale - Operational
Third Party: Supabase → Supabase Cloud → AWS ec2-sa-east-1 - Operational
Third Party: Discord → Voice → Brazil - Operational
Third Party: Fly.io → Edge Proxy → Routing - Operational
Third Party: Supabase → Auth - Operational
Third Party: Supabase → Storage - Operational
We deployed a solution. Environments may need a reset to go back to work.
Sites that received a browserslist update (dependency) are unable to run, due to lack of permissions to access filesystem.
We are deploying some solutions to mitigate this issue.
Rollback and lock to browserslist 4.24.3 may fix this problem.
We reversed our node policies, and environments are now going back as expected.This incident has been resolved.
Some pods were not able to claim a PV due to some policies on our instance role.
We are currently investigating this incident.
Previews / admin environments are not able to run.
The thirdparty provider is aware and acting
We are currently observing an elevated number of 5xx errors on a subset of our sites. Preliminary investigation suggests these errors are resulting from issues within a third-party infrastructure component that some of our services depend on.
We moved our sites to a new DNS, and already recovered our decocdn.com.
Our decocdn.com domain is not propagating our address.
We are migrating sites from that domain and in contact with our dns registrar to also fix that issue for our current domain.
We disable one layer of cache, and are monitoring sites going back.
One layer of our tiered cache strategy had a bottleneck on connections/usage.
Nov 2024 to Jan 2025
Next