Autonomous system
AS12102 CITY-OF-PORTLAND-OR-USA - City of Portland
Unclassified ARIN
Summary
City of Portland
government legacy
The network of the City of Portland, Oregon.
What it's used for
- Municipal government systems. One
/22of 1,024 addresses with three observed BGP neighbours, no IPv6 announced.
Notable
- A single announcement,
74.120.152.0/22, registered under the netnameCITY-OF-PORTLAND-OR-USA— the same string used as the AS handle. - The sampled reverse name is
254.154.ptldnet.portlandoregon.gov: the last two octets in reverse order, thenptldnetfor the city network, under a.govdomain. - First seen in the routing data in June 2007.
Interesting
- Three upstreams for one
/22is more redundancy than the address count suggests. A city runs emergency dispatch, water and traffic systems on the same network as its payroll, and the cost of a third circuit is small against any of those going dark. - Portland's
.govis worth putting next to Aurora'sci.aurora.co.usat AS12156. Both are city networks of similar size; one moved to the federal government namespace and one stayed in the geographic.ushierarchy that was originally meant for exactly this purpose. The.usscheme lost because.govcarried authority that a hierarchy of place names never did.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Northwest Access Exchange | Portland, United States | 198.32.195.103 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, 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 · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 1 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS12102- Registry name
- CITY-OF-PORTLAND-OR-USA
- Registrant
- City of Portland
- Abuse contact
- Hostmaster@portlandoregon.gov
- Registered
- 2007-05-16
- Last changed
- 2012-03-02
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- City of Portland
- Scope
- Not Disclosed
- Traffic ratio
- Mostly Inbound
- Peering policy
- Selective
- IRR as-set
RADB::AS-COP- Present at
- 1 exchanges
- Facilities
- 1 facilities
- Website
- http://www.portlandoregon.gov
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 1 with no ROA
- ROAs
- 0 authorising AS12102
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 2 naming AS12102
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: 447 networks and 1,843 prefixes, as published 2026-11-01. 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