Autonomous System
AS43566
Last fetched
AS43566 is operated by tyntec - TYNTEC S.A.C., registered in PE, and announces 2 prefixes to 2 BGP neighbours. AS43566 has a reputation score of 10.2 (NEUTRAL); 0 of its 512 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 2
- BGP neighbours
- 2
- RPKI ROAs
- 9
- MOAS conflicts
- 0
- CAIDA AS-rank
- 19,928
- Customer-cone ASNs
- 1
- Facilities
- 36
- Internet exchanges
- 3
- Customer degree
- 0
- Peer degree
- 79
- Provider degree
- 6
Infrastructure presence
Internet exchanges (3 total)
Facilities (36 total)
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Digital Realty Frankfurt FRA1-27
- ITENOS Frankfurt (FRA1)
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty Dusseldorf DUS1-3
- Telehouse - Frankfurt
- Digital Realty Frankfurt FRA28 (Closed)
- NewColo Frankfurt
- WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7
- NTT Frankfurt 1 Data Center (FRA1)
- Equinix DU1 - Dusseldorf
- Equinix FR2 - Frankfurt, North
- Equinix FR4 - Frankfurt, West
- Global Switch Frankfurt
- NewTelco Frankfurt
- NTT Frankfurt 2 Data Center (FRA2)
- TelemaxX IPC4
- WIIT Datacenter DUS5
- COLT DC Frankfurt
- CyrusOne Frankfurt 1
- Keppel Data Centres | Keppel DC Frankfurt 1
- Equinix FR6 - Frankfurt, West
- Digital Realty Frankfurt FRA29-32
- AtlasEdge DC Leverkusen LEV001
- maincubes FRA01
Route origin authorizations
A sample of 9 of this network’s 9 ROAs.
- 178.23.24.0/21 · max length /24
- 2a11:7f80::/32 · max length /36
- 78.110.224.0/21 · max length /24
- 78.110.232.0/24 · max length /24
- 78.110.233.0/24 · max length /24
- 78.110.234.0/24 · max length /24
- 78.110.235.0/24 · max length /24
- 78.110.236.0/22 · max length /24
- 91.199.83.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS43566.
Blast radius
- Announced IPv4 addresses
- 512
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 2
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 2 of this network’s 2 BGP neighbours.
Reputation
10.2reputation score (NEUTRAL)
AS43566 (tyntec - TYNTEC S.A.C., PE) 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
- TYNTEC S.A.C.
- RIR
- RIPE
- Registered
- Thu, 23 Aug 2007 12:47:50 GMT
- Abuse contact
- abuse@tyntec.pe
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS43566 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.