Is Monta down?

Between 11:56 and 12:14 CET, some Partner API requests failed with errors. Partner API is working normally again. Monta apologizes for the inconvenience.

Customers connecting to the Monta data warehouse are currently receiving 503 errors, and access to data warehouse data is unavailable. We are actively working on restoring access and will share another update as soon as we have more information.

The data warehouse connection issues are the result of an outage at our third-party provider, Snowflake, and are not a failure of Monta's own systems. Access to data warehouse data remains unavailable while Snowflake works to restore service. You can follow their progress at https://status.snowflake.com/incidents/bfh045zclk5k, and we will share another update as soon as service is restored.

Data warehouse connections have been fully restored as of 20:56 UTC on October 21, 2026, and the incident is resolved. The disruption originated with our third-party data warehouse provider, Snowflake, and was not an issue with Monta's own platform. You can read the provider's incident details at https://status.snowflake.com/incidents/bfh045zclk5k. We apologize for the inconvenience and thank you for your patience.

We are aware of the two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619, also known as “php2shell”) that the PHP project disclosed and patched today, 21 October 2026. Our engineering and security teams have investigated, and we have confirmed that the Monta platform is not exposed to these vulnerabilities. Protective measures are already in place, and as a further precaution we are applying the latest security updates. The hosting provider for our public website, monta.com, has also confirmed that its systems are fully patched. No action is needed from customers or partners, and all Monta services are working normally. We will update this page once the precautionary updates are complete. If you have questions, contact us at [email protected].

Our assessment is unchanged: the Monta platform is not exposed to CVE-2026-109618 or CVE-2026-109619. We have found no impact on Monta services or customer data, and no action is needed from customers or partners. We have applied additional protective measures and will keep applying security updates as part of our normal patching process, including any further fixes the PHP project releases. We are closing this notice. If you have questions, contact us at [email protected].

Since approximately 19:45 UTC, many charging sessions on Zaptec chargers (all models) are failing to start or stopping after a few minutes. This is mainly affecting customers in Denmark, Iceland and Sweden. Chargers from other brands are not affected. Our team is actively investigating and we will share another update as soon as we have more information.

We are continuing to investigate this issue.

We have identified the cause of the issue: confirmations that a charge has started are reaching our platform with a delay from some Zaptec chargers. As a result, sessions may fail to start or stop after a few minutes. Chargers from other brands are not affected. We are monitoring the situation closely. Workaround: starting a charge with an RFID tag or card is currently the most reliable option. Repeatedly retrying from the app is unlikely to help.

Charging on Zaptec chargers is recovering, and we are seeing sessions start more reliably again. We are continuing to monitor closely to confirm that the recovery holds. Chargers from other brands were not affected. If a session still fails to start, starting with an RFID tag or card remains the most reliable option, and trying again in a few minutes may now succeed.

The issue affecting Zaptec chargers, where charges failed to start or stopped after a few minutes, has been resolved. Charging is back to normal.

The issue causing degraded performance for Wallet and Partner API requests has been resolved. All services are operating normally and have been stable since 12:36. We apologize for the inconvenience this caused.