Autonomous system
AS15392 ELVIM-AS Elvim SIA
Unclassified RIPE
Summary
Elvim
business enterprise
The abuse contact is listed before the company that holds the block.
What it's used for
- A company's address space. A single IPv4
/24announced from Latvia, no IPv6, through two observed BGP neighbours.
Notable
- The registrant field lists a role for abuse first and the company second, the reverse of the usual order.
- The AS handle is the company name with a suffix marking it as an autonomous system; the netname is the same name with the word network instead.
- The company name carries the three letter form used for limited companies in this country.
- Three addresses were queried for reverse DNS and none returned a name.
- Two hundred and fifty-six addresses reaching the internet through two upstreams.
Interesting
- Field order in registry records is not meaningful, but it is revealing. Somebody entered the contact they were asked for most often before the one that identifies the network.
- One small block, two upstreams and nothing published in reverse is the most ordinary shape a network can have. There are thousands of these, and they carry a company's mail and its office connection.
- The corporate form in the name is the only clue to jurisdiction the record gives, and it happens to agree with where the block is announced. That is not always true.
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-11-03, 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 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| LV | Latvia | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS15392- Registry name
- ELVIM-AS
- Registrant
- ELVIM-MNT
- Abuse contact
- it@elvim.lv
- Registered
- 2009-09-18
- Last changed
- 2018-09-04
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 1 with no ROA
- ROAs
- 0 authorising AS15392
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS15392
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,851 prefixes, as published 2026-11-04. 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