Incidents reported on status page for METADAX https://status.metadax.com.br/ https://d1lppblt9t2x15.cloudfront.net/logos/49d8cdf5df0d1a3faa79bb8ee5ce7326.png https://status.metadax.com.br/ en https://status.metadax.com.br/ Fri, 19 Dec 2025 02:53:35 +0000 https://status.metadax.com.br/#12d9d6fec4dbe0ce0d3b61fd38aba1f4ef1a9e9d74378b625598398050c09b9f metadax.com.br recovered https://status.metadax.com.br/ Wed, 17 Dec 2025 02:22:52 +0000 https://status.metadax.com.br/#12d9d6fec4dbe0ce0d3b61fd38aba1f4ef1a9e9d74378b625598398050c09b9f metadax.com.br went down https://status.metadax.com.br/ Tue, 18 Nov 2025 04:29:21 +0000 https://status.metadax.com.br/#1ffad0ce60ffd08e9d12417bf8a0e70d7f4df094a2c697650bacafeb8ae9e685 metadax.com.br recovered https://status.metadax.com.br/ Tue, 18 Nov 2025 04:05:21 +0000 https://status.metadax.com.br/#1ffad0ce60ffd08e9d12417bf8a0e70d7f4df094a2c697650bacafeb8ae9e685 metadax.com.br went down https://status.metadax.com.br/ Mon, 17 Nov 2025 02:16:17 +0000 https://status.metadax.com.br/#3d5f0a7b5797acfbf46cf3adf849432bb68af47dbacdaeb3475c9033abb57bff metadax.com.br recovered https://status.metadax.com.br/ Mon, 17 Nov 2025 02:13:31 +0000 https://status.metadax.com.br/#3d5f0a7b5797acfbf46cf3adf849432bb68af47dbacdaeb3475c9033abb57bff metadax.com.br went down https://status.metadax.com.br/ Thu, 13 Nov 2025 18:57:48 +0000 https://status.metadax.com.br/#e7937a71166f0196ad4dc8ac4fed3cf05c3c4ca9d08cbd8edcae1f3822ca4e8c metadax.com.br recovered https://status.metadax.com.br/ Thu, 13 Nov 2025 18:15:51 +0000 https://status.metadax.com.br/#e7937a71166f0196ad4dc8ac4fed3cf05c3c4ca9d08cbd8edcae1f3822ca4e8c metadax.com.br went down https://status.metadax.com.br/ Thu, 13 Nov 2025 01:53:09 +0000 https://status.metadax.com.br/#67df8eafe19ed1a7cc5a6ef625d3dee8660f728181efb4dd5af9dc57e2897ab2 metadax.com.br recovered https://status.metadax.com.br/ Thu, 13 Nov 2025 01:47:08 +0000 https://status.metadax.com.br/#67df8eafe19ed1a7cc5a6ef625d3dee8660f728181efb4dd5af9dc57e2897ab2 metadax.com.br went down https://status.metadax.com.br/ Sun, 26 Oct 2025 15:29:34 +0000 https://status.metadax.com.br/#ba2feff7c2de0c8677d0ad31bed26d12533bd247c635839583daf415e080843a metadax.com.br recovered https://status.metadax.com.br/ Sun, 26 Oct 2025 15:24:06 +0000 https://status.metadax.com.br/#ba2feff7c2de0c8677d0ad31bed26d12533bd247c635839583daf415e080843a metadax.com.br went down https://status.metadax.com.br/incident/770693 Sun, 26 Oct 2025 10:00:00 -0000 https://status.metadax.com.br/incident/770693#4c599b9a343f520e65a417142916e6120a03817e1f5ed659f5421ef1ed7bd5d7 TECHNICAL STATUS REPORT - METADAX REF: INFRASTRUCTURE MIGRATION (ON-PREMISE TO CLOUD) REPORT PERIOD: October 20, 2025 to November 18, 2025 SCENARIO SUMMARY We inform you that, between October 20, 2025 and December 14, 2025, MetaDax is executing the wave migration process of our on-premise servers. to the cloud. As of the date of this report, we have reached the milestone of 82% of the infrastructure successfully migrated. Our new architecture was designed to be geographically and computationally distributed among the main cloud providers, meeting strict requirements for user location, latency optimization, load balancing, redundancy, and security. IMPACT ANALYSIS (October 20th to November 18th) During the migration windows within this period, occasional instabilities were recorded on our status page. It is crucial to highlight the nature of these events: - SCOPE: The identified impacts exclusively affected the availability of auxiliary serverless services. - RISK: These services were classified as having very low impact and low or zero risk to the core operation. - CRITICAL SERVICES: The availability of essential services provided to our clients remained intact and did not suffer negative impacts, as the migration of these components follows an isolated plan. All reported interruptions in this phase have already been corrected. NEXT STEPS: MIGRATION OF CRITICAL ENVIRONMENTS We will soon begin the final migration of critical environments. To ensure business continuity and data security, the following preventive measures are in place: A) SECURITY AND ROLLBACK: The environments already have full backups, in addition to rollback policies and incident handling plans previously mapped. B) ACCESS AND REDUNDANCY: Access for clients, suppliers, and partners has already been configured via proxy. In case of instability, a fallback mechanism will be automatically activated. C) MAINTENANCE WINDOW: The migration of each environment will be performed during low-traffic hours, with adjusted load distribution. NOTE: During the final switchover, some non-critical information may be temporarily unavailable while the data is synchronized to the new infrastructure. END OF REPORT Infrastructure and DevOps Team METADAX