Skip to content

Clarify when ip_risk_snapshot is not populated #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marselester merged 1 commit into from
Dec 16, 2025
Merged

Clarify when ip_risk_snapshot is not populated #133

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion lib/maxmind/geoip2/record/traits.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,15 @@ def user_count
# services is more static than the IP risk score provided in minFraud
# and is not responsive to traffic on your network. If you need realtime
# IP risk scoring based on behavioral signals on your own network, please
# use minFraud. This property is only available from Insights.
# use minFraud.
#
# We do not provide an IP risk snapshot for low-risk networks. If this
# field is not populated, we either do not have signals for the network
# or the signals we have show that the network is low-risk. If you would
# like to get signals for low-risk networks, please use the minFraud web
# services.
#
# This property is only available from Insights.
#
# @return [Float, nil]
def ip_risk_snapshot
Expand Down