Autonomous system
AS10632 PSE-AS
Unclassified ARIN
Summary
Puget Sound Energy
enterprise legacy
PSE-AS is Puget Sound Energy, the regulated electric and natural gas utility serving the Puget Sound region of Washington State, headquartered in Bellevue. This is a utility's corporate network, not a telecoms product: the "AS" in the handle is the ASN suffix, not part of a company name.
What it's used for
This is an end-site enterprise edge. The AS announces 12 IPv4 prefixes totalling 2,048 addresses, no IPv6, and RIS sees three observed neighbours.
Both numbers matter, and the neighbour count matters more. An energy utility of this size runs a very large internal estate, but almost all of it lives on private RFC 1918 space behind firewalls and on isolated operational-technology networks that never appear in BGP at all. What needs a public ASN and provider-independent space is the small public-facing and inter-connect surface, multi-homed across a few upstreams so that customer-facing systems and business connectivity survive a single provider outage. Three neighbours is exactly that shape: enough for redundancy, nowhere near enough to be reselling transit to anyone.
Notable
Every announced prefix falls inside one contiguous legacy range, 204.61.56.0/21. The utility announces the covering /22s, the /23s inside them, and then all eight constituent /24s as well, so the same 2,048 addresses appear in the table at three different levels of specificity at once.
That is deaggregation, and it is usually deliberate: announcing more-specifics of your own space is the standard way to steer inbound traffic across multiple upstreams, and it also narrows the window for a hijack of the covering block. The cost is table bloat, twelve routes where one would do.
Reverse DNS returned nothing on the 20 addresses sampled. That is a sample, not a finding, and nothing should be read into it.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-16, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 2.05K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 1 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS10632- Registry name
- PSE-AS
- Registrant
- Puget Sound Energy
- Abuse contact
- noc@pse.com
- Registered
- 1997-10-08
- Last changed
- 2019-09-04
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 12 with no ROA
- ROAs
- 0 authorising AS10632
- ASPA
- no ASPA record
- IRR
- 100% registered · 12 of 12 announcements
- Route objects
- 5 naming AS10632
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,783 prefixes, as published 2026-10-17. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere