Resolved -
This incident is resolved. The Anvil web application, API, and telemetry ingestion have been operating normally since the fix was applied, and we have confirmed all services are healthy.
The disruption was caused by an internal component reaching a capacity limit, which prevented dependent services from accepting traffic. We have increased that capacity and are making a further change to prevent the condition from recurring.
Telemetry queued by your drivers during the disruption has been processed. We apologise for the interruption.
Jul 20, 20:47 AEST
Monitoring -
All services have been restored and are operating normally. The Anvil web application, API, and telemetry ingestion are available again.
We are continuing to monitor closely to confirm stability. Telemetry queued by your drivers during the disruption should now be processed.
We will follow up with a resolution notice once we are satisfied the fix is holding.
Jul 20, 20:10 AEST
Identified -
We have identified the cause of the disruption affecting the Anvil web application, the API, and telemetry ingestion. A shared internal component reached a capacity limit, which caused dependent services to stop accepting traffic.
We have applied a fix and are currently monitoring recovery. Services should begin returning to normal shortly.
Telemetry sent from your drivers during this period may be delayed rather than lost, and we expect queued data to be processed once services are fully restored. Our documentation site and driverforge.com remain unaffected.
We will post a further update once we have confirmed all services are healthy.
Jul 20, 19:55 AEST
Investigating -
We are currently investigating a service disruption affecting the Anvil web application, the API, and telemetry ingestion.
During this period you may be unable to sign in or load data in the Anvil app, API requests may fail, and telemetry sent from your drivers may be delayed.
Our documentation site and driverforge.com are not affected.
We have identified a likely cause and are actively working to restore service. We will provide a further update within 30 minutes, or sooner if the situation changes.
Jul 20, 19:45 AEST