AS270
Operated by AS270 - National Aeronautics and Space Administration.
Summary
- // analyst note
- Early actively-routed government ASN registered to NASA. WHOIS/RDAP and all routing sources agree on identity; only ambiguity is upstream-vs-downstream among five all-NASA neighbours. A1 canonical RDAP timed out; allocated_date 1989-02-24 confirmed via A3 re-fetch of the un-truncated autnum top-level events[].
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-21; not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives.
About this ASN.
AS270 is a legacy autonomous system number registered under ARIN to the National Aeronautics and Space Administration (NASA), the U.S. civilian space agency established on October 1, 1958 by the National Aeronautics and Space Act. The ASN sits at the low, early-allocation end of the ARIN registry — its autnum top-level registration event carries a date of 1989-02-24, making it one of the oldest ASNs in the region and a direct reflection of NASA's foundational role in the early Internet. Per BGP registries the network is named the Program Support Communication Network (PSCN), a fully digital internal wide-area network that interconnected all NASA centers and contractor/international locations for voice, video, data, and facsimile communications. Unlike a commercial ISP, AS270 is a closed government enterprise network: routing sources agree it announces roughly 185–187 IPv4 prefixes (~1.85–2.12 million addresses) and zero IPv6 prefixes, with only about five observed BGP neighbours — every one of them another NASA autonomous system (AS297, AS372, AS1701, AS2143, AS7847). It holds no PeeringDB record and shows no Internet Exchange participation, consistent with internal-only peering and upstream transit rather than open peering or transit-offering. RIS visibility is complete for its IPv4 announcements (327/327 peers), and routing has been continuously observed since roughly 2000. No notable public abuse signal was found as of June 2026 — not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives. Where NASA appears in security reporting it is as the TARGET of external attacks (e.g. a 2024 North Korean ransomware indictment, a 2025 GAO risk-management finding), never as a source of outbound abuse from AS270's routed prefixes.
- Operator
- National Aeronautics and Space Administration (NASA); U.S. federal civilian space agency; ARIN org handle NASA-Z [Confirmed] — ARIN RDAP autnum/270, nasa.gov/about
- Country / RIR
- United States, ARIN [Confirmed] — ARIN RDAP autnum/270; RIPEstat abuse-contact-finder (authoritative_rir: arin)
- Allocated
- 1989-02-24 (ARIN registry date from the autnum top-level events[] registration event — a first-party RIR fact, NOT an IEEE date); last changed 2024-12-16 [Confirmed] — ARIN RDAP autnum/270 top-level events
- Org status
- active U.S. federal government agency; established 1958-10-01 under the National Aeronautics and Space Act; civilian space agency in the executive branch [Confirmed] — nasa.gov/about
- Contacts
- abuse@nasa.gov; NOC noc@nisn.nasa.gov, +1-256-961-4000 (Marshall Space Flight Center); technical dns@nasa.gov; registration address MSFC, AL 35812; NASA HQ 300 E Street SW, Washington, DC 20546 [Confirmed for abuse/RIR via RIPEstat + RDAP; Likely for NOC/HQ details via RDAP entities] — ARIN RDAP autnum/270, RIPEstat abuse-contact-finder
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal found as of 2026-06-21 — not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives [Likely — negative findings via public search, not live per-service API]. NASA as an organization has been an attack TARGET (July 2024 North Korean ransomware indictment; GAO-25-108138 cybersecurity risk-management gaps), not a source of outbound abuse from AS270
Network & routing
- Network type
- government — U.S. federal agency internal WAN / enterprise network (Program Support Communication Network, PSCN) interconnecting NASA centers and contractor locations; not a commercial ISP or transit provider [Confirmed] — bgp.he.net/AS270, GAO AIMD-96-33, ipinfo.io/AS270
- Size
- ~185–187 IPv4 prefixes, roughly 1.85M–2.12M IPv4 addresses; 0 IPv6 prefixes [Confirmed] — RIPEstat routing-status / announced-prefixes (187 v4 / 0 v6 / ~2.12M IPs); ipinfo.io/AS270, ipregistry.co/AS270
- Routing/peering
- announced and fully visible (327/327 RIS v4 peers, 0/322 v6); ~5 observed neighbours, all NASA ASNs (AS297 upstream; AS372, AS1701, AS2143, AS7847 downstream); routing first seen ~2000-08-18, last seen 2026-06-21 [Confirmed for visibility/neighbour count via RIPEstat; Likely for upstream-vs-downstream classification via bgp.tools/ipinfo, since RIPEstat does not classify role]
- Peering policy / IX presence
- no public peering policy page found; no PeeringDB record; no Internet Exchange participation found — consistent with a closed internal-only government WAN [Likely] — bgp.tools/as/270, ipinfo.io/AS270
- RPKI
- not assessed — per-prefix RPKI validation was skipped in the canonical fetch (no prefix supplied); bgp.he.net reportedly shows 0 RPKI-invalid originations [Unknown for ROA coverage; Likely for 0 invalid] — bgp.he.net/AS270
- Notable usage
- one of the earliest ARIN ASNs (registered 1989-02-24); the PSCN interconnected all NASA centers and contractor/international locations for voice, video, data, and facsimile; ~185–187 IPv4 prefixes, no IPv6; major router infrastructure co-located with NASA facilities (Greenbelt MD, Huntsville AL, Houston TX, San Jose CA, Ashburn VA) [Confirmed for tenure/PSCN; Likely for the city list per third-party geo] — ARIN RDAP, GAO AIMD-96-33, ipinfo.io/AS270, bgp.tools/as/270
- Related ASNs
- AS297, AS372, AS1701, AS2143, AS7847 (all NASA) [Confirmed] — bgp.tools/as/270, ipinfo.io/AS270
- Analyst note
- Encountered as an early, actively-routed government ASN registered to NASA. WHOIS/RDAP and all routing sources agree on the NASA identity; the only role ambiguity is upstream-vs-downstream among the five all-NASA neighbours. A1 canonical RDAP timed out on first fetch; allocated_date 1989-02-24 was confirmed via an A3 re-fetch of the un-truncated autnum top-level events[].
What this network routes.
- 198.120.0.0/14
- 163.205.0.0/16
- 129.164.0.0/16
- 131.182.0.0/16
- 128.102.0.0/16
- 128.217.0.0/16
- 136.178.0.0/16
- 156.68.0.0/16
- 128.158.0.0/16
- 129.168.0.0/16
- 163.206.0.0/16
- 128.159.0.0/16
- 146.165.0.0/16
- 130.40.0.0/16
- 130.134.0.0/16
- 128.157.0.0/16
- 146.154.0.0/16
- 148.114.0.0/16
- 138.115.0.0/16
- 128.156.0.0/16
- 158.154.0.0/16
- 139.88.0.0/16
- 128.183.0.0/16
- 128.155.0.0/16
- 139.169.0.0/16
- 143.232.0.0/16
- 130.135.0.0/16
- 134.12.0.0/17
- 128.154.0.0/17
- 129.164.128.0/17
- 128.154.128.0/17
- 129.168.128.0/18
- 129.168.192.0/18
- 129.168.64.0/18
- 129.168.0.0/18
- 134.118.96.0/19
- 192.225.64.0/19
- 156.68.96.0/20
- 156.68.112.0/20
- 156.68.16.0/20
- 192.77.80.0/20
- 156.68.0.0/20
- 198.116.240.0/21
- 156.68.240.0/21
- 156.68.128.0/21
- 156.68.40.0/21
- 156.68.136.0/21
- 198.116.248.0/21
- 156.68.200.0/21
- 156.68.208.0/21
- 192.77.32.0/21
- 156.68.160.0/21
- 156.68.184.0/21
- 156.68.176.0/21
- 156.68.80.0/21
- 156.68.168.0/21
- 156.68.224.0/21
- 156.68.232.0/21
- 156.68.72.0/21
- 156.68.144.0/21
- 156.68.216.0/21
- 156.68.152.0/21
- 156.68.48.0/21
- 192.150.32.0/21
- 192.112.16.0/22
- 156.68.64.0/22
- 134.118.112.0/22
- 156.68.36.0/22
- 156.68.252.0/22
- 156.68.32.0/22
- 156.68.248.0/22
- 156.68.92.0/22
- 156.68.60.0/22
- 156.68.68.0/22
- 156.68.56.0/23
- 192.77.40.0/23
- 156.68.88.0/23
- 192.88.40.0/23
- 198.182.30.0/23
- 156.68.90.0/23
- 156.68.58.0/23
- 192.55.90.0/23
- 192.48.14.0/24
- 192.52.91.0/24
- 192.67.115.0/24
- 192.160.78.0/24
- 192.77.45.0/24
- 192.70.122.0/24
- 192.70.123.0/24
- 192.52.217.0/24
- 192.68.196.0/24
- 198.27.40.0/24
- 198.27.43.0/24
- 192.58.36.0/24
- 192.52.89.0/24
- 192.70.120.0/24
- 192.52.81.0/24
- 192.58.21.0/24
- 192.112.11.0/24
- 192.88.44.0/24
- 192.77.27.0/24
- 192.100.14.0/24
- 198.27.47.0/24
- 192.67.186.0/24
- 198.27.46.0/24
- 192.52.215.0/24
- 192.52.83.0/24
- 192.107.191.0/24
- 192.68.194.0/24
- 192.88.49.0/24
- 198.182.28.0/24
- 192.52.206.0/24
- 192.52.95.0/24
- 192.52.82.0/24
- 192.77.30.0/24
- 192.58.19.0/24
- 198.27.42.0/24
- 192.149.128.0/24
- 192.88.36.0/24
- 192.77.26.0/24
- 192.77.31.0/24
- 192.88.46.0/24
- 192.77.28.0/24
- 192.77.43.0/24
- 192.88.37.0/24
- 192.92.199.0/24
- 192.52.78.0/24
- 192.189.100.0/24
- 192.52.213.0/24
- 192.112.9.0/24
- 192.52.212.0/24
- 192.88.32.0/24
- 192.52.84.0/24
- 192.67.109.0/24
- 192.92.197.0/24
- 192.52.88.0/24
- 198.119.2.0/24
- 192.77.44.0/24
- 194.85.23.0/24
- 192.92.198.0/24
- 192.52.90.0/24
- 192.52.80.0/24
- 192.67.110.0/24
- 192.88.33.0/24
- 192.70.125.0/24
- 198.27.34.0/24
- 192.52.86.0/24
- 192.88.43.0/24
- 156.68.195.0/24
- 192.52.87.0/24
- 192.68.192.0/24
- 192.160.74.0/24
- 192.100.9.0/24
- 156.68.193.0/24
- 192.88.31.0/24
- 156.68.192.0/24
- 192.52.207.0/24
- 192.52.92.0/24
- 198.27.39.0/24
- 192.77.42.0/24
- 192.149.107.0/24
- 192.70.124.0/24
- 192.52.85.0/24
- 192.70.126.0/24
- 156.68.194.0/24
- 192.225.88.0/24
- 192.52.198.0/24
- 192.112.224.0/24
- 192.112.230.0/24
- 192.76.235.0/24
- 198.27.41.0/24
- 156.68.31.0/24
- 192.52.94.0/24
- 192.52.214.0/24
- 198.27.44.0/24
- 192.77.29.0/24
- 192.68.197.0/24
- 192.149.141.0/24
- 198.27.49.0/24
- 192.88.48.0/24
- 192.52.216.0/24
- 192.52.98.0/24
- 198.27.45.0/24
- 192.149.140.0/24
- 192.52.211.0/24
- 192.112.10.0/24
- 198.27.37.0/24
Who it talks to.
| ASN | Operator | Role |
|---|---|---|
| AS297 | AS297 - National Aeronautics and Space Administration | upstream |
| AS2143 | AS2143 - National Aeronautics and Space Administration | downstream |
| AS372 | AS372 - National Aeronautics and Space Administration | downstream |
| AS1701 | AS1701 - National Aeronautics and Space Administration | downstream |
| AS7847 | NASA-HPCC-ESS - NASA Goddard Space Flight Center | downstream |