Autonomous System
AS703
Last fetched
AS703 is operated by UUNET - Verizon Business, registered in US, and announces 54 prefixes to 91 BGP neighbours. AS703 has a reputation score of 7.3 (REPUTABLE); 0 of its 705,552 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 54
- BGP neighbours
- 91
- RPKI ROAs
- 3
- MOAS conflicts
- 1
- CAIDA AS-rank
- 494
- Customer-cone ASNs
- 94
- Facilities
- 86
- Internet exchanges
- 14
- Customer degree
- 80
- Peer degree
- 38
- Provider degree
- 7
- 70.104.248.12/30
- 70.104.255.104/30
- 70.104.255.108/30
- 70.104.255.244/30
- 103.8.138.0/24
- 113.21.128.0/19
- 137.109.0.0/16
- 152.186.94.0/24
- 155.94.57.0/24
- 192.58.134.0/23
- 202.22.176.0/20
- 202.75.192.0/20
- 202.80.48.0/20
- 202.94.96.0/19
- 202.95.64.0/18
- 202.130.128.0/18
- 203.2.192.0/22
- 203.7.176.0/20
- 203.11.90.0/24
- 203.12.176.0/20
- 203.15.160.0/21
- 203.21.24.0/21
- 203.34.34.0/23
- 203.55.240.0/21
- 203.61.0.0/16
Infrastructure presence
Internet exchanges (14 total)
Facilities (86 total)
- Equinix SY1/SY2 - Sydney
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- KINX Dogok
- Equinix HK1 - Hong Kong
- Singapore Open Exchange (SOX)
- MEGA-i (iAdvantage Hong Kong)
- Equinix SG1 - Singapore
- Global Switch Singapore
- HKCOLO - Sino Favour Centre
- Equinix TY2 - Tokyo
- Chief LY Building Taipei
- Singapore - Science Park II
- TATA Communications Mumbai
- Sky Tower
- NTT DATA Otemachi Bldg
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- Equinix SG2 - Singapore
- AT TOKYO (CC1/CC2)
- CUHK
- Equinix HK2 - Hong Kong
- COLT in Asia Tokyo Data Center 1 (TDC1)
- 2degrees Auckland - Albany
- Mayoral Drive Exchange (MDR)
- Equinix SY3 - Sydney
- Web Werks Mumbai 1
Route origin authorizations
A sample of 3 of this network’s 3 ROAs.
- 152.186.94.0/24
- 155.94.57.0/24
- 194.169.18.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS703.
Blast radius
- Announced IPv4 addresses
- 705,552
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 48
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 25 of this network’s 91 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- UUNET - Verizon Business · AS701
- TWELVE99 - Arelion Sweden AB · AS1299
- ANSBB-ASNNET-1 - Verizon Business · AS1321
- ANS-ATLANTA - Verizon Business · AS1661
- ANS-UK - Verizon Business · AS1670
- ANS-1689-AS - Verizon Business · AS1689
- ANS-1699-AS - Verizon Business · AS1699
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- LEVEL3 - Level 3 Parent, LLC · AS3356
- DELL-BLK - Dell, Inc. · AS3614
- MCIASN-BLK - Verizon Business · AS3620
- SSB-ASN-3738 - State Street Bank and Trust Company · AS3738
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- STARHUB-INTERNET - StarHub Ltd · AS4657
- TATACOMM-AS - TATA Communications formerly VSNL is Leading ISP · AS4755
- KIXS-AS-KR-KR - Korea Telecom · AS4766
- OCBC-AS-AP - OCBC Bank (Hong Kong) Limited · AS4828
- INTEL-SC-AS - Intel Corporation · AS4983
- Opentransit - Orange S.A. · AS5511
- AS6220 - inContact Inc. · AS6220
- CELLCO-PART - Verizon Business · AS6256
- AS6453 - TATA COMMUNICATIONS (AMERICA) INC · AS6453
- SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A. · AS6762
- HURRICANE - Hurricane Electric LLC · AS6939
MOAS / hijack watch
1 announced prefix conflict with AS703 — another network announces the same address space. A sample:
Reputation
7.3reputation score (REPUTABLE)
AS703 (UUNET - Verizon Business, US) has a reputation score of 78.3 (REPUTABLE).
- Threat density
- 90.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
- Verizon Business
Threat-feed evidence
Related pages
Pivot from AS703 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.