Autonomous system
AS15682 ITERANET-AS ISP in Moscow
Unclassified RIPE
Summary
ITERANET
isp hosting telecom business
Two of the blocks are registered to the registry's own placeholder, with no holder named.
What it's used for
- A provider's network. Four IPv4 prefixes and one IPv6 prefix announced from the Russian Federation, three thousand eight hundred and forty addresses, across fourteen observed BGP neighbours.
Notable
- Two blocks carry the netname
RIPE-NCC-MANAGED-ADDRESS-BLOCKand an unknown registrant, which is what the registry puts on space it holds itself rather than on space it has assigned. - Those two sit inside the same range as a third block that is properly registered to the operator, so the parent is documented and the pieces are not.
- A fourth block belongs to a different company entirely, under a netname dated in the current decade, with two contacts whose names use underscores.
- Every answering reverse name writes the four octets in reverse order, hyphenated, before the operator's domain:
255-243-74-212.iteranet.ru. - The AS handle continues past the abbreviation into a plain description of the business and the city.
- Twelve addresses were queried and six returned a name.
Interesting
- Reversed octets in a reverse name are one step from the zone that produced them, where the address is already written backwards. The template was copied out of the zone file rather than written for people, and it reads as a different address entirely.
- A registry placeholder on a routed block is a gap, not a fault. The addresses work; the record just does not say whose they are.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.208.105 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-21, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 3.84K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 5 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS15682- Registry name
- ITERANET-AS
- Registrant
- ITERANET-MNT
- Abuse contact
- adm@iteranet.com
- Registered
- 2002-05-31
- Last changed
- 2024-04-12
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 9 valid, 0 with no ROA
- ROAs
- 9 authorising AS15682
- ASPA
- no ASPA record
- IRR
- 100% registered · 9 of 9 announcements
- Route objects
- 9 naming AS15682
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,779 prefixes, as published 2026-10-22. 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