app.qfield.cloud on QField Ecosystem Status

[Resolved] Degraded service

Fri, 19 Jun 2026 12:00:00 +0000

Investigating

[2026-06-22 12:00] We are experiencing problems with email delivery. We are working on a resolution with our email provider.
[2026-06-22 21:00] We have switched to a new email provider, emails are now sent through Lettermint. The sub-processor list of our DPA has been updated accordingly. We had to do this as an express measure in order to keep things running smoothly, we therefore had to skip the standard 10 days announcement period for new sub-processors. To make sure you keep full control over your personal data, we have put an information on pages where notification emails are triggered. No action needed on your end.

[Resolved] Degraded service

Tue, 09 Jun 2026 09:40:00 +0000

Resolved

We identified a spike and punctual high load, which is now over. app.qfield.cloud is back to normal.

Investigating

We are experiencing service and stability issues on app.qfield.cloud. We are investigating the cause of the issue and will provide further updates as soon as possible.

[Resolved] Degraded service

Tue, 05 May 2026 14:20:00 +0000

Resolved

We identified the reason for the high memory usage and applied a fix.
app.qfield.cloud is running again without issues.

Investigating

Update 2026-05-05: We are experiencing a service disruption on app.qfield.cloud. We are investigating the cause of the issue and will provide further updates as soon as possible.
Update 2026-05-05: We are seeing unsually high memory usage and we are still investigating the root cause of it.

[Resolved] Degraded service

Mon, 12 Jan 2026 12:00:00 +0000

Resolved

Our upstream infrastructure provider has resolved the infrastructure issue affecting the single rack. All services are now operating normally.

Ongoing

Our infrastructure provider has posted an update that the issue is linked to a single rack, and they are still working on mitigations.
Our upstream infrastructure provider is experiencing an issue that is causing increased internet network latencies and packet loss. They are working on resolving the problem.
We are experiencing a service degradation on app.qfield.cloud. We are investigating the cause of the issue and will provide further updates as soon as possible.

[Resolved] Degraded service

Tue, 11 Nov 2025 13:35:00 +0000

Resolved

Our upstream provider had a network issue that prevented QFieldCloud instances from reaching the backend databases. A faulty switch was identified and replaced, and network connectivity has been restored.
All QFieldCloud Dedicated instances are reachable again.

Investigating

We are experiencing a service degradation on app.qfield.cloud and some dedicated QFieldCloud instances. We can see interrupted network connectivity between QFieldCloud and the backend database. We are investigating and in contact with our upstream provider.

[Resolved] Degraded service

Wed, 22 Oct 2025 08:00:00 +0000

Resolved

On October 21 and 22, we experienced intermittent service disruptions caused by high system load. We upgraded the server resources and adjusted load distribution in order to restore regular service, which seems to have resolved the issue.

Investigating

We are experiencing a service degradation, currently we are investigating the root cause.

[Resolved] Degraded service

Tue, 19 Aug 2025 15:00:00 +0000

Resolved

We believe all users experiencing issues have been able to connect and run their jobs at this time.

Monitoring

We have rolled out a patch that should have solved the suspected issue. The systems are now under close monitoring. Jobs have been restarted and will be processed in the next few hours. (17:25 UTC — Aug 19)

Investigating

We have isolated the core issue and are preparing a patch to be rolled out soon. (16:25 UTC — Aug 19)

Investigating

We are experiencing a service level problem on app.qfield.cloud and have stopped the workers while we are investigating. Jobs are being accumulated and will be processed once the issue is resolved. (15:00 UTC — Aug 19)

[Resolved] Degraded service

Mon, 04 Aug 2025 18:00:00 +0000

We are experiencing stability problems on the system at the moment and are looking into it.

Update 2025-08-04: We were able to recover services and are observing the situation.

Update 2025-08-09: The instabilities surfaced again and we could identify the source. It is related to projects with many files which cause a lot of internal requests and memory usage and therefore take too long to respond. A patch is deployed and being monitored.

Update 2025-08-11: The initial patch did cause unintended side effects and didn’t resolve the problem and different attempts to mitigate the issue resulted in service instabilities and problems with accessing the storage backend which prevented some users from uploading files. We have now identified the main source of troubles and are deploying an improved and tested hotfix.

Update 2025-08-12: All systems are running stable and memory usage is on normal levels. In a follow up of this incident, we have improved our monitoring systems to detect such problems earlier.

Update 2025-08-15: Summary of the issue

QFieldCloud experienced a series of performance and availability degradations in the last week, starting from August 4th until late August 11th.

While this immediately caught our attention, it took us until August 8th to discover the root cause.

The root cause was excessive database queries for projects that have more than a few hundred files, which caused overall service degradation. While the affected APIs were for uploading and downloading files, the heavy workload on the database caused sporadic problems with the service as a whole.

We worked on finding solutions immediately; however, due to the complexity of the issue, the solutions were not stable enough, which further degraded the service in the early hours of August 11th. We reverted to the previous version of QFieldCloud in the afternoon on the 11th.

Later on August 11th, we deployed a new version of QFieldCloud that fixed the scalability issue for bigger projects, resulting in much less pressure on our servers.

We are closely monitoring our systems to confirm everything is working as intended. From the lessons learned, we have already improved our monitoring and prioritized measures to ensure the overall availability of the service.

Apologies for the inconvenience.