Autonomous system
AS216068 BEAPI
Unclassified RIPE
Summary
BEAPI
leased business russia
The AS handle BEAPI is held by BEAPI LLC.
What it's used for
- The address space carries a mix of leased and direct holdings, with netnames
CLIENT-LEASEfor the 72.56.218.0/23 and 72.56.220.0/23 blocks, andBEAPI-NET-176andBEAPI-NET-165for the 147.45.176.0/24 and 193.233.165.0/24 blocks. - The AS announces 1792 IPv4 addresses across 5 prefixes and maintains 2 observed neighbours, a ratio that suggests a small-scale access or business network rather than a transit provider.
- Traffic from this AS consists of business endpoints and leased infrastructure, given the operator's role as a network provider in the Russian Federation.
Notable
- Registrants for the 72.56.218.0/23 and 72.56.220.0/23 prefixes are listed as Alaxona Internet Inc., while the 147.45.176.0/24 and 193.233.165.0/24 prefixes are registered to BEAPI LLC, indicating a mix of leased and owned address space.
- The 195.10.193.0/24 prefix has the netname
RU-PANCHENKO-20250312and is registered to Dmitriy Panchenko, which does not align with the primary BEAPI branding. - The address inventory is small and fragmented, with no IPv6 prefixes announced.
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-31, 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 · 1.79K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 5 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS216068- Registry name
- BEAPI
- Registrant
- BEAPI-MNT
- Abuse contact
- a@beapi.ru
- Registered
- 2023-10-30
- Last changed
- 2023-10-30
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- BEAPI
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Website
- https://www.beapi.ru
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 · 7 valid, 0 with no ROA
- ROAs
- 8 authorising AS216068
- ASPA
- no ASPA record
- IRR
- 100% registered · 7 of 7 announcements
- Route objects
- 10 naming AS216068
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: 447 networks and 1,845 prefixes, as published 2026-10-31. 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