Autonomous system
AS14303 MEMASN1
Unclassified ARIN
Summary
City of Memphis
government infrastructure business
A netname from the era when a city network was called a metropolitan area network.
What it's used for
- A municipal government's network. 2,048 addresses across two IPv4 prefixes, with two observed BGP neighbours and no IPv6 announced.
Notable
167.29.0.0/22carries the netnameMEMPHIS-MAN, registered to the city with a DNS administration role contact.- The registry lookup for
167.29.12.0/22failed, so nothing is known about that block's record. - The two blocks sit in the same range with a gap of eight blocks between them.
- Six addresses were queried for reverse DNS and none returned a name.
Interesting
- The three letters at the end of that netname stand for metropolitan area network, a term for the city-scale fibre rings that municipalities and universities built to join their own buildings together, in the decade before this AS was first seen routing. The technology behind the phrase is long gone and the name outlived it, which is the usual fate of a registry field.
- Naming a DNS administrator as the contact is a small piece of good practice, since address records and name records are managed by the same people and most registrations name neither.
- The gap between the two blocks is space the city either never received or gave back, and it costs a second announcement to work around.
- Two upstreams and nothing published fits a network carrying payroll, permits, police and traffic systems that have no reason to be reachable by name.
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-25, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 2.05K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14303- Registry name
- MEMASN1
- Registrant
- City of Memphis
- Abuse contact
- dnsadmin@cityofmemphis.org
- Registered
- 2007-10-15
- Last changed
- 2012-03-02
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS14303
- ASPA
- no ASPA record
- IRR
- 0% registered · 0 of 2 announcements
- Route objects
- 0 naming AS14303
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: 443 networks and 1,779 prefixes, as published 2026-10-24. 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