Autonomous system
AS14847 PECKSERVERS-ROUTING
Hosting ARIN Content
Summary
Peck Servers
hosting isp
The one published hostname names two IPv6 transition mechanisms at once.
What it's used for
- A hosting provider's network. 256 IPv4 addresses in a single prefix alongside an IPv6
/40, with one observed BGP neighbour.
Notable
- One sampled address answers as
nat64-464xlat-190.peckservers.com, naming two mechanisms for carrying IPv4 traffic across an IPv6 network. - The IPv4 block is
23.136.84.0/24, carrying the netnamePECKSERVERS-WEBHOSTING. - The IPv6 block is
2602:f6af::/40. - The holder record and the AS handle both end in a routing suffix rather than a product one.
Interesting
- The IPv6 allocation is enormous next to the IPv4 one: a
/40against 256 addresses. That ratio is the whole point of the hostname, since a network with that much IPv6 and that little IPv4 needs translation to reach the older half of the internet at all. - Naming a host after the translation stack it runs is unusually candid. Most operators hide this layer behind generic labels, and finding it spelled out means the operator treats it as infrastructure worth labelling rather than a workaround worth hiding.
- Three fields describe three different things about the same company: routing in the holder record, routing in the handle, web hosting in the netname.
- One upstream for a hosting provider is the constraint the address plan cannot work around.
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.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS4181 | TDS TELECOM | 92 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-18, 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 · 256 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14847- Registry name
- PECKSERVERS-LLC-IP-ROUTING
- Registrant
- Peck Servers, LLC
- Abuse contact
- contact@peckservers.com
- Registered
- 2025-03-19
- Last changed
- 2025-09-05
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Peck Servers
- Network type
- Content
- Scope
- North America
- Traffic ratio
- Balanced
- Peering policy
- Open
- Website
- https://www.peckservers.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
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS14847
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 3 naming AS14847
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
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: 442 networks and 1,784 prefixes, as published 2026-10-19. 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