Skip to content
Install MCP

Autonomous System

AS17222

Last fetched

AS17222 is operated by AS17222 - MUNDIVOX DO BRASIL LTDA, registered in BR, and announces 87 prefixes to 67 BGP neighbours. AS17222 has a reputation score of 8.9 (REPUTABLE); 31 of its 136,704 announced IPv4 addresses appear on threat feeds.

Nutrition Label

WHISPER CANON · AS17222Routing diversity9.7/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/17222

Routing footprint

Announced prefixes
87
BGP neighbours
67
RPKI ROAs
23
MOAS conflicts
0
CAIDA AS-rank
675
Customer-cone ASNs
67
Facilities
106
Internet exchanges
11
Customer degree
63
Peer degree
20
Provider degree
5

Infrastructure presence

Internet exchanges (11 total)

Facilities (106 total)

Route origin authorizations

A sample of 10 of this network’s 23 ROAs.

Upstreams

The networks that most often share an observed BGP path with AS17222.

Blast radius

Announced IPv4 addresses
136,704
Threat-listed addresses
31
Threat density
0.0227 %
Routed prefixes
78

How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.

Peering ecosystem

A sample of 25 of this network’s 67 BGP neighbours.

Reputation

8.9reputation score (REPUTABLE)

AS17222 (AS17222 - MUNDIVOX DO BRASIL LTDA, BR) has a reputation score of 73.3 (REPUTABLE).

Threat density
76.0/100
Graph metrics
90.0/100
Historical behaviour
85.0/100
Prefix age
20.0/100

These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.

Registration

Registered to
MUNDIVOX DO BRASIL LTDA
RIR
LACNIC
Registered
Thu, 17 Aug 2000 12:00:00 GMT
Abuse contact
aij6@numeracao.registro.br

This is the abuse contact WhisperGraph holds for the network.

Threat-feed evidence

Related pages

Pivot from AS17222 into the prefixes, peers and country it routes for.

Queries

This ASN's full card — routing footprint, peers, conflicts and RIR facts.


MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
     collect(an.name) AS operatorNames,
     collect(co.name) AS countries,
     collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
     collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
     collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
     collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
     collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
     collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
     collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
     collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
       a.rir AS rir,
       a.orgName AS orgName,
       a.asRank AS asRank,
       a.coneAsns AS coneAsns,
       a.conePrefixes AS conePrefixes,
       a.coneAddresses AS coneAddresses,
       a.registrationDate AS registrationDate,
       a.reputationScore AS reputationScore,
       a.reputationCategory AS reputationCategory,
       a.overallThreatLevel AS overallThreatLevel,
       a.abuseEmail AS abuseEmail,
       a.hijackPostureScore AS hijackPostureScore,
       a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
       a.routeLeakCount AS routeLeakCount,
       a.routeLeakTypes AS routeLeakTypes,
       a.degreeCustomer AS degreeCustomer,
       a.degreePeer AS degreePeer,
       a.degreeProvider AS degreeProvider,
       operatorNames, countries, organizations,
       samplePrefixes, samplePeers, sampleConflicts,
       signals, sampleExchanges, sampleFacilities, sampleRoas,
       prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCount
Run yourself →

The five networks that most often share this ASN's observed BGP paths.


MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observations
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.