Autonomous system
AS16502 CITY-OF-PHOENIX - City of Phoenix
Unclassified ARIN
Summary
City of Phoenix
government infrastructure business
The contact on every block is a department's initials followed by the name of its web team.
What it's used for
- A municipal government's network. Eleven IPv4 prefixes announced from the United States, no IPv6, twelve thousand two hundred and eighty-eight addresses, through two observed BGP neighbours.
Notable
- All eleven blocks come from one parent range, carry the same netname, and list the same contacts. The netname is three letters for the city and three for a government.
- Beside the city, each block names a contact built from three initials for a technology department and then a mixed-case word joining the city's abbreviation to the word for the web.
- The pieces come at three sizes and are scattered through the parent range rather than adjacent, so none of them can be combined.
- The AS handle spells the city out in three hyphenated words, including the joining word that the netname drops.
- Eighteen addresses were queried for reverse DNS and none returned a name.
Interesting
- A web team as the registered contact for the whole city network is a snapshot of which office owned the internet when the paperwork was filed. The addresses outlived the org chart, and the record still points at the team that was in charge of the front page.
- Publishing nothing in reverse DNS is a choice, and for a city it is the quieter one. Every address here belongs to a government, and none of them says so to anyone who asks the resolver.
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-11-01, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 11 prefixes · 12.29K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 11 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS16502- Registry name
- CITY-OF-PHOENIX
- Registrant
- City of Phoenix
- Abuse contact
- abuse@phoenix.gov
- Registered
- 2016-08-19
- Last changed
- 2016-08-19
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 34 with no ROA
- ROAs
- 0 authorising AS16502
- ASPA
- no ASPA record
- IRR
- 100% registered · 34 of 34 announcements
- Route objects
- 30 naming AS16502
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-02. 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