Autonomous system
AS54218 BERENET
Unclassified ARIN
Summary
System36
business small us
BERENET is operated by System36 L.L.C.
What it's used for
- The address space carries corporate infrastructure, indicated by netnames
BERENETandRASPBERRYNETSand registrants(rasp)berryand(rasp)berry 2(tmp). - The AS announces 512 IPv4 addresses across 2 prefixes and 4 IPv6 prefixes, with 6 observed neighbours, a ratio consistent with a small business or internal corporate estate rather than a transit or large access network.
- Traffic from this AS represents internal corporate endpoints and services for System36, a US-based technology company.
Notable
- Registrants
(rasp)berryand(rasp)berry 2(tmp)align with the announcerBERENETand the holder System36 L.L.C., confirming consistent ownership of the address space. - The inventory consists of two /24 IPv4 blocks and four IPv6 prefixes, a compact and finely subdivided estate typical of a single organization's internal network segmentation.
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-10-14, 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 4 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 5 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS54218- Registry name
- BERENET
- Registrant
- SYSTEM36 L.L.C.
- Abuse contact
- issue@sys36.net
- Registered
- 2024-01-19
- Last changed
- 2024-09-10
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Berenet
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS-SYS36- Website
- https://sys36.net/
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
- 13 authorising AS54218
- ASPA
- 10 declared providers
- IRR
- 100% registered · 5 of 5 announcements
- Route objects
- 14 naming AS54218
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: 442 networks and 1,771 prefixes, as published 2026-10-15. 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