Autonomous System
AS270 — AS270 - National Aeronautics and Space Administration(US)
Last fetched
AS270 is an Autonomous System operated by AS270 - National Aeronautics and Space Administration and registered in US. As of Thu, 21 May 2026 06:16:46 GMT, it announces 186 routed IP prefixes and peers with 5 other Autonomous Systems in the WhisperGraph BGP dataset.
Nutrition Label
Routing footprint
AS270 announces 186 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.
- 128.102.0.0/16
- 128.154.0.0/17
- 128.154.128.0/17
- 128.155.0.0/16
- 128.156.0.0/16
- 128.157.0.0/16
- 128.158.0.0/16
- 128.159.0.0/16
- 128.183.0.0/16
- 128.217.0.0/16
- 129.164.0.0/16
- 129.164.128.0/17
- 129.168.0.0/18
- 129.168.64.0/18
- 129.168.0.0/16
- 129.168.128.0/18
- 129.168.192.0/18
- 130.40.0.0/16
- 130.134.0.0/16
- 130.135.0.0/16
- 131.182.0.0/16
- 134.12.0.0/17
- 134.118.96.0/19
- 134.118.112.0/22
- 136.178.0.0/16
Peering ecosystem
5 distinct peers via BGP. The first 5 are listed below.
| Peer ASN | Operator | Country |
|---|---|---|
| AS297 | AS297 - National Aeronautics and Space Administration | US |
| AS7847 | NASA-HPCC-ESS - NASA Goddard Space Flight Center | US |
| AS2143 | AS2143 - National Aeronautics and Space Administration | US |
| AS1701 | AS1701 - National Aeronautics and Space Administration | US |
| AS372 | AS372 - National Aeronautics and Space Administration | US |
Blast radius
Approximate count of dependent hostnames if AS270 disappeared from the routing table.
~681,374 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 06:16:46 GMT.
MOAS / hijack watch
Prefixes routed by AS270 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 AS270 is unique to AS270 in the current routing snapshot.
Threat posture
Related pages
Pivot deeper into the graph from AS270.
Cypher and MCP
Reproduce the headline metric directly against graph.whisper.security:
MATCH (a:ASN {name: "AS270"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.