Incidents reported on status page for METADAX https://status.metadax.com.br/ https://d1lppblt9t2x15.cloudfront.net/logos/dca2bd18cef49723df1799eff0ac03f6.png https://status.metadax.com.br/ en https://status.metadax.com.br/ Thu, 05 Feb 2026 07:58:51 +0000 https://status.metadax.com.br/#f2129f66e0a12f0c92e63607dd208c6fa462302c5d2f05593c8be099e5199fa3 metadax.com.br recovered https://status.metadax.com.br/ Thu, 05 Feb 2026 07:50:58 +0000 https://status.metadax.com.br/#f2129f66e0a12f0c92e63607dd208c6fa462302c5d2f05593c8be099e5199fa3 metadax.com.br went down https://status.metadax.com.br/ Fri, 02 Jan 2026 18:53:11 +0000 https://status.metadax.com.br/#c63af26010f7268005da17cc4b16d693bcb96020a4d0395124eb91b7c6de67e6 cdn.metadax.com.br recovered https://status.metadax.com.br/ Fri, 02 Jan 2026 18:46:35 +0000 https://status.metadax.com.br/#c63af26010f7268005da17cc4b16d693bcb96020a4d0395124eb91b7c6de67e6 cdn.metadax.com.br went down https://status.metadax.com.br/ Fri, 02 Jan 2026 18:44:55 +0000 https://status.metadax.com.br/#3cf157dec1e586927c9d230dc843e2c7ce286353666b2355a3f9986b24a94c0f cdn.metadax.com.br recovered https://status.metadax.com.br/ Fri, 02 Jan 2026 18:06:30 +0000 https://status.metadax.com.br/#3cf157dec1e586927c9d230dc843e2c7ce286353666b2355a3f9986b24a94c0f cdn.metadax.com.br went down https://status.metadax.com.br/ Fri, 02 Jan 2026 18:01:36 +0000 https://status.metadax.com.br/#917576bfb9f7cf7607ce5869f3aca86b9e103191d1ed78dbdd2dae397c5953cc cdn.metadax.com.br recovered https://status.metadax.com.br/ Fri, 02 Jan 2026 17:56:30 +0000 https://status.metadax.com.br/#917576bfb9f7cf7607ce5869f3aca86b9e103191d1ed78dbdd2dae397c5953cc cdn.metadax.com.br went down https://status.metadax.com.br/ Fri, 02 Jan 2026 17:56:00 +0000 https://status.metadax.com.br/#42381acbadaf080528fde3868e628be3883f5860c10eb1bacac89d50cacf09cd cdn.metadax.com.br recovered https://status.metadax.com.br/ Fri, 02 Jan 2026 17:41:28 +0000 https://status.metadax.com.br/#42381acbadaf080528fde3868e628be3883f5860c10eb1bacac89d50cacf09cd cdn.metadax.com.br went down https://status.metadax.com.br/ Wed, 31 Dec 2025 20:41:29 +0000 https://status.metadax.com.br/#f9b6b7911c784306cb01418af989acc919bc5a61578c7ab6816cc85f7fb1bf64 cdn.metadax.com.br recovered https://status.metadax.com.br/ Wed, 31 Dec 2025 20:21:29 +0000 https://status.metadax.com.br/#f9b6b7911c784306cb01418af989acc919bc5a61578c7ab6816cc85f7fb1bf64 cdn.metadax.com.br went down 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/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