Autonomous System
AS30990
Last fetched
AS30990 is operated by DJIBOUTI TELECOM S.A. - DJIBOUTI TELECOM S.A., registered in DJ, and announces 69 prefixes to 34 BGP neighbours. AS30990 has a reputation score of 9.9 (REPUTABLE); 5 of its 43,776 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 69
- BGP neighbours
- 34
- RPKI ROAs
- 85
- MOAS conflicts
- 0
- CAIDA AS-rank
- 747
- Customer-cone ASNs
- 57
- Facilities
- 33
- Internet exchanges
- 6
- Customer degree
- 20
- Peer degree
- 17
- Provider degree
- 7
- 41.189.224.0/24
- 41.189.225.0/24
- 41.189.226.0/24
- 41.189.227.0/24
- 41.189.228.0/24
- 41.189.230.0/24
- 41.189.232.0/21
- 41.189.242.0/24
- 41.189.243.0/24
- 41.189.244.0/24
- 41.189.245.0/24
- 41.189.246.0/24
- 41.189.247.0/24
- 41.189.248.0/24
- 41.189.249.0/24
- 41.189.250.0/24
- 41.189.251.0/24
- 41.189.252.0/24
- 41.189.253.0/24
- 41.189.254.0/24
- 41.189.255.0/24
- 102.202.232.0/24
- 102.202.233.0/24
- 102.202.234.0/24
- 196.201.192.0/24
Routing posture
- Hijack posture score
- 0.08
- Route leaks
- 4
Leak types observed: TYPE1_HAIRPIN_TURN, TYPE4_PEER_TO_PROVIDER.
Signals
- critical-infrastructureServes infrastructure the internet depends on operationally.
Infrastructure presence
Internet exchanges (6 total)
Facilities (33 total)
- Equinix LD8 - London, Docklands
- Digital Realty London LHR19
- Digital Realty London LHR20
- Telehouse - London (Docklands East)
- Telehouse - London (Docklands North)
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Digital Realty London LON1-3
- Digital Realty Paris PAR2
- Equinix PA7 - Paris, Energy Park
- Digital Realty London LHR21 (closed)
- Digital Realty Marseille MRS1/2/3/4
- Equinix LD4 - London, Slough
- Equinix LD9 - London, Powergate
- Telehouse - Paris 3 (Magny)
- OPCORE - DC2 / PAR2
- Equinix PA3 - Paris, Saint-Denis
- Digital Realty Paris PAR5
- Equinix PA6 - Paris, Condorcet
- Telehouse - London (Docklands West)
- Equinix LD5 - London, Slough
- datamena DXA - Dubai
- OPCORE - DC3 / PAR3
- SmartHub Fujairah
- Djibouti Data Center
- Free Pro - Marseille - MRS1
Route origin authorizations
A sample of 10 of this network’s 85 ROAs.
- 102.202.232.0/22 · max length /24
- 196.201.192.0/20 · max length /24
- 197.241.0.0/17 · max length /24
- 2001:4298::/32 · max length /128
- 41.189.224.0/19 · max length /24
- 196.201.192.0/21
- 196.201.192.0/22
- 196.201.192.0/24
- 196.201.193.0/24
- 196.201.194.0/24
Upstreams
The networks that most often share an observed BGP path with AS30990.
Blast radius
- Announced IPv4 addresses
- 43,776
- Threat-listed addresses
- 5
- Threat density
- 0.0114 %
- Routed prefixes
- 67
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 34 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- Opentransit - Orange S.A. · AS5511
- ZAYO-6461 - Zayo Bandwidth · AS6461
- SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A. · AS6762
- HURRICANE - Hurricane Electric LLC · AS6939
- HUTCHISON-AS-AP - HGC Global Communications Limited · AS9304
- SES-LUX-AS - SES ASTRA S.A. · AS12684
- ITGATE - IT.Gate S.p.A. · AS12779
- CLOUDFLARENET - Cloudflare, Inc. · AS13335
- CLOUDFLARENET - Cloudflare, Inc. · AS14789
- CTGNet - CTGNet · AS23764
- SGGS-AS-AP - SG.GS · AS24482
- Ethio Telecom - Ethio Telecom · AS24757
- CMC NETWORK (PTY) LTD - CMC NETWORK (PTY) LTD · AS25818
- LIQUID-AS - Liquid Telecommunications Ltd · AS30844
- MEER-AS - meerfarbig GmbH & Co. KG · AS34549
- DATANET.COM LLC - DATANET.COM LLC · AS36901
- MIC TANZANIA LTD - MIC TANZANIA LTD · AS37035
- Telecom Malagasy - Telecom Malagasy · AS37054
- Hormuud Telecom Somalia INC - Hormuud Telecom Somalia INC · AS37371
- Telesom - Telesom · AS37473
- SOMTEL INTERNATIONAL Ltd - SOMTEL INTERNATIONAL Ltd · AS37563
- GLESYS - Glesys AB · AS42708
Reputation
9.9reputation score (REPUTABLE)
AS30990 (DJIBOUTI TELECOM S.A. - DJIBOUTI TELECOM S.A., DJ) has a reputation score of 70.2 (REPUTABLE).
- Threat density
- 74.1/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.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
- DJIBOUTI TELECOM S.A.
- RIR
- AFRINIC
- Registered
- Thu, 26 May 2016 06:46:00 GMT
Threat-feed evidence
Related pages
Pivot from AS30990 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.