Autonomous System
AS8360
Last fetched
AS8360 is operated by UNSPECIFIED - Allianz Technology SE, registered in DE, and announces 27 prefixes to 4 BGP neighbours. AS8360 has a reputation score of 10.2 (NEUTRAL); 0 of its 6,912 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 27
- BGP neighbours
- 4
- RPKI ROAs
- 35
- MOAS conflicts
- 0
- CAIDA AS-rank
- 19,634
- Customer-cone ASNs
- 1
- Facilities
- 33
- Internet exchanges
- 7
- Customer degree
- 0
- Peer degree
- 53
- Provider degree
- 4
- 103.85.135.0/24
- 103.119.72.0/24
- 103.119.73.0/24
- 103.233.172.0/24
- 103.233.173.0/24
- 103.233.174.0/24
- 103.233.175.0/24
- 193.194.10.0/24
- 193.194.11.0/24
- 194.127.21.0/24
- 194.127.31.0/24
- 194.127.68.0/24
- 194.127.69.0/24
- 194.127.70.0/24
- 194.127.71.0/24
- 194.127.72.0/24
- 194.127.73.0/24
- 194.127.74.0/24
- 194.127.75.0/24
- 194.127.77.0/24
- 194.127.78.0/24
- 194.127.79.0/24
- 194.127.80.0/24
- 203.23.96.0/24
- 203.23.97.0/24
Infrastructure presence
Internet exchanges (7 total)
Facilities (33 total)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix CH1/CH2/CH4 - Chicago
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix SV8 - Silicon Valley, Palo Alto
- Equinix DA1 - Dallas
- Equinix DA3 - Dallas
- Equinix SY1/SY2 - Sydney
- Equinix SP4 - São Paulo
- Equinix SG1 - Singapore
- Equinix SV2 - Silicon Valley, Santa Clara
- Equinix SV3 - Silicon Valley, San Jose
- Digital Realty CHI (350 E Cermak)
- Equinix DA4 - Dallas
- Equinix SV4 - Silicon Valley, Sunnyvale
- Equinix ME5 - Melbourne (formerly Metronode Melbourne 1)
- Equinix SG2 - Singapore
- Equinix CU1/CU2/CU3/CU4 - Culpeper
- Equinix CH3 - Elk Grove
- Equinix SY3 - Sydney
- Equinix ME1/ME2 - Melbourne
- Equinix DA6 - Dallas
- Equinix SG3 - Singapore
- Equinix SY6 - Sydney (formerly Metronode Sydney 2)
- Equinix DA7 - Dallas
- Equinix DA2 - Dallas
Route origin authorizations
A sample of 10 of this network’s 35 ROAs.
- 103.119.72.0/23 · max length /23
- 103.119.72.0/24 · max length /24
- 103.119.73.0/24 · max length /24
- 103.233.172.0/23 · max length /24
- 103.233.174.0/23 · max length /23
- 103.233.174.0/24 · max length /24
- 103.233.175.0/24 · max length /24
- 103.85.135.0/24 · max length /24
- 203.23.96.0/24 · max length /24
- 203.23.97.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS8360.
Blast radius
- Announced IPv4 addresses
- 6,912
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 27
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: clean.
Peering ecosystem
A sample of 4 of this network’s 4 BGP neighbours.
Reputation
10.2reputation score (NEUTRAL)
AS8360 (UNSPECIFIED - Allianz Technology SE, DE) has a reputation score of 69.5 (NEUTRAL).
- Threat density
- 90.0/100
- Graph metrics
- 55.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
- Allianz Technology SE
- RIR
- RIPE
- Registered
- Wed, 04 Sep 2002 05:17:19 GMT
- Abuse contact
- abuse@allianz.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS8360 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, ixpCountRun 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, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.