We saw a higher amount of geocoding taking > 1000ms today in 3 one hour timeslots. Less than 3% of geocoding affected. We identified the affected server and took it offline. Inconclusive what exactly caused it, we suspect network hardware of the virtual machine and will replace the server.