Autonomous system
AS15552 CK
Unclassified RIPE
Summary
Real-net
isp telecom infrastructure
Thirty-three thousand addresses, every sampled one named, and a single observed upstream.
What it's used for
- A broadband provider. Ten IPv4 prefixes and one IPv6
/29announced from the Russian Federation, thirty-three thousand addresses, through one observed BGP neighbour.
Notable
- All eighteen sampled addresses answered, every one with the same form: the address in ordinary forward order, then a three-letter label for broadband access, then a domain under a different brand entirely.
- Nine of the ten blocks carry the country code, the company name and an allocation date; the tenth drops the date and the company, leaving only an operations role.
- Three of those dates fall within four weeks of each other, and two more are three days apart, so the network took several allocations in short bursts rather than steadily.
- The company name sits in quotation marks after its corporate abbreviation.
- Eighteen addresses were queried for reverse DNS and all eighteen returned a name.
Interesting
- Complete reverse coverage on a network this size means the zone is generated, not maintained, and the forward octet order confirms it: a script wrote the address straight into the label.
- Two brands, one in the registry and one in DNS, is the ordinary shape of a provider that trades under a name different from the one it registered.
- One observed upstream for thirty-three thousand subscribers is the exposure worth naming. Everything here depends on a single relationship holding.
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.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS13178 | LLC "Real-net" | 730 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-18, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 10 prefixes · 33.28K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 11 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS15552- Registry name
- CK
- Registrant
- MNT-REAL-NET
- Abuse contact
- abuse@real-net.pro
- Registered
- 2005-04-13
- Last changed
- 2023-03-24
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Real-net
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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 · 12 valid, 0 with no ROA
- ROAs
- 12 authorising AS15552
- ASPA
- no ASPA record
- IRR
- 100% registered · 12 of 12 announcements
- Route objects
- 12 naming AS15552
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: 443 networks and 1,784 prefixes, as published 2026-10-19. 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