Location
Lagoa Seca, Brazil
Within about 20 km
IPv4 address
187.86.80.0
Operated by Proxxima Telecomunicações in Lagoa Seca, Brazil.
Still looking this up. This tab fills in as the answers arrive.
Network Every network on the internet has an autonomous system number (ASN). This is the one that announces this address.
AS262773Proxxima Telecomunicações
Proxxima Telecomunicações
BGP prefixPrefix The block of addresses this IP is announced in to the rest of the internet. RPKI valid means the block's owner signed off on the network announcing it.
RPKI valid187.86.80.0/20
Seen by 2,643 peers
Latency Round trip for an HTTPS request from your browser to the site and back, including the server's reply time.
Live— ms
Measured along the route below
At a glance
Route
Finding a probe near you…
Networks crossed
Each network is an autonomous system (AS). Your traffic is handed from one to the next where they connect, following
the routes BGP advertises.
- AS16509Anthropic, PBC
- AS262773Proxxima Telecomunicações
Tracing from a probe near you with Globalping. Hop locations that its round-trip times rule out are left off the map.
Exposure
Open ports
None seenShodan hasn't found any open ports on this address.
From Shodan InternetDB, updated weekly.
Details
Network
- IPv4
- 187.86.80.0
- Reverse DNSThe hostname this address points back to (its PTR record).
- 187-86-80-0.PROXXIMA.NET
- ASNThe autonomous system number of the network that announces this address.
- AS262773
- Operator
- Proxxima Telecomunicações
- PrefixThe block of addresses announced over BGP that contains this address.
- 187.86.80.0/20
- RPKIWhether a signed record (ROA) authorizes this network to announce this prefix.
- Valid
- VisibilityHow many bgp.tools peers carry this announcement.
- 2,643 peers
- Type
- Eyeball
- Registry
- LACNIC
Location
- Country
- Brazil
- Region
- Paraíba
- City
- Lagoa Seca
- Coordinates
- 7.1422° S, 35.8324° W
- Accuracy
- Within about 20 km
- Time zone
- America/FortalezaUTC-3
- Local time
- 15:10
- Continent
- South America
Allocation
rdap.registro.br returned 403