IDVerse incident

GeoLocation details not showing on transaction

Resolved after 3 hours 45 minutes, affecting 3rd Party Component Services, on February 18, 2025.

monitoring Feb 18, 2025, 04:02 AM UTC

We are continuing to monitor for any further issues.

Started
Feb 18, 2025, 01:32 AM UTC
Resolved
Feb 18, 2025, 05:17 AM UTC
Duration
3h 45m
Detected by Pingoru
Feb 18, 2025, 01:32 AM UTC

Affected components

3rd Party Component Services

Update timeline

  1. identified Feb 18, 2025, 01:32 AM UTC

    GeoLocation is no longer displaying on transactions relying on the IPStack location service, this impacts IDKit Enterprise customers using the service. This also impacts DFA results (causing it to flag) for customers below 4.8 and using Geo-Flagging: https://ocrlabs.atlassian.net/servicedesk/customer/portal/1/article/1870462988

  2. identified Feb 18, 2025, 03:05 AM UTC

    This is impacting a small number of customers. We have also confirmed in almost all situations is not impacting the ability to complete or send out transactions.

  3. monitoring Feb 18, 2025, 03:16 AM UTC

    IPStack service is up and running. We're monitoring to ensure this is true for all impacted customers.

  4. monitoring Feb 18, 2025, 04:02 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 18, 2025, 05:17 AM UTC

    This incident has been resolved.

Your product runs on more than IDVerse

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →