Skip to content

Autonomous System

AS2609 — TN-BB-AS - IDDQD-AS(TN)

Last fetched

AS2609 is an Autonomous System operated by TN-BB-AS - IDDQD-AS and registered in TN. As of Fri, 04 Sep 2026 08:18:54 GMT, it announces 65 routed IP prefixes and peers with 12 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS2609Routing diversity9.1/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/2609

Routing footprint

AS2609 announces 65 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

12 distinct peers via BGP. The first 12 are listed below.

Peer ASNOperatorCountry
AS31245ATI - Agence Tunisienne Internet - ATI - Agence Tunisienne InternetTN
AS3257GTT-BACKBONE - GTT Communications Inc.US
AS327934SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom) - SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)TN
AS328414STE NEXT STEP IT - STE NEXT STEP ITTN
AS329268STE SAFOZI - STE SAFOZITN
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS37551ATI - Agence Tunisienne Internet - ATI - Agence Tunisienne InternetTN
AS376713S INF - 3S INFTN
AS37705TOPNET - TOPNETTN
AS5438ATI-TN - Agence Tunisienne d'InternetTN
AS5511Opentransit - Orange S.A.FR
AS6762SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A.IT

Blast radius

Count of dependent hostnames if AS2609 disappeared from the routing table.

6,235 hostnames depend on this network.Exact count across all 55 announced prefixes. Snapshot Thu, 16 Jul 2026 02:01:06 GMT.

MOAS / hijack watch

Prefixes routed by AS2609 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS2609 is unique to AS2609 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS2609.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS2609"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

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