OpenCage incident

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

Minor Resolved View vendor source →
Started
Feb 25, 2026, 09:04 PM UTC
Resolved
Feb 25, 2026, 09:04 PM UTC
Duration
—
Detected by Pingoru
Feb 25, 2026, 09:04 PM UTC

Update timeline

  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.

Looking to track OpenCage downtime and outages?

Pingoru polls OpenCage's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when OpenCage reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track OpenCage alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring OpenCage for free

5 free monitors · No credit card required