deco - Notice history

All systems operational

hosting-kubernets - Operational

100% - uptime
Apr 2024 · 100.0%May · 99.98%Jun · 100.0%

Previous page

Next page

Apr 2024
May 2024
Jun 2024

hosting-denodeploy - Operational

admin - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2024
May 2024
Jun 2024

VTEX - Operational

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

Notice history

Jun 2024

We have observed an increase in timeouts within our Kubernetes infrastructure.
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    Our CoreDNS service became unresponsive due to a node malfunction.

  • Investigating
    Investigating
    We are currently investigating this incident.
Status Report: Commits Not Deploying
  • Resolved
    Resolved

    Our infrastructure reports that builds are running smoothly.

  • Update
    Update

    We are continuing to work on a fix for this incident.

    A more definitive solution will be postponed until tomorrow morning.

  • Identified
    Identified

    We are actively investigating the issue. While we have made improvements to site stability, we are still working on fixing some broken builds and refining the build process.

  • Investigating
    Investigating

    Users have reported that builds are taking an unusually long time or not completing on GitHub Actions.

Partial outage (timeout)
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
Timeouts occurring on our sites running on Deno Deploy.
  • Monitoring
    Monitoring

    Timeout issues were resolved.

  • Resolved
    Resolved

    No further incidents were observed on our infrastructure. During the incident, we experienced a peak of 10% of requests resulting in high latency responses.

  • Identified
    Identified

    After thorough investigation, we confirmed the issues were related to Deno Deploy. The issue was escalated to their infrastructure team.

  • Investigating
    Investigating

    Notification received from the health check system about timeouts on our sites.

May 2024

Admin site outage
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    A redeployment of the previous admin version was done, and the system is now operational.

  • Identified
    Identified

    The deployment of a new admin version with issues.

  • Investigating
    Investigating
    We are currently investigating this incident.

Apr 2024

Admin site unstable (1016 origin DNS error)
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    Following an infrastructure upgrade to our Kubernetes (k8) system, the ELB DNS has been modified. Consequently, we've observed occurrences of error 1016 (CF DNS origin error). We are actively addressing this issue and appreciate your patience as we resolve it.

  • Investigating
    Investigating
    We are currently investigating this incident.
GitHub Account Flagged
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We are pleased to inform you that the issue with our GitHub organization being flagged has been fully resolved.

    Visibility and access to our repositories have been restored.

    We sincerely appreciate your patience and understanding while we worked to resolve this matter.

    We are monitoring now.

  • Investigating
    Investigating

    Dear deco.cx Users,

    We regret to inform you that our GitHub organization has been flagged, resulting in a temporary loss of visibility and access to our repositories. This issue affects our ability to provide services and support through GitHub.

    We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time.

    Sincerely,
    The deco.cx Team

Apr 2024 to Jun 2024

Next