Autonomous system
AS48610 OFORO
Unclassified RIPE NSP
Summary
OFORO
isp regional russia
The AS handle OFORO is held by Bykov Roman Andreevich.
What it's used for
- The address space carries a single IPv4 prefix,
176.97.194.0/24, and one IPv6 prefix,2a13:8e40::/36, with the netnameRU-OFORO-20211022. - With 256 IPv4 addresses announced against 40 observed neighbours, the ratio indicates a transit or network service provider role rather than a large access network.
- As a regional Network Service Provider (NSP) in Russia, the traffic consists of upstream transit and interconnection for its customer base.
Notable
- The registrant
Bykov Roman Andreevichmatches the AS holder and the PeeringDB identity, confirming consistent ownership. - The address inventory is minimal, consisting of one /24 block and one /36 block, typical for a small regional operator.
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 2 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.209.232 |
| NetIX | Sofia, Bulgaria | 2001:67c:29f0::4:8610:1 |
Transit providers
10 upstream, 2 downstream and 20 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-16, 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 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48610- Registry name
- OFORO
- Registrant
- lir-ru-oforo-1-MNT
- Abuse contact
- info@oforo.ru
- Registered
- 2023-07-13
- Last changed
- 2025-05-12
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Bykov Roman Andreevich
- Also known as
- OFORO
- Network type
- NSP
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Selective
- IRR as-set
AS48610:AS-OFORO- Present at
- 12 exchanges
- Facilities
- 2 facilities
- Website
- https://oforo.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 · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS48610
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS48610
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,783 prefixes, as published 2026-10-17. 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