hosting-kubernets - Operational
hosting-kubernets
Previous page
Next page
hosting-denodeploy - Operational
hosting-denodeploy
admin - Operational
admin
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: Supabase → Auth - Operational
Third Party: Supabase → Storage - Operational
Some sites reported slowness from 9:20 to 9:39 (timeout requests increased from 600 to 1.6k) requests (0.8% to 2.3%).
We rolled back some configuration.
A change on our network configuration dropped packages from some origins.
Deno deploy isolates were killed due to memory starvation.
A new memory profile was applied, thus resolving this issue.
Deno deploy added capacity to mitigate reported issues.
Still investigating root cause.
We are back to normal status rate.
No errors logged since 14:45:11 (UTC).
We are closing this issue.
We are pushing a fix and monitoring it.
An update on our aws dependencies broke the submit asset feature. We are investigating solutions.
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.
Jan 2025 to Mar 2025
Next