OpenCage GmbH - geosearch - customers received HTTP 401 errors – Incident details

All systems operational

Uptime is measured independently by performance monitoring company StatusCake.

Changes to our API are published in our CHANGE LOG on GitHub.

Follow us on Mastodon, and please visit our blog for our annual uptime reports.

geosearch - customers received HTTP 401 errors

Resolved
Operational
Started about 3 years agoLasted less than a minute

Affected

API

Operational from 3:05 PM to 3:05 PM

Geosearch

Operational from 3:05 PM to 3:05 PM

Updates
  • Resolved
    UTC
    Resolved

    Between 14:13 and 14:41 UTC our geosearch customer received HTTP 401 errors for some of their queries. The customer API key list wasn't correctly synced to all servers. There is a backup/fallback for geocoding if that happens but there wasn't for geosearch yet. Geocoding customers were not affected.