Autonomous system
AS41704 OGS-AS
Unclassified RIPE
Summary
Ufanet
isp residential orenburg russia
The AS handle OGS-AS is held by JSC "Ufanet".
What it's used for
- The address space carries residential subscriber traffic, evidenced by reverse DNS entries such as
46.191.244.0.dynamic.orsk.ufanet.ruand94.41.164.0.dynamic.o56.ru. - With 38,912 IPv4 addresses announced across 46 prefixes and only 8 observed neighbours, the network functions as an access provider rather than a transit hub.
- Traffic originates from end-user devices in the Orenburg region, consistent with Ufanet's role as a regional internet service provider.
Notable
- All sampled registrants are listed as
Ufanet NOCwith the netnameUBN, aligning perfectly with the AS holder. - The inventory is finely subdivided into numerous /21 and /22 blocks, reflecting site-by-site segmentation typical of a regional ISP managing distinct customer pools.
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-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 47 prefixes · 38.91K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 49 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS41704- Registry name
- OGS-AS
- Registrant
- JSC "Ufanet"
- Abuse contact
- abuse@ufanet.ru
- Registered
- 2006-10-11
- Last changed
- 2018-09-04
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Ufanet Orenburg Branch
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- http://www.ufanet.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 · 74 valid, 0 with no ROA
- ROAs
- 132 authorising AS41704
- ASPA
- no ASPA record
- IRR
- 100% registered · 74 of 74 announcements
- Route objects
- 283 naming AS41704
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: 431 networks and 1,768 prefixes, as published 2026-10-12. 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