Skip to content

Autonomous System

AS22697 — ROBLOX-PRODUCTION - Roblox(US)

Last fetched

AS22697 is an Autonomous System operated by ROBLOX-PRODUCTION - Roblox and registered in US. As of Tue, 11 Aug 2026 19:18:38 GMT, it announces 60 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS22697Routing diversity8.9/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/22697

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS11281ROBLOX-CORPORATE - RobloxUS
AS12956IDDQD-AS - IDDQD-ASES
AS1299TWELVE99 - Arelion Sweden ABSE
AS136766RBX-AS-AP - ROBLOX (SHENZHEN) DIGITAL SCIENCE AND TECHNOLOGY CO., LTDCN
AS2914NTT-DATA-2914 - NTT America, Inc.US
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS34549MEER-AS - meerfarbig GmbH & Co. KGDE
AS4637ASN-TELSTRA-GLOBAL - Telstra GlobalHK
AS4755TATACOMM-AS - TATA Communications formerly VSNL is Leading ISPIN
AS48362TKSWF-AS - Stadtwerke FeldkirchAT
AS6762SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A.IT
AS6939HURRICANE - Hurricane Electric LLCUS
AS9304HUTCHISON-AS-AP - HGC Global Communications LimitedHK

Blast radius

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

119 hostnames depend on this network.Exact count across all 59 announced prefixes. Snapshot Sat, 11 Jul 2026 03:01:19 GMT.

MOAS / hijack watch

Prefixes routed by AS22697 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 AS22697 is unique to AS22697 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS22697.

Cypher and MCP

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

MATCH (a:ASN {name: "AS22697"})-[: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.