Mockoon Cloud status

Having trouble? Email us at [email protected]

Loading...

Average uptime (last 90 days)

Incidents History

All services - Schedule downtime, v9.3.0 release

2025-07-01 08:10 GMT+00:00 - 2025-07-01 09:15 GMT+00:00

All services will be restarted to apply the v9.3.0 release. The downtime is expected to last less than 5 minutes for each service. We apologize for the inconvenience.

Google Cloud outage - Impact on Mockoon Cloud

2025-06-12 18:10 GMT+00:00 - 2025-06-12 21:35 GMT+00:00

Google Cloud is currently experiencing a global outage that is impacting all Mockoon Cloud services. We are monitoring the situation and will provide updates as soon as we have more information.
Google Cloud status page: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
Update (21:00 UTC): The situation is progressively improving and we are seeing services being restored. However, some issues may still occur, especially with the authentication service.
Update (21:35 UTC): The situation is now stable and all services are operational. We will continue to monitor the situation closely. We apologize for the inconvenience.

Cloud deployments - Scheduled downtime, maintainance and fix

2025-05-29 06:20 GMT+00:00 - 2025-05-29 06:35 GMT+00:00

All cloud deployments servers and customer instances will be restarted to apply a maintenance release, and upgrade the hardware.

All cloud services - Scheduled downtime, maintainance

2025-05-17 08:00 GMT+00:00 - 2025-05-17 08:35 GMT+00:00

All cloud deployments servers and customer instances will be restarted to apply a maintenance release, and upgrade the hardware. The downtime is expected to last less than an hour. We apologize for the inconvenience.

Cloud web app - Possible disruption

2025-04-23 09:30 GMT+00:00 - 2025-04-23 13:00 GMT+00:00

We are currently transitioning from hosting the web app on https://mockoon.app to https://app.mockoon.com. Some users may experience issues accessing the web app during this transition. No action should be required from your side but if you experience issues, please clear your browser cache and cookies (for the mockoon.com domain).

All services - Schedule downtime, v9.2.0 release

2025-03-12 13:05 GMT+00:00 - 2025-03-12 13:20 GMT+00:00

All services will be restarted to apply the v9.2.0 release. The downtime is expected to last less than 15 minutes. We apologize for the inconvenience.

All services - Schedule downtime, maintenance

2025-01-11 15:30 GMT+00:00 - 2025-01-11 15:35 GMT+00:00

All services will be restarted for maintenance. The downtime is expected to last less than 5 minutes. We apologize for the inconvenience.

All services - Schedule downtime, v9.1.0 release

2024-10-25 17:00 GMT+00:00 - 2024-10-25 17:15 GMT+00:00

All services will be restarted to apply the v9.1.0 release. The downtime is expected to last less than 15 minutes. We apologize for the inconvenience.

All services - Schedule downtime, v9.0.0 release

2024-10-25 15:08 GMT+00:00 - 2024-10-25 15:11 GMT+00:00

All services will be restarted to apply the v9.0.0 release. The downtime is expected to last less than 5 minutes. We apologize for the inconvenience.

Cloud deployments - Schedule downtime, security fix

2024-09-17 13:30 GMT+00:00 - 2024-09-17 13:35 GMT+00:00

Cloud deployments servers were restarted to apply a security fix. The downtime is expected to last 5 to 10 minutes. We apologize for the inconvenience.

Cloud deployments - Schedule downtime v8.4.0 release

2024-08-06 14:40 GMT+00:00 - 2024-08-06 15:48 GMT+00:00

Cloud deployments servers were restarted to apply the v8.4.0 release. The downtime is expected to last 5 to 10 minutes. We apologize for the inconvenience.

Cloud deployments - bugfix release

2024-07-24 14:49 GMT+00:00 - 2024-07-24 14:52 GMT+00:00

Cloud deployments servers were restarted to apply a fix affecting requests containing specific bodies. The issue has been resolved and deployments are back to normal.

Main API - issue with user creation

2024-04-23 14:00 GMT+00:00 - 2024-04-23 21:00 GMT+00:00

An issue prevented new users from being created. The issue has been identified and a fix deployed. Existing users were not affected. We put in place better monitoring to prevent this issue from happening again.