Autonomous system
AS27418 OOW-INC
Hosting ARIN Content
Summary
Outofwall Inc
content business us
OOW-INC is the AS handle for Outofwall Inc.
What it's used for
- The address space carries content delivery infrastructure, evidenced by the netname
US-ZENLAYER-20120425associated with the prefix199.182.232.0/24. - The AS announces 512 IPv4 addresses across 2 prefixes and 1 IPv6 prefix, while maintaining only 1 observed neighbour, a ratio that suggests a specialized or internal network rather than a general transit provider.
Notable
- Registrants differ from the announcer;
23.149.48.0/24is registered toOUTOFWALL INC.with netnameOOW-4-1, while199.182.232.0/24is registered toZenlayer Incwith netnameUS-ZENLAYER-20120425. - The address inventory is small and split between two distinct registrants, indicating a mix of owned and leased or partner space.
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 |
|---|---|---|
| AS21859 | Zenlayer Inc | 644 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-27, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 3 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS27418- Registry name
- OOW-INC
- Registrant
- OUTOFWALL INC.
- Abuse contact
- root@outofwall.com
- Registered
- 2012-10-18
- Last changed
- 2013-12-26
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Outofwall Inc
- Network type
- Content
- Peering policy
- Open
- Facilities
- 2 facilities
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
- 6% valid · 1 valid, 17 with no ROA
- ROAs
- 1 authorising AS27418
- ASPA
- no ASPA record
- IRR
- 11% registered · 2 of 18 announcements
- Route objects
- 2 naming AS27418
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: 447 networks and 1,852 prefixes, as published 2026-10-27. 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