Quick Search: Finding an IP, ASN, or Service Tag
Use quick search to jump straight to any IP, ASN or service tag, a Monocle app, or a main area of the app, from anywhere, without navigating through menus.
Difficulty
Beginner
No prior Spur experience needed
Time estimate
1 minute
Typical time to complete
What you'll achieve
- Open quick search from anywhere in the app
- Search for an IP, ASN, or service tag
- Jump straight to its page from the results
- Jump to a main area of the app or a Monocle app
Steps
- 1
Open quick search
Press / from anywhere in the app (as long as you're not typing in another field), or click the Search field in the top navigation.
- 2
Type your query
Enter an IP address, ASN or service tag name. Matching results appear as you type, grouped into Recent searches, Service tags, Autonomous systems, Monocle apps and Quick actions.
- 3
Select a result
Use the arrow keys and Enter, or click a result, to jump straight to that IP's, ASN's, or service tag's page.
- 4
Use quick actions
Quick actions take you straight to Home, Monocle, Context API, Data Feeds, Settings, Support or Documentation. Your Monocle apps are listed too, so you can open one directly.
Related FAQs & guides
How do I dispute an incorrect IP or ASN geolocation?
If you believe an IP, CIDR, or ASN is geolocated incorrectly, open it in the Spur app and select the Report button (the warning-triangle icon) on its IP or ASN page. Choose Incorrect Labels, and under Additional information give the location Spur reports, the location you expect, and the evidence behind it. For a range, report one IP from it and list the full CIDR in your message. Your own measurements, such as traceroute or latency results from a known location, are the most useful. Registration records and other providers' results are helpful context, but Spur locates IPs from observed network measurement, so our research team reviews each report against that before making any correction. If you don't have access to the Spur app, email support@spur.us with the same details.
Expanding IP and Service Rows in the Explorer
Click any IP or service row in the Monocle Explorer's breakdown tables to expand an inline detail panel, without leaving the table.
Why did I get a Monocle health email?
A Monocle health email means one of your Monocle applications has gone longer than its health threshold without traffic, which usually means Monocle is no longer installed or running correctly on that site or app. Only organization admins get these emails. Check that the integration is still in place, or, if the application is simply quiet, set a longer threshold under Alert after on the application's Settings page. Admins can turn the email off for an application in the same Notifications section, or for themselves on their Profile page. See Understanding Monocle Application Health Status.
What is the difference between using Monocle to monitor vs. enforce traffic decisions?
Monitor is passive: Monocle provides visibility into how users connect to your application without impacting users or taking any blocking action. Enforce applies actions such as blocking or allowing traffic based on Monocle's assessments. Most users start with a monitoring phase before configuring and enabling enforcement.
What does "client count" mean in Spur's data?
It's Spur's count of instances or connections observed from a given IP. As a general signal, a high count often points to shared infrastructure such as carrier-grade NAT, where many users' traffic passes through the same address, while a low count is more consistent with dedicated, single-tenant infrastructure. Treat it as a supporting signal alongside other data rather than a definitive classification on its own.
What does "Client Proxies" mean in Spur's data?
It refers to proxy client ecosystems or networks observed interacting through an IP, based on Spur telemetry. It does not mean the IP is owned or operated by the named provider — only that related activity was observed from it.