Skip to main content

AS48293

UNIONTEL-RU-AS

CLIENTS

Registry

Authoritative registration data

AS number
48293
Name
UNIONTEL-RU-AS
Organisation
CLIENTS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

23

IPv6 prefixes

1

Total announced

24

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS48293
94.228.192.0/20 IPv4 /20 not checked
185.108.20.0/22 IPv4 /22 not checked
91.194.246.0/23 IPv4 /23 not checked
185.108.20.0/24 IPv4 /24 not checked
185.108.21.0/24 IPv4 /24 not checked
185.108.22.0/24 IPv4 /24 not checked
91.194.247.0/24 IPv4 /24 not checked
91.212.217.0/24 IPv4 /24 not checked
94.228.192.0/24 IPv4 /24 not checked
94.228.193.0/24 IPv4 /24 not checked
94.228.194.0/24 IPv4 /24 not checked
94.228.195.0/24 IPv4 /24 not checked
94.228.196.0/24 IPv4 /24 not checked
94.228.197.0/24 IPv4 /24 not checked
94.228.198.0/24 IPv4 /24 not checked
94.228.199.0/24 IPv4 /24 not checked
94.228.200.0/24 IPv4 /24 not checked
94.228.201.0/24 IPv4 /24 not checked
94.228.202.0/24 IPv4 /24 not checked
94.228.203.0/24 IPv4 /24 not checked
94.228.204.0/24 IPv4 /24 not checked
94.228.205.0/24 IPv4 /24 not checked
94.228.207.0/24 IPv4 /24 not checked
2a06:4180::/29 IPv6 /29 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS48293
Address families
CLOUD-IX MSK 10,000 Mbps IPv4
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 80,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,000 Mbps IPv4 · IPv6
W-IX: vlan800 20,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS48293 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS48293 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 1,035 3,114
v4
AS20764 RASCOM-AS 135 226
v4 v6
AS29076 CITYTELECOM-AS 133 209
v4 v6
AS47122 CYBERFIRST-AS 150 169
v4
AS35598 INETCOM 31 119
v4
AS6939 HURRICANE 61 74
v6
AS62255 BEMYLINK 9 50
v4
AS25091 IP-Max 19 39
v4 v6
AS1299 TWELVE99 23 26
v6
AS13194 BITE 1 18
v4
AS48166 FORTEX-AS 2 16
v4

No rows match “”.

Showing – of

Observed downstreams

12 networks seen after AS48293 in AS paths

Observed downstreams
Families
AS205784 NV-Tel 142 728
v4
AS60986 RDITELECOM-AS 157 675
v4
AS59665 ULTRATEL-AS 154 388
v4
AS64419 ECOTEL-AS 20 319
v4
AS57375 VN 157 200
v4
AS44342 NetComLine 158 197
v4
AS208936 COMVIP-AS 158 197
v4
AS56493 DLINE-AS 109 139
v4
AS43595 UGRESHA-NET-AS 65 79
v6
AS211134 AS-Intersys 40 42
v4
AS49357 AS-UTECH-RU 10 24
v4
AS210201 Connected-businiess 6 8
v4

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 8 120
v4 v6
AS49673 TRUENETWORK 10 60
v4
AS37721 ORG-VTS1-AFRINIC 9 49
v4
AS34927 iFog-GmbH 1 36
v4
AS49544 i3Dnet 2 5
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.