Autonomous system
AS11179 ARYAKA-ARIN
Hosting ARIN Enterprise
Summary
Aryaka Networks, Inc.
enterprise transit legacy
ARYAKA-ARIN is Aryaka Networks, a managed SD-WAN and SASE provider. Aryaka does not sell access circuits; it runs its own global private core with points of presence in the major metros and hauls enterprise WAN traffic across it, so its address space is POP infrastructure and customer-facing service addresses rather than anything an end subscriber holds.
What it's used for
Running a distributed overlay backbone. RIS sees 140 IPv4 prefixes / 35,840 addresses, 3 IPv6 prefixes, and 77 observed neighbours. The prefixes are almost all /24s scattered across the world, and the high neighbour count against a fairly small address total is the giveaway of an interconnect-heavy network: many BGP sessions, in many places, carrying customer traffic that originates somewhere else entirely.
Notable
This is the inventory shape that normally means trouble — dozens of small blocks drawn from ARIN, RIPE and APNIC at once — and it is worth being explicit about why it does not mean trouble here. Every registrant is Aryaka itself: ARYAK, ARYAKA-NET-224-20, MNT-ARYAKA, and a series of US-ARYAKARIPE-<date> RIPE records. And the reverse DNS is uniformly first-party, right down to naming the AS in the hostname: ri5-236-75-147.11179.rev.aryaka.net. Self-registered space plus first-party rDNS is a real operator, however untidy the map looks.
Interesting
The scatter is a direct consequence of the business: to give a customer in Frankfurt, Singapore or Chicago a local on-ramp, you need routable space in each of those regions, and a global overlay accumulates it one small block per RIR per market.
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 2 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.212.73 |
| NAPAfrica IX Johannesburg | Johannesburg, South Africa | 196.60.8.223 |
Transit providers
33 upstream, 0 downstream and 34 adjacent networks observed; most-used upstreams first.
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 38 prefixes · 35.58K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 40 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS11179- Registry name
- ARYAKA-ARIN
- Registrant
- Aryaka Networks, Inc.
- Abuse contact
- ipmen@aryaka.com
- Registered
- 2010-12-06
- Last changed
- 2026-06-17
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Aryaka Networks
- Also known as
- GLOBAL SD-WAN
- Network type
- Enterprise
- Scope
- Global
- Traffic ratio
- Balanced
- Peering policy
- Open
- Present at
- 2 exchanges
- Facilities
- 27 facilities
- Website
- http://www.aryaka.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
- 98% valid · 139 valid, 3 with no ROA
- ROAs
- 140 authorising AS11179
- ASPA
- no ASPA record
- IRR
- 100% registered · 142 of 142 announcements
- Route objects
- 321 naming AS11179
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: 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