Autonomous system
AS32413 EXIGO-EPIC - Epic Servers, LLC
Unclassified ARIN
Summary
Epic Servers
hosting business us
EXIGO-EPIC is operated by Epic Servers, LLC.
What it's used for
- The address space carries hosting infrastructure, evidenced by reverse DNS entries pointing to
ip.net.exigo.comand netnames likeEXIGO-NET-1throughEXIGO-NET-4andEPIC-NET-1. - The AS announces 10,240 IPv4 addresses across 5 prefixes with only 4 observed neighbours, indicating a small-scale hosting or business network rather than a transit provider.
Notable
- Registrants are split between
Exigo Office, INCfor four prefixes andEpic Servers, LLCfor one, suggesting a corporate relationship or acquisition history between the two entities. - The address inventory consists of five distinct IPv4 blocks with no IPv6 prefixes announced, reflecting a legacy IPv4-only footprint.
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-05, 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 · 10.24K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 5 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS32413- Registry name
- EXIGO-EPIC
- Registrant
- Epic Servers, LLC
- Abuse contact
- abuse@exigo.com
- Registered
- 2010-08-09
- Last changed
- 2023-12-18
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- AEPRIO
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS-EPICSERVERS- Website
- https://www.epic.io/
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 · 5 valid, 0 with no ROA
- ROAs
- 6 authorising AS32413
- ASPA
- no ASPA record
- IRR
- 100% registered · 5 of 5 announcements
- Route objects
- 17 naming AS32413
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: 453 networks and 1,854 prefixes, as published 2026-11-06. 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