Autonomous system
AS13549 MERCURY
Unclassified ARIN
Summary
Mercury Network
isp hosting business
Five prefixes tiling one range, all under a netname that stamps the protocol version onto space that has an IPv6 sibling.
What it's used for
- A regional network provider. 8,192 addresses across five IPv4 prefixes, the IPv6 block
2604:8fc0::/32, and four observed BGP neighbours.
Notable
- The prefixes are a /20, a /21, a /22 and two /23s, all inside
64.7, laid end to end with no gaps. - All five carry the same netname,
MERCURY-V4-1, registered to the company. - Seven of fifteen sampled addresses answered, each as the address with hyphens under
mercury.net. - The sampled names end in
.254,.126and.128, addresses that sit at small subnet boundaries.
Interesting
- One registry object split into five announcements that exactly cover it is deaggregation for its own sake, or the residue of a plan to steer pieces separately that was never finished. Four upstreams make the second reading plausible in a way a single-homed network would not.
- Numbering the netname
V4-1while holding a full IPv6 /32 is unusual bookkeeping: most operators who stamp the version onto IPv4 never register the other half, and this one did. - Answers clustering at
.126,.128and.254are gateway addresses of subnets carved out of the block for individual customers. The generated names are uniform, but which ones exist is not.
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 |
|---|---|---|
| Detroit Internet Exchange | Detroit, United States | 209.124.52.23 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 8.19K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 6 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS13549- Registry name
- MERCURY
- Registrant
- Mercury Network Corporation
- Abuse contact
- abuse@mercury.net
- Registered
- 1999-09-13
- Last changed
- 2012-03-02
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 100% valid · 4 valid, 0 with no ROA
- ROAs
- 2 authorising AS13549
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 7 naming AS13549
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: 431 networks and 1,768 prefixes, as published 2026-10-12. 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