Autonomous system
AS11597 MW-KANSAS
Residential ARIN Cable/DSL/ISP
Summary
Mercury Broadband
isp legacy
MW-KANSAS is Mercury Broadband (formerly Mercury Wireless), a Midwestern fixed-wireless and fibre internet provider serving rural and small-town Kansas, Missouri, Indiana and neighbouring states. The handle preserves the Kansas origin; the rDNS preserves the old name.
What it's used for
This is the cleanest eyeball-ISP evidence in the batch. RIS shows 36 announced IPv4 prefixes, 10,240 addresses, 6 IPv6 prefixes (a 2605:ae80::/32 with four /36s carved from it) and 9 observed neighbours. Every prefix RDAP resolved registers to Mercury Broadband itself, under MERCURY-WIRELESS and MWIN — not one third-party registrant, which removes the leased-address question entirely.
Reverse DNS settles the use. Nineteen sampled addresses across nine different prefixes all resolve to the same template: host204-10-232-005.rev.mercurywireless.com, host104-218-88-005.rev.mercurywireless.com, and so on. A single machine-generated PTR pattern applied uniformly across the whole estate is how an access provider numbers subscriber lines. Individual servers get individual names; customer pools get templates.
The prefix list is heavily deaggregated — /21s and /22s announced alongside the /23s and /24s inside them — which is what a wireless operator does when different tower clusters hang off different upstreams. Nine neighbours is consistent: several transit providers plus regional peering, not a carrier role.
Notable
The /36s carved out of the IPv6 /32 and announced separately point the same way: per-region or per-POP allocations for distributing addresses to customers. Mercury holds and announces its own space, runs its own rDNS, and uses it for residential broadband.
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 |
|---|---|---|
| Kansas City Internet Exchange | Kansas City, United States | 206.51.7.236 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 15 prefixes · 10.24K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 16 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS11597- Registry name
- MW-KANSAS
- Registrant
- Mercury Broadband
- Abuse contact
- ntac@mercuryfiber.com
- Registered
- 2010-12-07
- Last changed
- 2014-04-24
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Mercury Broadband
- Network type
- Cable/DSL/ISP
- Scope
- Not Disclosed
- Traffic ratio
- Heavy Inbound
- Peering policy
- Open
- IRR as-set
AS-AS11597-MW- Facilities
- 2 facilities
- Website
- https://mercurybroadband.com/
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, 44 with no ROA
- ROAs
- 1 authorising AS11597
- ASPA
- no ASPA record
- IRR
- 100% registered · 44 of 44 announcements
- Route objects
- 14 naming AS11597
Reputation
Classification and threat
Residential Fixed-line consumer ISP. Addresses here are homes.
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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