OpenCage Outage History

OpenCage is up right now

OpenCage had 5 outages in the last 2 years totaling 1h 22m of downtime — averaging 0.2 incidents per month.

There were 5 OpenCage outages since September 19, 2025 totaling 1h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.opencagedata.com

Major June 26, 2026

Email outage

Detected by Pingoru
Jun 26, 2026, 08:24 AM UTC
Resolved
Jun 26, 2026, 09:46 AM UTC
Duration
1h 22m
Timeline · 2 updates
  1. identified Jun 26, 2026, 08:24 AM UTC

    We are currently having issues with our email provider and are unable to receive emails.

  2. resolved Jun 26, 2026, 09:46 AM UTC

    This incident has been resolved, we are now able to receive emails again 🎉

Read the full incident report →

Minor March 27, 2026

API - Geosearch isn't accessible at the moment (automated)

Detected by Pingoru
Mar 27, 2026, 11:05 AM UTC
Resolved
Mar 27, 2026, 11:05 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 27, 2026, 11:05 AM UTC

    Type: Incident Duration: 3 minutes Affected Components: Geosearch Mar 27, 11:05:32 GMT+0 - Investigating - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 27, 11:08:03 GMT+0 - Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Minor February 25, 2026

API - Geocoding API - forward isn't accessible at the moment (automated)

Detected by Pingoru
Feb 25, 2026, 09:06 PM UTC
Resolved
Feb 25, 2026, 09:06 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 25, 2026, 09:06 PM UTC

    Type: Incident Duration: 6 minutes Affected Components: Geocoding API - forward Feb 25, 21:06:07 GMT+0 - Investigating - API - Geocoding API - forward cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 25, 21:12:00 GMT+0 - Resolved - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Minor February 25, 2026

API - Geocoding API - reverse isn't accessible at the moment (automated)

Detected by Pingoru
Feb 25, 2026, 09:04 PM UTC
Resolved
Feb 25, 2026, 09:04 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 25, 2026, 09:04 PM UTC

    Type: Incident Duration: 8 minutes Affected Components: Geocoding API - reverse Feb 25, 21:04:33 GMT+0 - Investigating - API - Geocoding API - reverse cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 25, 21:12:12 GMT+0 - Resolved - API - Geocoding API - reverse is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Minor September 19, 2025

Drop in incoming traffic, timeouts

Detected by Pingoru
Sep 19, 2025, 09:00 AM UTC
Resolved
Sep 19, 2025, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 19, 2025, 09:00 AM UTC

    Type: Incident Affected Components: , Geocoding API - forward, Geocoding API - reverse, Geosearch, API → Sep 19, 09:00:43 GMT+0 - Resolved - We saw a drop in incoming traffic of 70% for a 30min period between 8:15 to 8:45 UTC. Our hosting provider had a router outage. Traffic was rerouted to another data center but the automatic DNS switch-over didn't kick in to reroute all traffic. Sep 19, 09:41:43 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →