LocationIQ Status Page https://status.locationiq.org/ 2026-04-11T15:29:02+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/100/ We recently identified and resolved an issue caused by intermittent packet loss that resulted in sporadic service disruptions for some users. All systems are now operating normally. We apologize for any inconvenience caused.

]]> 2026-04-02T20:00:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/102/ We are currently investigating reports of intermittent service disruptions affecting some users. We'll share an update as soon as we have more information.

]]> 2026-04-02T16:50:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/98/ This incident has been resolved and all services are now operating normally.

]]> 2025-11-18T19:28:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/97/ We are currently experiencing a network-wide issue with one of our upstream service providers. This is resulting in intermittent 500 errors, increased latency, and occasional request failures. Since our traffic is routed through this provider, some users may notice slower load times or temporary disruptions.

We are actively monitoring the situation and will provide updates as more information becomes available.

]]> 2025-11-18T11:48:00+00:00 LocationIQ Status Page <![CDATA[Network Issue]]> http://status.locationiq.org/incident/95/ The network instability affecting our US endpoints has been resolved. All services are operating normally.

]]> 2025-10-27T11:32:00+00:00 LocationIQ Status Page <![CDATA[Network Issue]]> http://status.locationiq.org/incident/94/ We're observing minor network instability affecting our US endpoints due to upstream issues at one of our data center providers. The provider is mitigating a DDoS attack, and impact to our services remains minimal. We're monitoring closely and will update if there are any significant changes.

]]> 2025-10-26T19:06:00+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/93/ Database Maintenance has been completed. All systems are fully operational now.

]]> 2024-11-28T08:50:00+00:00 LocationIQ Status Page <![CDATA[Database maintenance]]> http://status.locationiq.org/incident/92/ We are presently running maintenance upgrades and migrations on our primary cluster. During this time all APIs will continue to function. User Dashboard reports will be late and some features such as editing or deleting access tokens will be unavailable. We expect to complete these in the next 3 hours and will post updates if there are any delays.

]]> 2024-11-28T05:45:00+00:00 LocationIQ Status Page <![CDATA[Unplanned database maintenance]]> http://status.locationiq.org/incident/91/ Database Maintenance has been completed. All systems are fully operational now.

]]> 2024-10-18T13:59:00+00:00 LocationIQ Status Page <![CDATA[Unplanned database maintenance]]> http://status.locationiq.org/incident/90/ We are presently running maintenance upgrades and migrations on our primary cluster. During this time all APIs will continue to function. User Dashboard reports will be late and some features such as editing or deleting access tokens will be unavailable. We expect to complete these in the next 3 hours and will post updates if there are any delays.

]]> 2024-10-18T08:57:00+00:00 LocationIQ Status Page <![CDATA[Email Provider Issues]]> http://status.locationiq.org/incident/89/ The issue with our email provider causing delays in magic link delivery and other emails has been resolved. All services are now operating normally, and email delivery times should return to expected levels.

]]> 2024-09-16T06:55:00+00:00 LocationIQ Status Page <![CDATA[Email Provider Issues]]> http://status.locationiq.org/incident/88/ We have identified an issue with our email provider that is causing delays in the delivery of magic links and other emails.

]]> 2024-09-16T00:15:00+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/86/ Database Maintenance has been completed. All systems are fully operational now.

]]> 2024-06-22T10:50:00+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/65/ We are presently running maintenance upgrades and migrations on our primary cluster. During this time all APIs will continue to function. User Dashboard reports will be late and some features such as editing or deleting access tokens will be unavailable. We expect to complete these in the next 2 hours and will post updates if there are any delays.

]]> 2024-06-22T06:30:00+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/70/ We are presently running maintenance upgrades and migrations on our primary cluster. During this time all APIs will continue to function. User Dashboard reports will be late and some features such as editing or deleting access tokens will be unavailable. We expect to complete these in the next 2 hours and will post updates if there are any delays.

]]> 2023-05-20T03:30:00+00:00 LocationIQ Status Page <![CDATA[Network Issues - Resolved]]> http://status.locationiq.org/incident/85/ Full performance has been restored on this endpoint.

]]> 2022-09-10T16:28:00+00:00 LocationIQ Status Page <![CDATA[Network Issue - Rerouted]]> http://status.locationiq.org/incident/84/ We are no longer seeing network issues on this route. We have rerouted traffic to Europe - DC1 as a precaution while we keep this under observation.

]]> 2022-09-10T10:45:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/83/ We are investigating issues with network performance in this datacenter. This may cause higher latencies or request timeouts.

]]> 2022-09-10T09:45:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/81/ This incident has been resolved.

]]> 2022-06-21T08:06:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/80/ We are currently experiencing downtime due to a worldwide Cloudflare outage. We've fixed this by bypassing Cloudflare for now. We will switch back as soon as the issue has been sorted.

]]> 2022-06-21T06:30:00+00:00 LocationIQ Status Page <![CDATA[Network Maintenance]]> http://status.locationiq.org/incident/79/ Network maintenance is complete in our EU1 datacenter. Routes have been restored to this DC and latencies should be normal.

]]> 2021-10-12T04:30:00+00:00 LocationIQ Status Page <![CDATA[Network Maintenance]]> http://status.locationiq.org/incident/78/ Our EU1 Datacenter will be undergoing routine network maintenance on Monday, October 11, 21:00 UTC. This is expected to last 7 hours. As a precautionary measure, we will be routing all traffic to our US East DC1. While there will be no disruptions in service, there may be higher than normal latencies on this endpoint while this routing is in place.

]]> 2021-10-11T13:10:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/77/ Full performance has been restored on this endpoint.

]]> 2021-10-01T05:00:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/76/ We are no longer seeing network issues on this route. We have rerouted traffic to US East DC1 as a precaution while we keep this under observation. During this time, users may experience higher latencies due to the rerouting.

]]> 2021-09-30T20:25:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/75/ We are investigating issues with network performance in this datacenter. This may cause higher latencies or request timeouts.

]]> 2021-09-30T20:00:00+00:00 LocationIQ Status Page <![CDATA[Delay in Dashboard Reporting]]> http://status.locationiq.org/incident/74/ Reports backlog has processed successfully. Dashboard Reports are no longer delayed.

]]> 2021-09-02T03:30:00+00:00 LocationIQ Status Page <![CDATA[Delay in Dashboard Reporting]]> http://status.locationiq.org/incident/73/ Reports backlog is still processing with a delay of ~45 minutes. We expect this to be caught up shortly.

]]> 2021-09-01T13:30:00+00:00 LocationIQ Status Page <![CDATA[Delay in Dashboard Reporting]]> http://status.locationiq.org/incident/72/ We have identified delays in dashboard reports delivery, and are actively investigating. We’re currently working through a backlog and will be up to date once processing is complete.

]]> 2021-08-31T17:30:00+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/71/ Database Maintenance has been completed. All systems are fully operational now.

]]> 2021-08-29T10:00:00+00:00 LocationIQ Status Page <![CDATA[Network Maintenance]]> http://status.locationiq.org/incident/69/ The scheduled maintenance has been completed. Full performance has been restored on this endpoint.

]]> 2021-03-03T04:00:00+00:00 LocationIQ Status Page <![CDATA[Network Maintenance]]> http://status.locationiq.org/incident/68/ Scheduled maintenance is currently in progress. We have redirected affected routes to our US Datacenters. During this time, users may experience higher latencies due to the rerouting.

]]> 2021-03-03T03:00:00+00:00 LocationIQ Status Page <![CDATA[Network Maintenance]]> http://status.locationiq.org/incident/67/ Our EU Data Center provider will perform routine network maintenance on Wednesday, March 3, 2:30 AM UTC which is expected to run for 1 hour. As a precaution and to avoid any disruption in service, we will redirect affected routes to our US Datacenters. During this time, users may experience higher latencies due to the rerouting.

]]> 2021-03-02T14:31:03+00:00 LocationIQ Status Page <![CDATA[Database Maintenance]]> http://status.locationiq.org/incident/66/ Database Maintenance has been completed. All systems are fully operational now.

]]> 2020-08-29T12:15:00+00:00 LocationIQ Status Page <![CDATA[Network Issues - Resolved]]> http://status.locationiq.org/incident/64/ Full performance has been restored on this endpoint.

]]> 2020-02-04T07:00:00+00:00 LocationIQ Status Page <![CDATA[Network Issue]]> http://status.locationiq.org/incident/63/ We are no longer seeing network issues on this route. We have rerouted traffic to US East DC1 as a precaution while we keep this under observation.

]]> 2020-02-04T02:40:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/62/ We are investigating issues with network performance in this datacenter. This may cause higher latencies or request timeouts.

]]> 2020-02-03T20:58:00+00:00 LocationIQ Status Page <![CDATA[Network Issues - Resolved]]> http://status.locationiq.org/incident/61/ Full performance has been restored on this endpoint.

]]> 2020-02-02T00:00:00+00:00 LocationIQ Status Page <![CDATA[Network Issues]]> http://status.locationiq.org/incident/59/ We are investigating issues with network performance in this datacenter. This may cause higher latencies or request timeouts. All requests have been routed to US East - DC1.

]]> 2020-02-01T01:50:00+00:00 LocationIQ Status Page <![CDATA[Routing API Status]]> http://status.locationiq.org/incident/57/ A load balancer server failed causing a portion of requests to fail or timeout. Requests were automatically routed to alternate datacenter. We are looking at multi-region load balancers to avoid this issue in the future.

]]> 2019-11-16T00:18:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/56/ A load balancer server failed causing a portion of requests to fail or timeout. Requests were automatically routed to alternate datacenter. We are looking at multi-region load balancers to avoid this issue in the future.

]]> 2019-11-16T00:18:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/55/ We are investigating packet-loss issues on this endpoint.

]]> 2019-11-16T00:15:00+00:00 LocationIQ Status Page <![CDATA[Routing API Status]]> http://status.locationiq.org/incident/58/ We are investigating packet-loss issues on this endpoint.

]]> 2019-11-16T00:15:00+00:00 LocationIQ Status Page <![CDATA[Network issues]]> http://status.locationiq.org/incident/54/ Full performance has been restored on this endpoint.

]]> 2019-08-28T15:35:00+00:00 LocationIQ Status Page <![CDATA[Network issues]]> http://status.locationiq.org/incident/53/ We are investigating packet-loss issues on this endpoint.

]]> 2019-08-28T15:25:00+00:00 LocationIQ Status Page <![CDATA[Network issues]]> http://status.locationiq.org/incident/52/ The performance issues appear to have been resolved and connectivity across the Internet should be returning to normal, including LocationIQ services. We're continuing to monitor the situation.

]]> 2019-07-02T14:15:00+00:00 LocationIQ Status Page <![CDATA[Network issues]]> http://status.locationiq.org/incident/51/ We are aware that performance issues from a major provider are causing connectivity problems across the Internet. LocationIQ users may experience issues when attempting to access resources on our platform, including our APIs, Dashboard and Map Tiles. We apologize for the inconvenience and will post an update as soon as more information is available.

]]> 2019-07-02T13:45:00+00:00 LocationIQ Status Page <![CDATA[Upstream issues]]> http://status.locationiq.org/incident/50/ We have received confirmation from our Earth Imagery partner that this issue is resolved. If you are still receiving 404s for valid tiles, please reach out to support and we'll help you.

]]> 2019-07-01T11:28:00+00:00 LocationIQ Status Page <![CDATA[Upstream issues]]> http://status.locationiq.org/incident/49/ Our Earth Imagery partner's APIs are returning sporadic 404s for valid tiles. We are working with them on a fix. In the meantime, we will return over-zoomed tiles if a specific tile isn't found. We apologise for the inconvenience.

]]> 2019-07-01T06:38:00+00:00 LocationIQ Status Page <![CDATA[Delays in Reports]]> http://status.locationiq.org/incident/48/ Due to a high volume of incoming requests, our geographically distributed reporting infrastructure is lagging behind. Our team is currently working on speeding this up. We expect this to be resolved in the next 2 hours.

]]> 2019-06-11T11:25:00+00:00 LocationIQ Status Page <![CDATA[Migration]]> http://status.locationiq.org/incident/47/ Migration is complete. Reports are now up to date.

]]> 2019-06-09T13:49:00+00:00 LocationIQ Status Page <![CDATA[Migration]]> http://status.locationiq.org/incident/46/ We are migrating our reporting infrastructure to a different Data Center. Only historic reports are accessible at this time. We expect to complete the migration in the next 3 hours.

]]> 2019-06-09T07:03:00+00:00 LocationIQ Status Page <![CDATA[Delays in reporting]]> http://status.locationiq.org/incident/45/ We are migrating our reporting infrastructure to support reporting separately by Access Tokens. The dashboard currently only shows reports made by the Private Token. Our team is currently completing the migration over to display reports from all access tokens. We expect this to be resolved in the next 2 hours.

]]> 2019-06-03T04:39:00+00:00 LocationIQ Status Page <![CDATA[Load Balancer failure]]> http://status.locationiq.org/incident/44/ Update: all traffic is operating normally. This specific LB was down for 6 minutes but all requests to this LB were re-routed within a minute.

One of the LBs in this DC failed and dropped requests. DNS failover kicked in to route all requests to another DC. A small set of customers' requests failed during this time.

]]> 2019-05-31T00:53:00+00:00 LocationIQ Status Page <![CDATA[Sign-ups failing for new users]]> http://status.locationiq.org/incident/43/ Sign-ups failed due to a failed SSL certificate update issue. Update has been rolled back and sign-ups are working again.

]]> 2019-05-17T20:20:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/42/ Full performance has been restored on this endpoint

]]> 2019-05-09T11:54:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/41/ We are experiencing network issues on this endpoint.

]]> 2019-05-09T11:22:00+00:00 LocationIQ Status Page <![CDATA[Network issues]]> http://status.locationiq.org/incident/40/ Due to routing issues between our DNS & DDOS protection provider, Cloudflare, and our Datacenters, some customers may experience network timeouts while querying the US East region.

]]> 2019-03-04T15:55:00+00:00 LocationIQ Status Page <![CDATA[Internal load balancer issues]]> http://status.locationiq.org/incident/38/ One of our internal load balancers failed and the DNS failover configured on this load balancer didn't trigger.

Update 1: We've fixed things up manually for now and are investigating the reason automatic failover didn't work. A small number of users experienced partial outage for 9 minutes, 21 seconds. Sorry about this, we are taking steps to prevent such incidents in the future.

]]> 2018-07-13T04:35:00+00:00 LocationIQ Status Page <![CDATA[Cascading effect of load balancer issue on EU DC1]]> http://status.locationiq.org/incident/39/ This endpoint was under routine maintenance and routed to the US East DC when the load-balancer failure occurred in that DC.

Update 1: We have interrupted maintenance and routed this endpoint back to it's original DC. A small number of users experienced partial outage for 9 minutes, 21 seconds. Sorry about this, we are taking steps to prevent such incidents in the future.

]]> 2018-07-13T04:35:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/37/ Full performance has been restored on this endpoint.

]]> 2018-06-28T22:10:00+00:00 LocationIQ Status Page <![CDATA[Intermittent network issues]]> http://status.locationiq.org/incident/35/ A Geocoding cluster went down in this DC for 3 minutes. Load balancers failed-over those servers to another cluster. Estimated packet-loss to clients on this DC to be around 5 seconds.

]]> 2018-06-28T22:04:00+00:00 LocationIQ Status Page <![CDATA[API Status - Europe endpoint]]> http://status.locationiq.org/incident/34/ Due to a failed deployment, high error rates were observed for some customers on our Europe endpoint causing a partial outage that lasted 3 minutes. Our team rolled back the deployment immediately. We're investigating why this deployment failed and will put in place processes to avoid this in the future.

]]> 2018-06-12T12:33:00+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/33/ Full performance has been restored on this endpoint.

]]> 2018-06-11T14:24:01+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/32/ Full performance has been restored on this endpoint.

]]> 2018-05-08T00:52:28+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/31/ Full performance has been restored on this endpoint.

]]> 2018-05-08T00:51:08+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/30/ Full performance has been restored on this endpoint.

]]> 2018-05-08T00:39:29+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/29/ Full performance has been restored on this endpoint.

]]> 2018-05-08T00:26:24+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/28/ Full performance has been restored on this endpoint.

]]> 2018-04-10T17:20:10+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/27/ We are experiencing higher than normal latencies on this endpoint.

]]> 2018-04-08T16:01:30+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/26/ Full performance has been restored on this endpoint.

]]> 2018-03-26T20:05:55+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/25/ Full performance has been restored on this endpoint.

]]> 2018-03-26T15:02:36+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/24/ Full performance has been restored on this endpoint.

]]> 2018-03-26T15:02:36+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/23/ Full performance has been restored on this endpoint.

]]> 2018-03-26T13:55:24+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/22/ Full performance has been restored on this endpoint.

]]> 2018-03-26T13:55:23+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/21/ Full performance has been restored on this endpoint.

]]> 2018-03-25T11:57:08+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/20/ Full performance has been restored on this endpoint.

]]> 2018-03-21T08:43:19+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/19/ Full performance has been restored on this endpoint.

]]> 2018-03-21T08:35:17+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/18/ Full performance has been restored on this endpoint.

]]> 2018-03-05T17:05:31+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/17/ Full performance has been restored on this endpoint.

]]> 2018-03-03T13:59:10+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/16/ We are investigating packet-loss issues on this endpoint.

]]> 2018-03-03T13:54:40+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/15/ Full performance has been restored on this endpoint.

]]> 2018-03-02T16:24:13+00:00 LocationIQ Status Page <![CDATA[API Status]]> http://status.locationiq.org/incident/14/ We are experiencing higher than normal latencies on this endpoint.

]]> 2018-03-02T16:23:43+00:00