Autonomous system
AS212416 PROXIMITY
Unclassified ARIN
Summary
Proximity EOOD
business cloud outsourcing
PROXIMITY is held by Proximity EOOD.
What it's used for
- The address space carries mixed registrants including
NET-31-56-118-0-24,IPXO,RIPE-CLOUNEX-ID,LT-UABXANTHO37-20210930, andINWEB-MULTIUSER-ADSL2. - The AS announces 1280 IPv4 addresses across 5 prefixes and 1 IPv6 prefix, with 5 observed neighbours, indicating a small-scale business or internal corporate estate.
- Proximity EOOD provides enterprise IT outsourcing and cloud infrastructure services, suggesting the traffic consists of business endpoints and cloud workloads.
Notable
- Registrants vary significantly, with some prefixes registered to
Private Customerand others to specific entities likeXantho UABorInternet Utilities, suggesting leased or historically acquired space. - The inventory consists of five distinct /24 blocks and one /48, showing a fragmented address allocation typical of a smaller operator or one that has accumulated space over time.
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-29, 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.28K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| BG | Bulgaria | 6 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS212416- Registry name
- Proximity
- Registrant
- MNT-LIR-BG
- Abuse contact
- manzur@proximity-bg.com
- Registered
- 2020-11-04
- Last changed
- 2020-11-16
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Proximity
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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
- 86% valid · 6 valid, 1 with no ROA
- ROAs
- 6 authorising AS212416
- ASPA
- no ASPA record
- IRR
- 86% registered · 6 of 7 announcements
- Route objects
- 11 naming AS212416
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: 448 networks and 1,849 prefixes, as published 2026-10-29. 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